This guidance is for players who are new to Robot Arena. It is not a full block catalog. Instead, it focuses on rules that are easy to miss in the UI: yaw angles, event priority, sensing monitors, rollback, accessory unlocks, capture zone logic, and match resolution.
Hover over accessory cards or blocks to see descriptions, return values, default parameters, and equipment requirements. Many answers to “why can’t I use this block?” or “does this sensing block return true/false or a number?” are hidden in hover tooltips.
Some action blocks require matching accessories before they unlock. If your Power exceeds the limit, the program will not start. The monitor in the top-left of the Accessories page shows Move Cd, Rotate Cd, Fire Cd, Max HP, HP, and Damage.
Turn on monitors for key sensing blocks, then use << 3 to return to the moment before a mistake and edit the logic. It is much faster than restarting blindly.
Once you understand these rules, your strategy becomes a debuggable robot program instead of a pile of blocks.
Some reporters and actions use start-axis yaw: 0-360 degrees measured from the line between the robot’s own starting position and the enemy starting position. Be careful to distinguish Rotate 90 from Point Towards 90.
Rotate takes a relative rotation angle: how many degrees to turn from the current heading. Point Towards takes a start-axis yaw: the exact arena-relative direction to face. In other words, running Rotate 90 twice accumulates two turns; running Point Towards 90 twice usually changes nothing the second time.
A yaw of 0 points toward the enemy starting position. The same yaw is applied from each robot’s own starting axis, so if both robots run Point Towards 9, they face opposite world directions rather than the same global direction.
Combining Direction To nearest enemy with Point Towards lets the robot dynamically face an enemy, a wall, or the map center, because Direction To also returns a start-axis yaw. The weapon block Aim At angle uses the same angle semantics for the cannon.
Some sensing blocks return true/false, while others return numbers. You can enable their monitor in the palette to display live values during the match. If a sensing block has dropdown options, and the workspace contains the same sensing block with different options, enabling the monitor will show multiple monitors, one for each option.
Enemy In View? does not simply mean “the enemy is on screen.” It is true only when all of these conditions are met:
Therefore, it returns false if the enemy is close but behind you, or if the center wall blocks the direct firing line. A common pattern is to check Enemy In View? before running Aim At Enemy and Fire.
When condition P=2 runs the chain below it when its condition triggers. It is not a normal if block; it is an event. It can interrupt the main chain, and it can also interrupt lower-priority event chains. Higher P values mean higher priority.
After the high-priority event chain finishes, execution returns directly to Robot Start. It does not resume at the block after the interrupted block. This makes events great for emergency reactions such as dodging bullets, escaping the map edge, or pushing back when touching the enemy. Do not put every normal behavior into events, or the main chain will be reset constantly.
When you save a void in MY VOIDS, the game saves the logic currently connected from Robot Start in the workspace, including blocks nested inside loops and conditions. After saving, a Call Void name block appears and can be reused in the main program or other branches.
Treat voids as tactical action snippets: briefly routing around a wall, aligning before capture, or executing an attack sequence after the enemy enters view. Avoid recursive self-calls; recursive calls are skipped at runtime to prevent infinite nesting.
Press << 3 while the program is running, and the game will try to return to the match moment from three blocks earlier. After rollback finishes, you can edit the block program. The rollback point turns pink, marking it as the resume anchor.
The pink rollback point cannot be deleted. When you click Run again, the program does not restart from the initial Robot Start state. It resumes from the match moment represented by the pink anchor, preserving robot positions, enemy position, and remaining time from that rollback point.
If the target rollback point is near a fall or another unsafe state, the game will look for a safer runnable rollback point. If it cannot find one, it will report that rollback is unavailable.
Stop the program, then click IM/EXPORT in the top-right corner. export saves the current block design as JSON. import for my robot imports a JSON strategy for your robot. import for enemy imports it for the enemy, which is useful for matchup testing.
Use clear file names for exported JSON, such as zone-control-v2.json. Make sure the current program is stopped before importing so you do not modify state mid-run.
Accessories affect speed, health, weapons, special abilities, and whether some action blocks are usable.
Wheels accessories control Move Cd and Rotate Cd. Lower values mean faster movement and turning. Equipping any wheels accessory enables Move, Rotate, and Point Towards.
Weapon accessories unlock Fire, Aim At Enemy, and Aim At angle. Aim At angle uses the same start-axis yaw rule as Point Towards. Turning on Fire Assistance enables the weapon range display and laser aim line, which are useful for debugging range and bullet paths.
Armor increases Max HP and does not directly unlock new blocks. Heavier armor improves forgiveness, but it consumes Power, so it must be balanced against weapons and mobility.
Radar accessory tooltips mark it as unlocking sensing and reporter-style blocks, such as distance, direction, health, contact, bullet range, and capture-zone state readings. In the current version, these sensing blocks can still be placed in the workspace, but players should treat radar as the main entry point for reading the environment and use monitors to debug live values.
Bouncer unlocks Activate Bouncer. When activated, it applies radial knockback to nearby enemies. The effect weakens with distance, has a cooldown, and is skipped while on cooldown. It is useful for pushing enemies out of the capture zone, toward the map edge, or out of close-range pressure.
Freezer unlocks Activate Freezer. When activated, it applies a temporary slow effect to enemies within range and also has a cooldown. It pairs well with chasing, capture-zone defense, and avoiding enemy rams.
Every weapon defines a max range (meters) and a linear falloff curve. Within the falloff start distance, bullets deal 100% base damage. Beyond that, damage decreases linearly with distance traveled — the farther the shot, the less it hurts. At max range, damage reaches a configurable minimum multiplier (e.g., 20%). This system rewards closing the gap and makes long-range sniping ineffective unless the weapon is built for it. Check weapon stats in the Accessories tab to understand each weapon's effective engagement envelope.
The center zone is a one-time objective: once captured, the other side cannot take it back.
One robot enters the center capture area while the opponent is outside the capture area.
If it stays alone for more than 5 seconds, the capture succeeds.
If the opponent enters the capture area during that time, the capture attempt fails and progress resets.
Once either side completes the capture during the match, ownership is locked and cannot be stolen.
Resolution order matters: death first, capture second, then damage comparison.
A robot can die from bullet damage, or by being pushed off the map edge, or by driving off the edge itself. If both robots die at the same time, the match is a draw.
If either side has successfully captured the zone and both robots are still alive, the capturing side wins.
If neither robot died and nobody captured the zone, the side that dealt more damage wins. Equivalently, the side that took less damage wins.
If neither side lost health, or both sides lost the same amount of health, the match is a draw.