Hero Client · Roadmap

Phase 1 is done. Here's the path to parity.

Roadmaps communicate intent, not promises. Shipped means shipped, planned means planned — untested work is never listed as done.

Phase 1 complete — v2.2 5 phases 125 features tracked See what shipped →

Complete Phase 1 · v2.2 · 2026-09-30

Multi-version + full GUI

Ship real builds for every supported Minecraft release, and a GUI that makes 125 features usable.

10 deliverables shipped — every one tested.

In progress Phase 2 · in development

Feature parity

Complete all 200 specification documents across the 15 modules — the full parity pass.

115 of 125 registry features already live.

Phases

The plan, phase by phase

Each phase has a single job. Nothing moves forward until the phase before it is actually done — which is why Phase 1 shipped with 125 real features instead of a promise.

Complete

Phase 1 — Multi-version + full GUI

2026-09-30 10 deliverables

Ship real builds for every supported Minecraft release, and a GUI that makes 125 features usable.

Multi-version builds for all 17 Minecraft releases (1.21 through 26.3)
Command framework — parser, namespaced registry, completion engine, middleware pipeline
Config validators with range, enum, TTL cache and diagnostics
Performance engine — real FPS, average FPS, 1% low, frametime monitor, CPU/memory dashboard
Six accessibility features wired end to end with a settings screen
HUD editor — drag-and-drop, snap-to-grid, grid overlay, JSON persistence
Keybind editor — click-to-rebind, conflict detection, per-row reset
Mod menu rewrite — category tabs, live search, feature card grid with toggles
Settings screen rewrite — seven sections
125 features across 16 categories — every one implemented

In progress

Phase 2 — Feature parity

4 deliverables

Complete all 200 specification documents across the 15 modules — the full parity pass.

Close the gap between the shipped registry and the complete 200-spec set
AI assistance (BYOK) across six providers
Cosmetics and marketplace completion
Per-module documentation for every parity feature

Planned

Phase 3 — Per-version CI/CD

3 deliverables

Automated builds for every supported Minecraft version — no manual release choreography.

Automated per-version build pipeline for all 17 releases
Checksum publishing and release-note generation
In-game update notifications wired to the release channel

Planned

Phase 4 — Ecosystem integration

3 deliverables

Deep integration with HeroSync, Hero Agent and DPT — one ecosystem, not a collection of mods.

HeroSync latency compensation as a first-class Hero Client module
Hero Agent as the AI backbone for every AI feature
DPT ecosystem theming across Hero Client and the mod suite

Later

Phase 5 — NeoForge support

2 deliverables

Bring Hero Client to NeoForge without a rewrite, via the Platform SPI.

Platform SPI abstraction over loader-specific code
NeoForge builds alongside the Fabric matrix

Feature parity timeline

From alpha to the full registry

The honest record — what shipped, when it shipped, and what is next. Dates for past releases are the real release dates from the changelog.

0.1.0-dev — alpha

2026-07-21

Modular client with 50+ toggleable features, HUD suite, keybinds and the mod menu. The 16-version build matrix begins.

2.1 — stabilisation

2026-09-28

Launch crash and mixin crash fixed. 3,800+ tests passing across all modules — the first build that launches clean on a fresh install.

2.2 — Phase 1 complete

2026-09-30

All 17 Minecraft releases, the full GUI (mod menu, settings, HUD editor, keybind editor), command framework, config validators and the performance engine. 125 features across 16 categories.

Phase 2 — feature parity

Now

Closing the gap to all 200 specification documents across the 15 modules, including BYOK AI assistance.

Phase 3 — per-version CI/CD

Automated builds, checksums and release notes for every supported Minecraft version.

Phase 4 — ecosystem integration

HeroSync, Hero Agent and DPT wired directly into the client.

Phase 5 — NeoForge

Later

NeoForge builds via the Platform SPI — same features, same quality bar.

In the ecosystem roadmap

Hero Client across the whole studio

Hero Client is one product in one ecosystem — these are the ecosystem-level items that touch it.

Hero Client multi-version

Real per-version builds instead of relabelled jars.

See the full ecosystem roadmap at /roadmap — Hero Play, CraftPilot, Hero Agent and the rest.