Skip to main content
StartPos is Akron’s public workflow for restoring position and room state. It is designed to prevent the silent application of risky or mismatched restores.

​
StartPos Capabilities

StartPos captures position, room, map SID, facing, dash count, stamina, idle/grab state, and Akron-managed restore data whenever Akron can safely preserve it. Use the StartPos tab for player workflows: setting, loading, clearing, selecting a slot, mouse placement, and configuring respawn at StartPos behavior.

​
Why a StartPos Restore May Be Blocked

Akron may block or refuse a StartPos restore if:
  • StartPos restore safety prohibits the action.
  • The saved StartPos belongs to a different map SID or room.
  • The saved runtime state is unavailable or unsafe for the current map.
  • The current player state cannot be restored safely.
  • The action is state-changing and is marked under the active attempt status.

​
Recovery Steps

1

Verify Policy State

Confirm that no clean-run policy state is blocking the StartPos restore or other state-changing tools.
2

Use Non-Submission Setup

Switch setups only when the goal is room-lab routing, testing, or another “Cheat” workflow.
3

Verify the StartPos Slot

Confirm that the active StartPos slot is set, belongs to the current map, and was captured in the target room.
4

Review Map Policy

If a map is known to be risky, maintain the safe map policy instead of forcing unsafe restore behavior.
5

Document the Issue

If behavior remains incorrect, record the map SID, visible policy/status state, Akron setup, StartPos slot, logs, and provide screenshots.
Unsafe restore overrides bypass risk blocking and are marked as “Cheat.” Use them exclusively in non-submission setups; do not use them for submitted attempts.

​
Safe Mode Stat Guards

Safe Mode stat guards prevent selected local stat fields from being altered by guarded Akron sessions. Sub-options that freeze deaths, jumps, or best-run stats are considered “Cheat” because they mutate or protect tracked statistics.