Forum Discussion
Building branching Storyline simulations that let learners go down the wrong path
KevinReagh: There are different ways to branch in Storyline. For extended "paths," I branch to slides (instead of layers). But the "best" method really depends on the complexity of the branching, as well as personal preferences.
I think these are the most important steps:
- Map out the branching in advance.
- Test all the possible paths, including recovering/restarting.
My post about branching includes a .story file that demonstrates how to let the users choose their own path. However, the same programming advice applies for branching simulations.
I agree with JudyNollet's point here! There are a lot of things that can be technically accomplished on a single slide with states and layers, but that I find easier to understand the overall decision tree if I keep to individual slides. Making use of the "scenes" framework in Storyline is also super useful for staying organized. Essentially making design decisions that allow you to see the "logic" of the scenario at a glance on the Story view, versus having those different branches obscured by the trigger behavior. If you prioritize your Story view as a "logic map" it makes the whole thing a lot easier to keep organized in my opinion.