Skip to main content
Akron gameplay tools help with routing, learning, and map inspection. Using many of these tools marks the active attempt as Cheat because they change state, timing, position, or execution.

Common tools

Room-lab workflow

1

Use a non-submission setup

Use a setup intended for state-changing tools before enabling room-lab features. This keeps the attempt indicator accurate.
2

Choose the right tool for the job

Use StartPos for repeated room or state-specific routing. Use Room reload for quick reset loops. Use Chapter reload when a full chapter restart matches the intended clean workflow.
3

Watch the status indicator

State-changing tools - StartPos restore, Room reload, frame tools, and timescale - mark the active attempt as Cheat. Check the status label before resuming a clean attempt.
4

Keep exports scoped

Export the StartPos section when sharing map-specific StartPos setups. It includes every saved StartPos slot for the target map.

StartPos safety

StartPos is Akron’s built-in workflow for saving and restoring room positions. Each StartPos snapshot stores the player coordinates and runtime room state. Loading it restores room state but does not rewind cumulative time or death statistics. If persistent StartPos Load is unavailable, wait for capture to finish and check the current map and save-file slot, snapshot presence and integrity, and runtime or mod-set compatibility. Current Map Compatibility broker and unsafe-native settings apply only to the separate Capture/Restore StartPos State savestate bindings. The saved room is the restore destination, so the current room can differ. See StartPos recovery for recovery guidance.

Input shortcut caution

Shortcuts that synthesize or modify execution inputs are Cheat. This includes input-assist shortcuts such as Neutral Drop and Backboost. Check Clean vs cheat classifications before binding a shortcut for submitted-run use.