Hero Studios

Tutorial

HeroSync

Latency compensation that makes high-ping gameplay feel local.

Product page Downloads Documentation Roadmap

Install HeroSync #

Install Fabric Loader for 1.21 (plus Fabric API if the downloads page asks for it), place the JAR in your mods folder, and launch with the Fabric profile.

  1. Download the HeroSync JAR for your exact Minecraft version (1.21 → 1.21.11 published; 26.x experimental).
  2. Place it in your Fabric mods folder (Fabric API recommended) — nothing to install server-side, ever.
  3. Join any server — actions now feel responsive immediately; the reconciliation engine works silently in the background.
  4. Open the in-game settings screen to tune or disable individual features, or edit config/herosync.json (created after first launch).
  5. Press F3+L to toggle the debug overlay and confirm the framework is active on your current server.
  6. Use /herosync status and /herosync stats to inspect current state, transactions and per-tick cost.
  7. Run /herosync reload after editing config/herosync.json to apply changes without restarting.
  8. Keep the JAR matched to your Minecraft version for best results — 26.x builds are bundled-mappings and experimental.

Working with HeroSync #

Product-specific steps, separate from the general install guide above.

Install

HeroSync is **fully client-side** — no server mod needed. Drop the JAR for your Minecraft version (1.21 → 1.21.11 published, 26.x experimental) into your Fabric mods folder and launch. It starts already armed: actions register locally the moment you join a server.

What you'll see. No setup wizard. Join any server and actions respond immediately — the reconciliation engine works silently in the background.

What it actually does (and does not do)

HeroSync does **not** reduce your ping — it reduces what your ping feels like. Your actions register locally at zero perceived latency, then outbound and inbound packets are observed and reconciled against authoritative server truth. When the server disagrees, a dedicated **rollback engine** reverses only what needs reversing, backed by state **snapshots** for consistent rollback points.

What you'll see. On a high-ping server, movement and block interactions feel local instead of delayed — the rubber-band effect shrinks because your side responds instantly and only corrects when the server says so.

Command suite

Control and inspect everything from chat:

  • status — current framework state and enabled features.
  • transaction list — recent latency-compensation transactions.
  • registration info — which action types register locally.
  • stats — per-tick cost and reconciliation counters.
  • debug overlay — toggles the live diagnostics overlay (F3+L).
  • reload — re-reads config/herosync.json without a restart.
/herosync status
/herosync transaction list
/herosync registration info
/herosync stats
/herosync debug overlay
/herosync reload

Debug overlay (F3+L)

Press **F3+L** to toggle the live diagnostics overlay: latency compensation state, recent transactions and rollback activity. Use it to confirm the framework is active and to see exactly what it reconciled after a lag spike.

What you'll see. The overlay shows rolling latency-compensation telemetry — outbound/inbound reconciliation rows and rollback events, updating in real time.

Configuration (config/herosync.json)

Optional tuning lives in **config/herosync.json** — created after first launch or via `/herosync reload`. Individual features and the whole framework can be disabled from this file. It keeps a **sub-2ms per-client-tick** performance budget even when enabled.

Tips

  • Fabric API is recommended but the mod is client-side — nothing to install server-side, ever.
  • Shipped versions: r1.4.0 across 1.21 → 1.21.11 plus experimental 26.1 → 26.2 builds.
  • Built from 100 specification documents with a fully modular engine — read the docs page for the developer API.

Common problems

Actions feel rubber-banded
The server is disagreeing with local state — that is the reconciliation working. If it is frequent on one server, disable individual features via config/herosync.json or /herosync reload.
Server rules restrict predictive clients
Always check the server's rules. HeroSync never fabricates confirmations, but some communities restrict any predictive behaviour.
26.x build misbehaves
26.x builds use bundled mappings and are experimental — keep the build matched to your Minecraft version.

Folder locations by platform #

Platformmods / resourcepacks folderconfig folder
Windows%appdata%\.minecraft\mods · \resourcepacks%appdata%\.minecraft\config
macOS~/Library/Application Support/minecraft/mods~/Library/Application Support/minecraft/config
Linux~/.minecraft/mods · ~/.minecraft/resourcepacks~/.minecraft/config

MultiMC / Prism users: these folders live inside Instances/<instance>/.minecraft/. Match the build to your exact Minecraft version — the compatibility table in the docs lists every supported version.

Configure #

Settings live in the config folder (JSON5 files you can edit by hand) and, where available, in the in-game settings screen the mod adds. The exact keys and keybinds are listed in the documentation and the FAQ below.

Tips for HeroSync #

  • Keep HeroSync on the version range shown on its product page.
  • If it doesn't load, confirm the JAR is in the right mods folder for the launcher and version you chose.
  • Bedrock Edition, mobile, and console can't run Java Edition mods or packs — for a port or custom variant, request a commission.

HeroSync FAQ #

Does this work on servers without the mod?
Yes. HeroSync is client-side and requires nothing on the server.
Will it get me banned?
It compensates for latency like predictive clients do — it never fabricates confirmations. Always check server rules first; some communities restrict predictive behaviour even when it is client-side.
Which versions are supported?
1.21 through 1.21.11 plus experimental 26.x builds (26.1 → 26.2). Keep the build matched to your Minecraft version.
Does it change my actual ping?
No — it changes how lag feels by making your inputs register locally (0ms perceived delay), then reconciling with the server.
Can I turn it off?
Yes — individual features and the whole framework can be disabled from config/herosync.json, or tuned from the in-game settings screen.
How much does it affect performance?
It keeps a sub-2ms per-client-tick performance budget, even with everything enabled.
Is there a command interface?
Yes — /herosync exposes status, transaction lists, registration toggles, stats, a debug overlay (F3+L) and reload. Run /herosync status to see current state, /herosync transaction list to inspect recent transactions, and /herosync stats for per-tick cost and reconciliation counters.
Can other mods integrate with it?
Yes — it ships a developer API (HeroSyncAPI) with registration rules, packet classifiers, snapshot providers and compatibility adapters.
What happens when the server disagrees with me?
The rollback engine reverses only what needs reversing — backed by state snapshots for consistent rollback points — instead of rubber-banding your whole position.
Still stuck? Open a guided request — every message is tagged and answered from support@herostudios.dev. Always include your Minecraft version and product version.
← Previous
Default Yellow Theme
 Next tutorial →
J2B MC