Skip to main content
Akron setup state includes options, bindings, StartPos slots, and scoped tool settings. Akron also uses .akr archives for setup packs, overlay themes, HUD labels, and control-display presets.

Setup state

Use separate setup packs for clean play, accessibility settings, map inspection, and state-changing room-lab tools. The overlay shows the current attempt status and tool state. It can export the whole setup or one scoped section.

.akr files

An .akr file is a strict ZIP archive with a manifest and one main payload. Current setup packs use a setup.json payload. StartPos and Whole packs also contain one compressed v10 snapshot entry per saved StartPos.

Scoped sections

Akron can export and import a whole setup or a focused section: Scoped imports replace only the selected portable settings. StartPos imports also replace every slot for the pack’s target map while preserving slots for other maps. Setup packs keep machine-local paths, device choices, recording colorspace arguments, and the Auto Deafen hotkey unchanged. Setup packs created before akron-setup-v8 cannot be imported. Recreate the setup and its StartPos slots in the current build, then export a new pack.

Sharing guidance

  • Export only the section needed by the recipient.
  • Prefer scoped StartPos, Auto Kill, Auto Deafen, Recorder, or Audio packs over whole setup packs for map-specific sharing.
  • Export the current setup before importing community packs.
  • Treat imported attempt-changing options as policy-visible when used.
See Import and export .akr packs for the workflow and Akron .akr archives for the reference contract.