🚀 Espectral Client: why it opens Minecraft faster

⚡ The AOT moat: why booting is the bottleneck

Every time stock Minecraft starts, the JVM loads thousands of classes and the JIT compiler has to profile and compile that bytecode from scratch — before you even see the main menu. That warm-up is the real cost of launching the game, not your hardware.

Project Leyden — started by Mark Reinhold in April 2020 to bring ahead-of-time compilation to the Java platform — lets the JVM record that startup work once and replay it on later boots from a pre-linked AOT cache (game.aot). The JEPs that make it possible:

One training run pays for every later boot: the JVM skips the class-loading work it already recorded in game.aot.

🧩 Not a native image

The AOT cache is not a GraalVM-style native image of the game. The JIT compiler still runs normally while you play, so in-game performance behaves exactly like stock Minecraft.

• Mod-compatible: loaders and mods keep working because the game still runs on a full JVM.
• Startup-only win: the cache accelerates class loading and resolution at boot, nothing else.
• Easy fallback: delete the cache and the game boots exactly as before — just slower.

⚙️ How the Client uses it

The Client fully automates the AOT lifecycle. On the first boot it launches the game in training mode to record the cache:

-XX:AOTCacheOutput=<cache>/game.aot

On later boots it replays that cache instead of re-doing the class-loading work:

-XX:AOTCache=<cache>/game.aot

• Warns and plays without cache: if the cache is missing or invalid, the Client warns you and still launches the game normally.
• Re-trains after you close the game: since version 1.3.7, the Client refreshes the cache after the game closes so everyday boots reuse a fresh cache.
• Needs a modern runtime: the AOT cache requires a JDK 25 runtime — the reason the Client ships and manages JDK 25 itself. Loaders still running on Java 21 don't use it.

🧱 Three-layer architecture

The Client is split into three cooperating layers so each one does what it is best at:

• The game is launched with -XX:-UsePerfData to keep JVM monitoring overhead out of the way.
• All local data lives under %LOCALAPPDATA%\espectral-client (instances, versions, per-instance AOT caches, settings).

🔒 Trust: verify it yourself

A launcher runs executables on your PC — it should earn that privilege. The Espectral Client is fully open source: releases are built by a public, tag-gated CI, and build artifacts ship with Sigstore attestations so you can confirm a binary really came from the published source.

Verify any installer checksum with Windows' built-in tool and compare it against the value published on the release:

certutil -hashfile <installer>.exe SHA256

SmartScreen note: the installer is unsigned, so Windows SmartScreen may show a warning on first run. That is expected for an unsigned open-source build — check the SHA-256 above and proceed if it matches.

❓ FAQ

• Does it raise my FPS in-game? No — the win is startup time. Once you are in a world, the JIT compiler runs exactly as in stock Minecraft, so FPS is unchanged.
• Does it work with mods? Yes. The AOT cache is not a native image: the game still runs on a full JVM, so loaders and mods keep working.
• What happens if the AOT cache is missing or corrupt? The Client warns you and launches the game normally without it — then re-trains a fresh cache (automatically since 1.3.7, after you close the game).
• Why does SmartScreen warn about the installer? Because the installer is unsigned. Verify the SHA-256 with certutil -hashfile against the published release value; the source and the tag-gated CI build are public.