📖 User Guide

This user Guide is updated regularly. It allows you to enter in the details to learn how to use the editor.

📄 View manual in PDF format

Listen in voice mode :

Storyboard

Last update: February 09, 2026

🔗 Editing & Connections

Cutscenes are represented by an image node.
This image is not just decorative: it represents the camera view of the very first frame of the cinematic. 🎥
It gives you a visual preview of what the cutscene is about and where it begins in the world.

Each cutscene node marks the exact point where a cinematic sequence starts in your game.

These cutscenes can be connected together using mission blocks.

One cutscene can be marked as Start.
This checkbox defines the very first cinematic of your game.
A starting cutscene does not need to be connected to any mission before it. 🚀

Missions are represented by simple text blocks. They display the mission description, making them easy to identify within the storyboard.

A mission can connect two cutscenes.
The logic follows the natural flow of gameplay:

  • A cutscene starts in the game.
  • At the end of the cutscene, a mission begins.
  • When the mission ends, it unlocks another cutscene.
  • This next cutscene then becomes accessible in the game.

This process can repeat as many times as needed to build a complete and coherent storyline. 🔁📖

Each mission can optionally lead to two different cutscenes:

  • 🎉 A success cutscene, played when the mission is completed successfully.
  • 💀 A failure cutscene, played when the mission fails.

Connecting a failure cutscene is optional. If no failure cutscene is linked, the game will simply not trigger a cinematic on mission failure.

Below are examples of mission connections:

top  page