Quick answer: Construct 3 Trigger once while true firing in a fresh layout when you wanted project-wide one-shot? Trigger state is per-layout; transitions reset it.

A tutorial pop-up uses Trigger once; visiting another layout and coming back shows the tutorial again.

Trigger State Is Per-Layout

Trigger conditions track their fire state in the current layout’s event sheet instance. Going to another layout resets state. Returning re-fires.

Global Variable Pattern

Global tutorial_shown = 0
// Condition: tutorial_shown = 0
// Action: Show tutorial, set tutorial_shown = 1

Global value survives layout changes. Explicit, no trigger semantics needed.

Local Storage for Persistence

Save to Local Storage to survive game restarts. On start of layout -> load the flag, gate tutorial on it.

Item-Counted Triggers

For “show first 3 times”, store a counter. More flexible than trigger-once for multi-occurrence cases.

Verifying

One-time events fire exactly once across the project lifetime. No repeat tutorials on layout return.

“Trigger once is per-layout. Use a global variable for persistent one-shots.”

Treat one-shot UX flags as game state — persist them to Local Storage and the system survives restarts and crashes.