Skip to main content
Akron uses Everest’s keyboard and controller configuration for binds. Use these configuration screens to ensure bindings remain consistent with your modded Celeste setup.

​
Default Keybindings

Actions marked - have no default binding on that input type. Open Menu starts on Tab; Click Teleport, Cursor Zoom, Cursor Tools, and Entity Inspector cursor hold default to Left Alt where their popup exposes a cursor bind. Other shortcut actions start unbound so you can assign them intentionally.

​
Configure a Bind

1

Open Everest controls

From Celeste’s mod options, open the Everest keyboard or controller configuration screen.
2

Find the Akron action

Search or scroll to the Akron action you want to change, such as the overlay toggle, retry, StartPos set/load, freeze, hitboxes, or inspector actions.
3

Assign the new input

Bind the key or controller input. Avoid using inputs already mapped to Celeste movement, pause, confirm, or other critical mod actions.
4

Test in a non-submission context

Test the bind in casual or room-lab play before using it in a clean or proof-oriented attempt.

​
Keyboard and Controller Inputs

Akron uses Celeste/Everest binding primitives where possible:
  • Built-in Akron hotkeys use Everest ButtonBinding settings.
  • Overlay row custom bindings accept keyboard chords such as LeftControl+LeftShift+D.
  • Binding capture preserves side-specific modifiers such as RightAlt, RightShift, and RightShift+F1.
  • Overlay row custom bindings can also use controller buttons, stored with an explicit value such as Button:LeftShoulder.
The binding capture popup accepts a keyboard key or a controller button. It waits for the input that opened capture to be released so a held button does not bind itself accidentally. Controller bindings display with controller-facing names such as LB, RB, and DPad Left. Multi-button controller combinations are not part of the current binding model.

​
Bind Recovery

If the overlay bind is unknown:
  • Open Everest controls from Celeste’s menus and search for Akron actions.
  • Temporarily disable other mods if a bind conflict prevents input from reaching Akron.
  • Check Everest logs if the bind appears configured but Akron never receives it.
Some shortcut actions are policy-visible. A convenient bind can still mark the active attempt if it uses a Cheat feature. See Clean vs cheat for details.