An area that seems to stop a lot of people is using the scenario function. It is important to understand that when you place a scenario into your course structure, the normal navigation is disabled by default. This means the only way past the scenario is to complete it.
If you add a scenario to your course in the outline, but have not yet got around to populating it with screens, you need to put in at least one empty "jump to" screen with an option to leave the scenario, or else your preview will stop when it gets to the scenario with no way forward.
We will add some simple scenario design templates this week to help people get started.
There are three quite common designs. One is to use the scenario as an assessment, where each choice the user makes can lead them to a different path with different outcomes, no going back, but with the possibility to make corrective choices along the way and achieve a final scored outcome.
Another is to establish the problem you are posing at the outset, and then allow the user to choose branches that will help them solve the problem or fill gaps in their knowledge. At all times in this type of scenario, they can jump to the end and solve the problem.
A third model is the "best practice algorythm" where the correct path through the scenario is established first, and then you place choices along the way that lead to remedial learning if they get it wrong, but always return them to the proper path.
There are many other ways to build scenarios, and the beauty of doing it in myUdutu is that you can continue to improve and expand or change your scenario as time and experience gives you new insights. So the most common problem of scenarios is defeated. (thats when your learners discover the logic and spread the word).
We will add scripts to create the screen structure for each of these scenario types, and add others as we hear from you. Any interesting models you create and want to share would be most appreciated.