Button from Base Layer SHowing up On Other Layers EVen though Hidden?

The problem with initiating a trigger action "When state of ..." is that it only fires at the moment the last of the listed unchanged states changes. Then if the Next button gets changed back, there is no way to change it again. I changed the trigger that disables Next when the timeline begins. That's reliable, because the timeline begins on revisit, whether it is set to Reset, Resume, or Automatically Decide. I changed it to enable Next if the conditions are met, and used an Else to disable it if they aren't all met.

I set slide 1.2 to use variables to do the changing. The disadvantage of that is a few more triggers. The advantage is that you can require an action on the last visited layer. You can't require reading, but at least action. You can use that action to hide the layer so a return is to the base.

I set slide 1.3 to use states to do the changing. The disadvantage is that if they click around and Next gets disabled, there is no way to advance. The advantage is fewer triggers. What may be either is that Next is available as soon as the last option is clicked. They don't have to return to the base to advance (advantage), but if they don't, if they do return the layer is visible, not the base (disadvantage).

Use whichever you think best. I am partial to variables, because unrelated actions can potentially change states, but my triggers are the only things that can change variables.

On thing I do suggest is changing "Back". You may be clear on what it means, but the learner may not be. they could think, for example, "I don't want to go back. I don't want to repeat something I have already done." I prefer "Continue" as it carries the idea of moving forward.