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 only the relevant StartPos snapshot or section when sharing map-specific setups.

​
StartPos Safety

StartPos is Akron’s built-in workflow for saving and restoring room positions. Each StartPos snapshot stores the full room state - not just coordinates - so repeated attempts start from the intended setup. If StartPos restore is blocked, check the visible policy status, the map compatibility settings, and whether the saved snapshot belongs to the current map and room. 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.