Skip to main content
Akron exposes developer-facing console commands through Everest’s debug console and DebugRC. These commands route into Akron’s runtime services and exist for QA, live verification, and automation.
Debug commands are not a player-facing UI. Player-facing documentation covers overlay rows and Everest mod options. Commands serve development, testing, and controlled verification contexts only.

Exposure Levels

Common UI Mirrors

Command-Only or Automation-First

Extended Gameplay Commands

Camera and Visual Commands

Hitbox and HUD Commands

Input and Utility Commands

Setup, Theme, and Settings Commands

Community Pack Commands

list prints the currently filtered zero-based entries. import downloads the selected .akr and imports it through the same scoped path as the in-game button.

File-Backed Automation Queue

When DebugRC’s /console endpoint is unreliable, Akron can process a file-backed queue on the game thread. Akron executes one command per frame so structural actions such as load or room transitions do not stack unsafely inside a single update.

Verification Scenarios

Commands support repeatable live verification scenarios:
  • Show the overlay before screenshots.
  • Drive settings without relying on fragile input.
  • Exercise StartPos, freeze, hitbox, inspector, and proof surfaces.
  • Refresh and import community packs.
  • Capture proof sidecars for comparison.
Command-only controls should not appear in player tutorials unless a normal UI path exists first.