Sandbox variables and condition keys

Use this page as the exact-key lookup beside the Sandbox event editor. For the full workflow—placing nodes, connecting actions, testing retries and saving maps—start with the Sandbox editor field guide.

Version check: this reference covers v0.65.0. A newer build may add choices. The keys shown by that build's Condition editor are authoritative.

Author-defined map variables

A Map Variable node uses a numeric key that you define. A Condition reads the same value with a var. prefix:

Variable node key: waves_seen
Condition metric: var.waves_seen

Keys match [A-Za-z_][A-Za-z0-9_]{0,31}: 1–32 ASCII letters, digits or underscores, beginning with a letter or underscore. Values are finite numbers from -1,000,000,000 through 1,000,000,000.

Set replaces the value. Add adds to it, treating a missing key as zero. Results are clamped to the supported range. Conditions compare with >=, >, ==, !=, < or <=, combining up to eight checks with ALL or ANY.

Variables last only for the current attempt. Retry, Reset Map and a fresh Fly entry clear them. They never change lifetime profile stats and cannot contain scripts or expressions.

Useful examples include waves_seen / var.waves_seen, stage / var.stage, doors_opened / var.doors_opened and hazards_fired / var.hazards_fired.

Current-run metrics

These values reset with the attempt:

Every enemy family supplies an attempt-local and a lifetime kill counter:

Pickup and collectible metrics

These counters also reset with the attempt:

Lifetime profile metrics

These are read-only lifetime values. Do not use them to gate a fresh player's required path; reserve them for optional veteran branches or secrets.

The per-enemy lifetime keys are listed beside their run equivalents above.

Achievement metrics

An achievement metric reads as 1 when earned and 0 otherwise:

Defense and dynamic keys

The fixed defense metrics are available to every map, but read as zero when no shared Custom defense scenario is active:

Each authored Core node adds defense.core.<core_id>, such as defense.core.relay_alpha, for its current health. A core ID is 1–48 letters, digits, underscores or hyphens. This family is dynamic because its IDs come from your map, just as var.<key> comes from your Variable nodes.

Choose the right scope

• Use run.* for the current attempt.
• Use profile.* only for optional branches based on lifetime progress.
• Use var.* for authored stage, latch and counter state.
• Use defense.* for core and assault state.

A Map Note disappearing, a Timer expiring or an author note existing does not change a numeric variable by itself. Connect the real event output to a Variable action when you need state to change.

For examples of event sources, actions, connection limits, reset behavior and testing, continue in the Sandbox editor field guide.