Skip to main content
Akron operates within the Everest Celeste environment. Compatibility issues typically arise from the active installation path, map-specific runtime behavior, availability of external tools, or platform-specific file locations.

​
Installation and Prefix Issues

If files are in the correct locations but Akron fails to load, verify the active runtime:
  • Steam and Steam Flatpak may utilize different filesystem roots.
  • Wine or Proton prefixes may isolate Celeste data.
  • Portable installations may use their own Mods and Saves directories.
  • Copied mod archives may reside in an installation folder other than the one currently being launched.

​
Map Compatibility

Some maps require conservative StartPos restore behavior. Akron provides per-map compatibility overrides for cases where standard StartPos restores are unsafe for a specific map. These overrides are located in the Everest Akron mod options under Current Map Compatibility. They serve as escape hatches for controlled testing and should not be used as standard recovery steps. If a StartPos restore is blocked:
  1. Verify the visible policy and status state.
  2. Review the map compatibility policy.
  3. Confirm that the saved StartPos belongs to the current map and room.
  4. Avoid using unsafe restore overrides unless you are intentionally testing that path in a non-submission setup.

​
External Tool Compatibility

Motion Smoothing’s current compatibility notes call out two cases that matter in Akron:
  • Fancy camera smoothing changes Celeste’s rendering pipeline and is currently documented as incompatible with auspicioushelper.
  • Dynamic framerate mode allows arbitrary FPS, but can conflict with mods that hook the main XNA tick path.
  • Interpolate object smoothing can add 1-2 frames of input delay, so Akron treats that selected value as “Cheat” even though the Extrapolate object-smoothing value is “Regular clean.”

​
Rendering and Capture

Visual verification is necessary for rendering-sensitive features, including overlays, hitboxes, camera, zoom, death transitions, room captures, map captures, and screenshots. If a rendering feature behaves inconsistently across different hosts, please document the host, platform, map SID, visible policy/status state, and Akron setup, and provide screenshot evidence before filing an issue.