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.

I agree with Phil that it's usually better to track with variables on a custom menu. This post about custom menus describes using T/F variables to track what scenes are completed. It also has a demo file. It controls the Player's Next button, but the same programming could be use to control a custom button or automatic advancing.

A few other things to know about Storyline:

An object with a Visited state automatically changes to that state when it is clicked. You don't need any triggers to change to Visited. (For more info, see the primer about built-in states.) For more control, it's sometimes better to use a custom "Done" state, and change to that state with a trigger.

Triggers run in order. However, any triggers that appear after a "jump to" trigger won't run, because the user has already left the slide. Thus, your "change to Visited" triggers that appear after the "jump to slide" triggers don't run. The objects changed to Visited because that's built-in functionality (as mentioned above). 

A "when the timeline starts on this slide" trigger runs every time the user visits the slide. That's true even if the Slide Properties are "Resume saved state." So that kind of trigger needs one or more conditions if you only want it to run in some situations.

You would be better tracking variables on this one.

and then set a trigger to jump when user returns to the map either on the slide they click to return or the map slide when all variables are true,

I can think of a few different possibilities. If you want people to return to the map before progressing to the final (seventh) sector, an automatic go-to could be triggered on the map slide when the timeline starts if the state of all six sector buttons is visited. Since the trigger is "when the timeline starts," it won't fire until the learner revisits the map after completing the sixth sector and returning to the map.

A slightly more accessible version would have a seventh button hidden on the map that only appears (again when the timeline starts) if the six buttons are all visited. That way learners won't be able to click it until they've returned to the menu from the sixth sector, but will still retain control of course and progress when they're ready. If your map has a visual theme (e.g., pirates) then I'm sure the seventh button can be "story"d in.