Global Events

Global Events (Developer Edition)

Global Events are system-level triggers that allow your launcher to run logic automatically, without the user clicking anything or interacting with the UI.

Instead of attaching logic to buttons or objects, Global Events sit above everything and let you control behaviour across the entire launcher.

How Global Events Work

Each Global Event contains a list of actions. When the event fires, those actions run in order, one after the other.

• No user interaction required
• Runs automatically based on triggers
• Executes actions sequentially
• 
  

Global Events Dialog

From this dialog, you select an event on the left and build its logic on the right. Each event becomes its own self-contained action flow.

Available Global Events

Launcher Lifecycle

• On Launcher Start – Runs when the launcher starts
• On Launcher Exit – Runs when the launcher is closing
• On Window Close – Triggered when the window is closed
• On Window Minimize – Triggered when minimized

These are your entry and exit points. Use them to initialise things or clean up before closing.

Install & Update

• On Install – Runs after installation
• On Update – Runs when the launcher updates

Useful for version changes, migrations, or setting up new data.

Always Events

• Always 1
• Always 2
• Always 3
• Always 4
• Always 5

These run continuously while the launcher is open. Think of them as a live loop.

Timed Events

• Every 1 Second
• Every 2 Seconds
• Every 5 Seconds
• Every 10 Seconds
• Every 1 Minute
• Every 5 Minutes
• Every 10 Minutes
• Every 30 Minutes
• Every 60 Minutes

These run on a schedule. Ideal for anything that needs to happen in the background at intervals.

What You Can Build

Auto Login

Run login logic on launcher start so users don’t have to log in every time.

• Check stored credentials
• Call login
• Update UI state

Live Updates

Keep your launcher fresh without user interaction.

• Refresh entitlements
• Update news feeds
• Check server status

Patch Detection

Poll your patch system in the background and react instantly.

• Check for updates every few minutes
• Trigger update UI automatically

Dynamic Behaviour

React to changing conditions in real time.

• Show or hide UI elements
• Trigger logic based on variables

Shutdown Handling

Cleanly handle exit logic.

• Save settings
• Store session data
• Send analytics

How Actions Run

When an event fires, its actions run one by one in order. Each action completes before the next starts.

• Variables are resolved before execution
• Expressions are evaluated at runtime
• If one action fails, the rest still continue

Best Practices

• Use timed events instead of Always where possible
• Keep Always logic minimal
• Use Global Events for shared logic instead of duplicating it
• Drive behaviour using variables

Global vs Object Events

Global Events let your launcher operate independently of the user. Instead of waiting for input, you can run logic automatically, react to changes, and keep everything up to date in the background.

Once you start using them properly, your launcher stops feeling static and starts behaving like a real system.