SandboX

Build your own scripted games in your Player World: functions, conditions and calls, the cinematic camera, character dialogue, and main-world sets.

SandboX is GamerX's in-game scripting tool. Without writing any code, you place functions in your Player World: checkpoints, teleports, timers, vehicles, pickups, messages, camera scenes and character dialogue. You chain them together with conditions and calls, the way code wires events to functions, to make races, obstacle courses, cutscenes, quests and mini-games. Then you save the result as a SandboX set that anyone can load.

> This page describes exactly what the game does today, read from the SandboX script itself. SandboX is being reworked: the [Known problems](#known-problems) and [Open questions](#open-questions-for-the-rework) sections at the end are where that work is being discussed. Use the comments at the bottom of the page to join in.

How it works in one minute

• A set is a file holding everything you built. Load it in editing mode to build, or in active mode to play it.
• A function is one action, such as "show a checkpoint here" or "give a Desert Eagle". Each function has an ID (1 to 99). It does nothing until something calls it.
• A function has conditions: the things that can happen to it. A vehicle can be entered, exited or explode; a checkpoint can be entered or left. See [the list](#conditions-and-calls).
• A call runs a function when a condition is met: "when function 5 (a checkpoint) is entered, call function 6". A condition can have as many calls as you like; they run in order, like the lines of an event handler.
• start is the set's own condition: it is met when the set is activated, like main() in a program. Everything begins with the calls on start.
• Every function also has involved players, the people it acts on: the trigger player (whoever entered the checkpoint), all players, a team, or nobody (for things placed in the world).

The chain looks like this:

Getting started: your Player World

SandboX runs in your own Player World (virtual world 1000 + your player ID). See player-worlds for more about worlds.

Visitors who join a world with an active set join the game in progress. They get the checkpoints, vehicles, sounds, freezes and character dialogue that are already running.

Sets: create, load, save, delete

You must be logged in for the set commands. Leaving your world (or disconnecting) unloads your set.

Alliance types

A new set first asks "Choose an Alliance Type.":

Building: functions

While editing, you see SandboX Editing Mode in the top right. Hold the walk key (or Y) to see the SandboX Editing Chart:

• the first row is start, with the functions it calls;
• every other row is one condition that has calls: the function and its condition on the left, the functions it calls (with their call IDs) on the right.

Most functions end with "Who is involved in this function?":

• Trigger Player (the one who met the condition), All Players, Player Allies, Player Enemies, or one team.
• When start calls a Trigger Player function, nobody has triggered anything yet, so it runs once for every player in the world, each as their own trigger player.

Positions are taken from where you stand when you finish the function.

Function types

LP (Launch Player) and BP (Boost Player) have codes but are not finished.

Conditions and calls

A condition is something that can happen to a function. A call says what happens then: "when this condition of this function is met, run that function". Think of a condition as an event and its calls as the event handler's lines.

The other function types have no conditions: they only do things.

The game answers "\ You created call number n on function number 4, condition "exit"."* and "\ On player exits the vehicle, function number 9 (CM) Client Message runs."* A condition can also be typed as its number (/call 4 3 9).

Good to know:

• Every call on a condition runs, in call ID order, so one condition can run several functions. A condition with no call does nothing.
• The player who met the condition is the trigger player for the functions it calls. When a vehicle explodes, that is the player it was spawned for, or else whoever the game says destroyed it.
• Getting into a Spawn Vehicle for Player vehicle doesn't count as enter at the moment SandboX puts the player in it; only getting back in does.
• Calls never run for a player who is in editing mode, so test your set in active mode.
• A checkpoint keeps working after it is entered, until a Destroy Function removes it.
• /condition, /conditiontypes and /deletecondition are the old names of /call, /conditions and /deletecall, and still work.
• Sets made with channels (before 2026-10-30) are converted when they load: channel 0 becomes calls on start, and each old condition becomes one call for every function that was on its channel, so the set does what it did. Saving it keeps the new form.

The cinematic camera (CC)

/function CC opens the camera editor:

1. You fly freely with the movement keys. The black bars of a film scene show what the camera sees.
2. Choose the fade the scene starts with: Normal, Slow or Fast.
3. Fly to a spot, look where you want, and press fire to save the camera position. Then enter how long it stays there (Position Length, 1-30000 ms).
4. Use Create New Camera Position for the next one (up to 20). Choose how the camera gets there:
5. Cut: jumps straight there;
6. Move: glides there, taking the Movement Speed you give;
7. Fade: goes black and comes back at the new spot (Normal, Slow or Fast).
8. < and > browse the positions; Edit Camera Position changes one.
9. Preview: play the whole Sequence, or just the Transition into the current position.
10. set call on current position runs a function when playback reaches that position (the position condition). Use it to time events with the scene.
11. Save and Exit CC Editing Mode asks for the fade at the end, then who is involved.

Character dialogue (CD)

/function CD opens the dialogue editor: a box with a character, their name and their lines. Click the arrows to change:

• the name;
• the model (skin 0-312);
• the colour (as 0xRRGGBBAA);
• each of the 8 dialogue lines (22 characters each, aligned left, centre or right).

The default is a Medic (skin 274). Save and Exit asks who is involved.

Menus (MN)

/function MN makes a menu: a window with buttons that a player answers, and every possible answer is a condition you can call functions from. For example a box "Are you sure?" whose Confirm calls function 5 and whose Cancel calls function 6, or a list whose items each call a different function.

1. Type /function MN (or click Menu (MN) in /function) and choose what kind of menu:
2. Message box: text and one or two buttons;
3. Input: a box to type in (Password: the same, shown as dots);
4. List: pick one item;
5. Table list: items in columns, | between the columns (for example M4|$500); Table list with headers: the first line is the column titles (Weapon|Price).
6. The Menu Settings list opens, already filled in (a message box starts as "Are you sure?" with Confirm and Cancel). Click a row to change it:
7. Title: the line at the top (up to 64 characters);
8. Text (or Items for a list): a line at a time. + Add one, click one to change it (empty deletes it), or delete them all. Colours work ({FF0000}red);
9. Answers (input and password only, optional): words players might type. Each answer is a condition of its own;
10. Button 1, Button 2 (leave button 2 empty for one button; Esc still counts as button2);
11. Who sees it: the triggering player (the default; from start, every player in the world), all players in the set's world, or for team sets the trigger player's enemies or team, or one team;
12. Preview: shows you the menu now, and tells you which conditions your answer would meet.
13. Click Done. Then call functions from its conditions: /call 7 button1 5 and /call 7 button2 6, or /call 7 item2 9. /conditions 7 lists them all with the button and item texts; /functions 7 shows them too, with + add a call under each.

Also accepted when you type a call: confirm, ok, select or any for button1, and cancel or close for button2.

Good to know:

• One answer can meet several conditions. Their calls run in this order: button1 first, then the item, or number, then the matching answers (or other). button2 (or Esc) meets only button2.
• Each player answers for themselves: they are the triggering player of the calls their answer runs.
• An answer only counts while the set is still loaded and the player is still in its world. If the set was unloaded (or the menu deleted) before they answered, nothing happens.
• Players in editing mode never see a running set's menus (use Preview).
• Changing a list's items moves the conditions with them: a call on item3 is on whatever item is third.
• SandboX has no variables yet, so the text a player types can't be stored or shown again; only which condition it meets.

Main-world sets (Hosts)

A Host standing in the main world (VW 0) who types /loadsandboxset [file] loads that set active for everyone in the main world. It is also added to the list of sets that load when the server starts (SandboXLoadOnFilterInIt.txt). Players get its running functions when they spawn.

The main world loads these sets at startup today: l1, gasajump4, rustler, intro v 011, mike, GXBillboard and ClassicPickups.

/unloadsandboxset [name] unloads one and takes it off the startup list.

Saved files (for builders and Hosts)

Sets are text files in scriptfiles/SandboXSystem/SandboXFiles/NAME.txt (83 today). One line per item, with commas between the values:

Commas in message and menu texts are saved as ` ``. Files from before menus (2026-11-05) load as they did; a file with menus needs the new SandboX to load them.

Limits

Known problems

Found by reading the script (2026-10-27). Each is a candidate for the rework:

1. Player Allies and Player Enemies are swapped: choosing "Player Allies" stores enemies, and the other way round.
2. Team-colour targets (Team Blue/Red/Yellow/Green) most likely fail when the function is finished, before it is saved.
3. **/lockworld never locks**: it locks and unlocks in the same go, so it always ends unlocked.
4. **Typing /myworld while already in your world unloads your set** without asking. /joinworld from your own world does the same.
5. Anyone can unload a main-world set with /unloadsandboxset NAME, and take it off the startup list.
6. Saving can't overwrite, so every edit needs a new file name.
7. Interiors are ignored: checkpoints always appear in interior 0, and teleports and vehicles don't record one.
8. "At my Location" sounds lose their spot when the set is saved: after loading, they play at 0, 0, 0.
9. Editing a Give Gun function gives the wrong weapon (it stores the list position instead of the weapon ID).
10. When a set is full (99 functions), the next function silently overwrites an old one. (Calls: fixed 2026-10-30, the 200th is refused.)
11. A 20-position camera scene runs off the end of its list.
12. The character colour box likely reads the colour as 0, and the skin check never refuses anything.
13. DEBUG lines go to every player when team sets load, and the editing chart leaks text draws each time it is shown.
14. Things that run with no trigger player (all-player timers and cameras called from start) use player ID -1 in places, which the server may stop with an error. (Trigger Player functions called from start: fixed 2026-10-30, they run for each player.)
15. Host status is read once, when you first spawn, so a new Host has to reconnect before loading main-world sets.
16. ~~Messages show channels as 0-30~~ (channels are gone since 2026-10-30).

Open questions for the rework

These decide how the new SandboX should behave. Answer in the comments below, by number:

1. Who may load, unload and delete main-world sets?
2. Should Player Allies / Enemies and the team targets work properly? What should "allies" and "enemies" mean in a Free for All?
3. ~~Should one event be able to call several things?~~ Yes, since 2026-10-30: every call on a condition runs. Should checkpoints and pickups fire once, or every time?
4. Should saving overwrite your own file (after asking)?
5. The start has no trigger player. Should it be the person who loaded the set, or each player as they arrive? What should players who join later get, for every function type?
6. Should sets run in party worlds, event worlds and races too?
7. Should teleports, checkpoints and vehicles keep their interior?
8. Do you still want Create Object, Launch Player and Boost Player? What exactly should they do?
9. When the owner leaves or types /myworld again, should the set unload, keep running for visitors, or ask?
10. May the file format change (a version number, sound positions, commas in dialogue)? The 83 existing files would be converted.
11. Keep the editing chart, the "SandboX Editing Mode" badge and the Discord log?
12. Are the limits right (49 sets, 99 functions, 199 calls, 20 camera positions, 120 s timers)?

All SandboX commands