Events Actions System Explained

Object Events (Overview)

Object Events are how your launcher reacts to user interaction and behaviour.

Whenever something happens to an object — like a button being clicked, a textbox changing, or a video finishing — an event is triggered. You then attach actions to that event to control what happens next.

Pro Tip

Events = something happens Actions = what you want to do about it

The Basics (Beginner Friendly)

What is an Event?

An event is simply a trigger.

User clicks a button → event fires
User types in a textbox → event fires
A video finishes → event fires

You don’t control when events happen — they happen automatically based on interaction.

What is an Action?

An action is what your launcher does when an event happens.

Change page
Show or hide something
Play a sound
Run a login

Putting It Together

You connect an event to one or more actions.

Example:

Button → On Click → Change Page

That’s the core idea. Every interactive launcher is built from this.

Events Dialog

When you open an object’s events, you’ll see:

Left side → Available events for that object
Right side → Actions for the selected event

Each event has its own action list. Think of it like separate logic blocks.

How Actions Run

When an event is triggered, all its actions run in order.

Action 1 runs
Then Action 2
Then Action 3

Each action finishes before the next one starts.

Simple Example

Goal: Open a new page when a button is clicked

Select your button
Open Events
Choose On Click
Add action → Change Page

Done. That’s your first working interaction.

Key Things to Understand

Events belong to objects

Not every object has the same events. A video has different events than a button.

Actions are shared

Most actions can be used across different objects and events.

Order matters

Actions run top to bottom. Changing the order changes behaviour.

Multiple actions allowed

One event can trigger many actions, not just one.

Common Use Cases

Buttons navigating between pages
Form inputs triggering validation
Videos triggering actions when finished
Login buttons starting authentication

Almost everything interactive in your launcher is powered by Object Events.

Advanced (For Developers)

Under the hood, object events are mapped to real runtime events (clicks, input changes, media events, etc). When triggered, they pass through the event system and execute a defined action chain.

A few important concepts:

Event mapping – Editor events (like "On Click") map to real runtime triggers
Sequential execution – Actions are processed in strict order
Parameter resolution – Variables and expressions are evaluated before execution
Object targeting – Actions can target objects across pages using identifiers

Because everything flows through the same action system, this means:

You can chain complex behaviour easily
You can reuse logic across different objects
You can build fully dynamic UI without writing code

Tip:

Combine Object Events with Global Events and Variables, and you effectively have a full logic system.

Final Thoughts

Object Events are the foundation of interactivity. Once you understand how events trigger actions, you can build almost anything inside the launcher.

Start simple. Click → Action. Then build from there.

Pro Tip

Next step: dive into individual object event pages to see exactly what each object can do.