The codeblocks indented below the if line will execute if the condition evaluates to true.

Description

Placed directly below an if, will run indented codeblocks if the first if is false. Can also be placed under an else if.

The codeblocks indented below the while line will execute when the condition evaluates to true. This is useful when iterating through a list.

The object the script is attached to runs when world is started at the start of the world, i.e., when the first person enters the world’s instance or upon using the codeblock reset world state.

The when event is received codeblock is executed when it receives a data transmission called an “event” from either itself or a script attached to another object.

This sets off an event on self. Replacing self with an object variable, allows for the other object to receive the event. You can use this to create communication between multiple objects.

This sets off an event on self after a delay. Replacing self with a different object, allows for another object to receive the event. Effectively communicating between objects.

Cancel sending event with delay stops the transmission of a send event with delay event that is still in progress.

Codeblocks below the when trigger is entered by object line will execute when an object enters the trigger. The trigger must be configured to detect objects with a specific tag, and the object must have that tag.

Codeblocks below the when trigger is exited by object line will execute when an object exits the trigger.

Codeblocks below when colliding with object will execute when another object collides with the object the script is attached to.

Codeblocks below the when colliding with player line will execute when a player’s head or torso collides with the object the script is attached to.

Commands below the when trigger is entered by player line will execute when a player enters the trigger the script is attached to. The trigger must be configured to detect players.

Description

Commands below when world is entered by player will execute when a player enters the game world, and again if the world is reset.

Commands below when world is exited by player will execute when a player leaves the world. When editing your world, the when player exits the world event will execute when a player enters build mode.

Event executes when a projectile, from the launcher gizmo, hits a player.

Event executes when a projectile, from the launcher gizmo, hits an interactive object.

Event executes when a projectile, from the launcher gizmo, hits a static object.

Event that runs when the object is grabbed by a player.

Event that runs when the object is released by a player.

Event that runs when the object is grabbed by a player with two hands.

Event that runs when the object is no longer grabbed by two hands.

Commands below when object is attached to player will execute when a player attaches an object to their avatar.

Commands below when object is unattached to player will execute when a player unattaches the object from their avatar.

This event executes when a player presses the index trigger button on their controller while grabbing the object that the script is attached to.

This event executes when a player releases the index trigger button on their controller when holding the object that the script is attached to.

Depending on which Touch Controller, the right or left, is holding the object, A or X buttons will represent button1.

Depending on which Touch Controller, the right or left, is holding the object, A or X buttons will represent button1.

Depending on which Touch Controller, the right or left, is holding the object, B or Y buttons will represent button2.

Depending on which Touch Controller, the right or left, is holding the object, B or Y buttons will represent button2.

Connect to event allows you to listen to specific events from other objects, and map them to local events.

Listen to allows you to receive all events from another object.