Designing Tutorials for Adaptability

Consider the following when planning your tutorial code:

• Adaptive components work by turning game objects on (gameObject.SetActive(true)) when a tutorial step starts and turning them off when that step is complete.

• You can initiate any dynamic sequences within a step using MonoBehaviour events. For example, Unity invokes OnEnable when a GameObject is turned on.

• You can bind adaptive components to more than one tutorial step to share GameObjects across multiple steps and multiple tutorials.

• Child GameObjects are only enabled when their parent GameObject is enabled, so be careful when nesting adaptive content.

• The Tutorial Manager automatically creates a remote text field for AdaptiveText components, which you can use to revise the text even after your game is live.

• Only one AdaptiveText component is supported per tutorial step. You can use AdaptiveContent components for additional tutorial text elements, but remote fields are not created for such elements.

• AdaptiveContent components have an option, Respect ‘off’ decision, which you can use to show portions of a tutorial even when the Tutorial Manager decision engine determines that a tutorial should not be shown to the current player. If you play a tutorial step associated with a component that respects the off decision, that component only turns on when the Tutorial Manager has decided the tutorial should be shown. If a component does not respect the off decision, then that component turns on whenever the associated tutorial step is played, no matter which decision has been made about showing the tutorial.

• Each tutorial has a limit of 50 steps.

• It is your responsibility to keep track of which tutorials have been completed if your game has more than one tutorial. The Tutorial Manager only keeps track of the most recent tutorial you started.