Changing Object States with Triggers and Variables for a simple Main Menu (5 Steps)

I searched many posts here and after absorbing a LOT of info, I finally figured out object states/triggers/variables in a way that makes sense to me. Sometimes it's difficult following along with the specific needs of others' projects but I'm hoping this will help make it plain for someone doing the exact thing I've done with a main menu.

Since Storyline 2  is great, it's easy to assume the intuitiveness/automation of certain features since they seem so simple but this group of features require a bit more effort.

Changing Object States with Triggers and Variables for a simple Main Menu
1) Create your menu objects. In my example I had 3 rectangles.

2) Create a true/false variable for each of your menu objects and set them to false.

3) Create the states for your menu objects. I chose Normal, Hover, and created a custom state that I named Completed. This custom state was very important because the Built-In state "Visited" would trigger my menu object states right away when slides were viewed, but my goal was to only trigger an object state when the last slide in the sequence was viewed. 

4) Create triggers for each object state and set conditions for each variable. Your object states will become triggered when your default- False variables are set equal to True.

Now this step is essentially the game "Duck Duck, Goose" but instead will be "False False, True" 

5) Add triggers to each slide associated with your menu object. All slide triggers should be set to False except for the last one. Setting these slides to False is pretty redundant and it would be nice if Storyline knew exactly what we wanted, but we have to tell Storyline to ignore these slides and only focus on the last slide in this way. One assumption I made, was that Storyline knew to ignore slides with no triggers and only focus on the slide trigger set to True. Wrong! Each slide needs a slide trigger with an adjusted variable action. This is OK unless you have hundreds of slides; maybe we can suggest a feature that can eliminate this in the future perhaps. Each of the triggers also need to be set to when the timeline starts for the slides. (For example, when your last slide trigger is set to True, once the timeline of the last slide starts, the menu object state will have been triggered when you go back to the menu.)

• Majority of slides will be set to False, except for the last one

• Your last slide should be set to True

Now when you preview your project, your object state should be changed how you specified when the learner accesses the last slide associated with your menu object. I really hope this helps someone. Everyone here has been a tremendous help for me. Thank you for being awesome! Pay it forward :-)