🟨 Open module

The Open a module block allows you to navigate to the highest level of the tree structure of your Celestory project: change the Application Module altogether.

Where the graph segments the internal logic, modules are often used as completely disconnected scenes (a module for the Main Menu, a module for Level 1 of the game, a module for the "Learning" phase and another "Evaluation" in a Serious Game).

📥 Entries

• in (Flow): Entry point to trigger the transition to the new module.
• module (Module): Allows you to select from the list of all modules in your project which one should be loaded and executed.

📤 Outings

• out (Flux): Exit point. Please note, this flow is theoretically activated to finalize the state of the block, but given that the application will load and change its executive base (new module), the direct continuation of this flow has very little chance of being executed in the new environment. Its use is therefore very specific or marginal.

💡 Example of use

Scenario: Launching the game from the main menu

1. Your project has two modules: "Home Module" and "Game Module".
2. In the "Home Module", the user reads the rules and clicks on "Start".
3. The interaction of the "Start" button (clickable area) is connected to the Open a module block.
4. You choose “Game Module” as your target.
5. Celestory closes the host environment and fully loads the structure, scenery and logic of the “Game Module”.

⚙️ Technical Details

• This block works via module references (ModuleRef). It triggers a shutdown of the virtual machine for the current module and an initial restart on the selected module.
• Pay attention to the persistence of your variables. When changing modules, global variables (often called project variables) are retained, while module-local variables can be reset, depending on your application design.

Updated on: 04/03/2026