Skip to main content
Akron setup state stores options, bindings, StartPos slots, and scoped tool settings for the current play context. .akr files are the shareable archive format Akron uses for setup packs and other structured data.

Setup State

Use separate setup packs for different goals so state-changing tools do not bleed into clean-play or accessibility setups. For most players, the practical choice is the setup pack or overlay section they are importing. The Akron overlay shows current policy/status state and tool state. It also supports .akr import/export for backing up or sharing the whole setup or a scoped section.

.akr Files

An .akr file is a strict ZIP archive with a manifest and one payload. Current setup packs use a setup.json payload, which is the archive entry name for setup data.

Scoped Sections

Akron can export and import a whole setup or a focused section: Scoped imports merge only the selected section into the current active settings. Unrelated settings are not affected.

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.
  • Keep a backup export 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.