Checkpoints can be used for few things:
- Designating the entry point (start) of your entire flow (this is a must-have)
- Designating where a section of your flow starts
- Stopping any currently repeating voice
While the Initial Checkpoint is a must, the section checkpoints are a merely a good practice. Using such checkpoint will allow to to shuffle sections of your flow graph around, and also start your simulation from any checkpoint (you just temporarily mark it as Initial). It’s great for debugging!
So it’s a great node to structure and organize your flow.
If you use Checkpoints to designate separate sections of your flow, try to make each section self-contained and not dependant on others.
Behavior
If tagged as Initial, this is where the simulation will start.
If not tagged as Initial, the node does nothing when flow reaches it.
Editor Only: To help you building non-dependant sections, the Node will check the scene for any remaining Grabbable or Selectable objects and provide an error in console if there are any left.
Typically you don’t want the user to have interactivity when a section ends. So if you see those errors in the console, that most likely means that you’ve forgotten to disable some grabs or selections by the end of the section.
Usage
You turn a Checkpoint into Initial Checkpoint by selecting it and clicking the Set Starting Checkpoint button.
Note that all Checkpoints are blue, while Initial Checkpoint is light blue (some would also call this color teal 😎).
Use Checkpoint wherever a new assignment starts. Any currently repeated voice will be stopped once Checkpoint is met.
States
No states, this node is instant.
Notes
The main idea of Checkpoint is to help you organizing a big endless flow into a number of smaller understandable sections.
While it can be a great aid, it wouldn’t help it you don’t create consice and independent sections in your flow.