Configuration order
1
Open the overlay
Use Akron’s overlay as the main player-facing control surface. Confirm the current status and active tools before changing individual options.
2
Review the feature badge
Check each feature’s policy badge before enabling it. The badge shows how Akron classifies the feature, and the attempt status shows the highest classification recorded during the current attempt. These indicators do not grant or deny permission to use a feature.
3
Set overlay behavior
Configure overlay scale, opacity, pause behavior, search behavior, and visual defaults so the UI is usable in your setup.
4
Enable specific tools
Enable only the tools needed for the current workflow. Keep state-changing features out of submitted-run setups.
5
Export the setup
Export the current setup as a
.akr pack once it is stable, especially before sharing settings or testing options classified as Cheat.Import and export
Use.akr setup packs to save and share configuration. You can export the whole Akron setup or a scoped section such as StartPos, keybinds, Auto Kill, Auto Deafen, recorder settings, audio settings, or HUD settings.
See Import and export .akr packs for the workflow and Akron .akr archives for the reference contract.
Safety defaults
Keep these defaults unless you know why you need a different setup:- Keep submission-oriented workflows in explicit proof-specific setups.
- Keep StartPos restore, warps, hitboxes, entity inspection, and timescale inside explicit room-lab or testing setups.
- Export the current setup before importing community packs.
- Treat Cheat feature use as attempt-changing even if the feature is later disabled.