Skip to content

Changelog

All releases so far are development releases for invited testers. Dates are the dates the builds were made.

0.2.2 built, not published yet

2026-09-18. A draft release. It is not offered to anyone yet. It contains everything that was prepared as 0.2.1, which was never published and was superseded, plus automatic updates.

Launcher

  • Automatic updates. With a valid access key, a new release is downloaded and verified in the background. It installs when you close Xol, or when you press Restart and update. It never installs while Minecraft runs. See Updates.
  • macOS: the verified disk image is mounted, Xol.app is copied next to the running app and checked (bundle identifier, version equal to the signed version, code signature). Installing is two renames and a restart. The previous app is removed at the next start.
  • Windows: the installer runs silently and restarts Xol.
  • New setting: Settings ▸ Service ▸ Update automatically, on by default.
  • A Mac copy that cannot replace itself (translocated, run from the disk image, or in a read-only folder) says why and falls back to opening the disk image.
  • No capsule badges anywhere. States are plain text: "experimental" shows as Preview, unsupported profiles are hidden from the picker, and verified and available profiles carry no label.
  • Profile notes rewritten in plain language (profile manifest revision 3).
  • Smoother transitions: pressed states, a cross-fade when the selected profile changes, eased progress.
  • A branded disk image window on macOS. How it looks has not been confirmed on a Mac yet.
  • The Xol service is now reached at xol.dev. Installs of 0.2.0 keep working against the previous address.
  • The application identifier changed to dev.xol.launcher. On Windows, an installation that started with 0.2.0 keeps a second uninstall entry.

Known limits

  • Going from 0.2.0 or 0.2.1 to 0.2.2 is still the manual hand-over, because the updater that runs is the old version's. Automatic from 0.2.2 onwards.
  • The self-update path was proven on automated macOS 14 and Windows Server 2022 build machines. The full loop from a running, installed copy on a user's Mac has not been observed; that needs 0.2.2 installed and a later release published.
  • Linux: no automatic update, because no Linux build exists.

The in-game client is unchanged at 0.2.0.

0.2.0 development release

2026-09-18. Published to testers, with signed release metadata.

Client 0.2.0

  • 13 modules, of which only FPS is on by default: FPS, Ping, Coordinates, Session timer, CPS, Keystrokes, Armor and held item, Potion effects, Toggle sprint, Zoom, Custom crosshair, Resource packs, Chat appearance.
  • Typed settings: on or off, whole and decimal numbers with ranges, choices, colours, keys.
  • Settings file schema 2, with migration from schema 1.
  • HUD layouts, and settings export and import.
  • A settings screen with search, opened with Right Shift.
  • A HUD editor: drag, scroll to scale, snap guides, re-anchoring, reset.
  • Checked in a running game on 1.8.9 (GUI scales 1 to 3) and 1.7.10. Parts that are compiled and unit-tested only are listed on The client.

Launcher 0.2.0

  • Self-update with manual hand-over: signed metadata, verified download, then the Windows installer starts or the macOS disk image opens. Keeps the last two installers. A signed "mandatory" flag can block Play.
  • Xol access key, sealed by the operating system.
  • Announcements strip.
  • Consent-gated crash reports with a preview.
  • Offline line at the top of the main screen.
  • OptiFine profiles that take a file you import. A launch with real OptiFine is unverified.
  • Remote profile manifest and remote configuration, both fail-soft: if anything is wrong, the launcher keeps what it has.
  • Instances created by 0.1.0 move to the 0.2.0 client jar automatically. The old managed jar is retired; your files are untouched.

0.1.0 first development release

2026-09-18. The first packaged installers.

Core

  • Official install of Minecraft: libraries, assets and natives, verified by SHA-1.
  • Mojang's jre-legacy Java runtime, installed and verified.
  • The game is started with an argument list, never through a shell. Process monitoring. Repair by re-running the install.
  • Legacy Forge for 1.8.9 and 1.7.10, from an installer pinned by SHA-256 that is never executed.
  • Profile manifests with validation, isolated instances, and presets merged into options.txt.
  • The Microsoft sign-in chain (PKCE in the browser, Xbox Live, XSTS, Minecraft Services, entitlement and profile, refresh, sealed account store). Implemented; not yet run against Microsoft, because it needs an approved application ID.
  • Signed release metadata: Ed25519, pinned keys, a replay-proof sequence number, authorised rollback.

Client 0.1.0

  • HUD modules: FPS (on by default), Ping, Coordinates and Session timer (off by default).
  • Per-instance JSON settings with a schema and migration.
  • The client brand Xol.
  • Xol 1.7.10 with the pinned stack: UniMixins, GTNHLib, Hodgepodge, ArchaicFix.

Launcher 0.1.0

  • Account button, profile picker, presets, Play, Cancel and Stop with real progress, settings, Repair and Clone, a redacted support log.
  • Installers: Xol-0.1.0-macos-arm64.dmg, Xol-0.1.0-macos-x64.dmg, Xol-0.1.0-windows-x64-setup.exe. Unsigned; on macOS ad-hoc signed only. Checked on automated build machines: the disk images mount, the apps have the right architecture and start; the Windows installer installs and uninstalls silently and keeps the instances folder. No Minecraft launch was done on those machines.