Skip to main content
Install Akron into an existing Celeste + Everest setup and verify that the mod loads correctly.

​
Requirements

You need:
  • Celeste with Everest installed.
  • Access to the Celeste Mods directory used by that Everest install.
  • The current Akron release, available through Olympus or the project’s public release page.
Install Akron into the same Celeste/Everest environment you intend to launch. A second Steam, Flatpak, or Wine prefix can have a different Mods directory.

​
Install with Olympus

Use Olympus for the fastest and easiest installation.
1

Close Celeste

Close the game before changing installed mods.
2

Open the Olympus install link

Use the Akron one-click install link:
3

Install Akron

Let Olympus download Akron into the active Everest Mods directory.
4

Launch Celeste through Everest

Start the same Celeste install that Olympus targets.
5

Check the mod list

Open Everest’s mod list and confirm Akron appears as an enabled mod.

​
Install from a release archive

Use this method if Olympus is unavailable or if you are testing a specific release archive.
1

Close Celeste

Close the game before changing files in the Mods directory.
2

Download the archive

Download the current Akron archive from the raw download link:
3

Copy the Akron archive

Put the Akron release archive, usually named Akron.zip, directly inside the Everest Mods directory. Do not unzip the archive unless a release explicitly tells you to.
4

Launch Celeste through Everest

Start the same Celeste install that owns the Mods directory you changed.
5

Check the mod list

Open Everest’s mod list and confirm Akron appears as an enabled mod.

​
Confirm Akron loaded

After launch, continue to First run. The first-run check confirms that the overlay opens, status is visible, and Akron can read its settings.

​
If Akron does not appear

  • Confirm the file is in the active Everest Mods directory.
  • Confirm the archive has the correct release name and contains an everest.yaml manifest at its root.
  • Check Everest logs for missing dependencies or load errors.
  • If the installation uses Steam Flatpak, Wine, or a custom prefix, verify that the directory you copied the archive into is the directory used by the runtime.
See Compatibility for platform-specific diagnosis.