Help !

This should be a simple branching scenario, and it’s easy to set up if you follow a few key steps:

• Set the map slide to Resume Saved State in the slide properties. This ensures that any buttons already visited will retain their state when the learner revisits the slide.
• All buttons come with built-in Visited states. Because of this, creating an additional trigger to change a button to “Visited” when clicked is redundant, the state updates automatically on click.
• While you can manage this scenario without variables, I strongly recommend using variables as your project grows. They provide better control and make it easier to track learner progress across more complex interactions. 

From a design perspective:

• I don’t recommend automatically jumping to the final slide once all buttons are visited. It’s better to let the learner stay in control.
• Give learners time to review what they’ve completed and read any success message or further instructions before moving on.
• Automatically advancing can also create a brief visual “flash” when revisiting the slide (before it jumps ahead), which doesn’t look polished or professional.

What you can do instead:

• Add a Next (or continue) button that appears only after all buttons on the map have been visited.

I’ve attached a simple storyline demo that shows how to achieve this without variables or redundant trigger. Just a clean setup where a Continue button appears once all map buttons are visited, allowing the learner to proceed to the final slide.

If you were using variables, you would typically set each sector variable to True when the timeline starts on its corresponding slide. Then, on the main map slide, you would change the state of the Continue button to Normal (unhide it) once all sector variables are True without needing to rely on slide properties (such as Resume Saved State vs. Reset to Initial State) or the built-in Visited states of buttons.