Skip to main content
Use this page to quickly diagnose common problems before exploring platform-specific compatibility.

​
Akron does not load

Confirm the following:
  • The downloaded Akron .zip archive is located in the active Everest Mods directory. Its filename may include the release tag.
  • The game was launched using the same installation where you added the mod.
  • Everest has not disabled Akron due to a load error.
  • The Everest logs do not indicate missing dependencies or archive-shape errors.

​
Overlay does not open

Confirm the following:
  • The overlay hotkey is correctly configured in the Everest keyboard/controller settings.
  • There are no conflicts with Celeste’s native controls or other installed mods.
  • The overlay is not hidden, off-screen, or scaled too small to be visible.
If the overlay still does not open, rebind the key through Everest controls and check the Everest log for errors before seeking further diagnostics.

​
Feature is unavailable or changes status

Row tooltips show how a feature is classified, and attempt status records classified use. They do not grant or deny permission. A row can still be unavailable when it needs an active level, an external mod, a saved slot, or another runtime condition.
  1. Read the row value and tooltip for its runtime requirement.
  2. Confirm that the required level, external mod, slot, or input is available.
  3. Check the row and popup suboption tooltips for the classification Akron will record.
  4. Use a non-submission setup if the feature is expected to mark the attempt status as Cheat.

​
Import failure

Common causes for .akr import failures:
  • The file is not a valid Akron archive.
  • The archive contains missing or unexpected ZIP entries.
  • The manifest kind or version is not supported.
  • The payload exceeds the size limit.
  • The JSON payload is malformed or invalid.
  • The payload section does not match the requested import workflow.
See Akron .akr archives for the import contract.

​
Incorrect capture output

If a screenshot, room capture, map capture, or recorder output is missing or incorrect:
  • For screenshots, verify the output folder, filename template, capture mode, and resolution.
  • For room or map capture, verify the export path, image format, wait and offset values, and marker settings.
  • For recording, verify the output folder, filename template, codec, and FFmpeg path.
  • Disable Streamer Mode if you need to see detailed path information.
  • If recording reports that FFmpeg did not start, install FFmpeg or set AKRON_FFMPEG to the executable path.
  • Check if a timer-freeze or capture suboption has altered the expected behavior.

​
Community Packs shows no entries

Confirm the following:
  • You are currently inside the map for which you expect packs.
  • The catalog URL is reachable and online.
  • The category filter is not overly restrictive.
  • The search text is not filtering out the desired pack.
  • The catalog entry’s map SID matches the current map’s SID.

​
Room transitions or Speedrun Tool unfreezes hitch

Akron prepares a room’s StartPos restart baseline when Set first needs it, not on every room entry. That first Set can still take longer than later Sets. Normal Speedrun Tool loads reuse Refill Clarity textures instead of reading them back from the GPU on the first resumed update. The reusable Clarity cache holds at most 128 generated frames and 4 MiB of texture pixels. Source pixel buffers leave the cache when no cached variant needs them. Live refills and savestates may still own textures outside that cache; those textures remain valid until their owners release them. If a hitch remains, distinguish the initial save, the Load keypress, the first resumed frame, and an actual room transition in your diagnostic description. Those are separate operations and may have different causes.

​
Send diagnostics to a maintainer

Open Interface → Send diagnostics in Akron’s overlay. The Akron form has fields for a title, what happened, steps to reproduce it, expected behavior, and extra context. The combined report accepts up to 4,000 characters. Choose Send now to upload. If every field is blank, Akron asks you to confirm first. Opening the form does not upload anything. The report includes game, Everest and Akron versions, loaded mod names and versions, the current map and room, CPU, GPU, RAM, operating system and runtime. It also includes available tails of the game log, current and previous Akron logs, and the latest Akron performance recording. Each log is limited to 1 MiB; the complete upload is limited to 4 MiB. Akron redacts common credentials, local paths, usernames and computer names from automatic details and logs. Other mods may write personal text that these filters do not recognize. Your description is sent as written; do not include passwords or other private information. Saves and environment variables are not collected. The default destination is https://akron.micr.dev/uploads/diagnostics. Reports stay in private Cloudflare storage, not the public pack catalog. The service queues each accepted report for Akron’s private Discord channel #diagnostic-alert, where people with access can read the description and download the complete JSON report. After receipt is confirmed, copy the report ID for follow-up. The ID is not a public download link. Keep the menu open while sending. Closing it cancels the request, but cannot recall a report the server already received. The game does not retry uploads automatically. The service retries Discord delivery if it cannot confirm that an accepted report was posted; you do not need to send it again. If upload receipt is unconfirmed, a maintainer can check the report ID before you send another report. The game needs network access; an offline launcher sandbox can block uploads even when your browser connects normally.