What problem does it solve?
This workflow helps MCC maintainers adapt the Minecraft Console Client to new Java edition releases by updating palettes, protocol mappings, entity metadata, block shapes, and routing logic to prevent ID shifts, metadata parsing errors, and packet mismatches that break connectivity or in-game correctness.
Core Features & Use Cases
- Authoritative registry generation: produce registries.json, blocks.json and packets.json from the server jar to obtain runtime protocol IDs.
- Registry diffing and palette generation: compare decompiled sources and server reports to generate updated Item, Block, Entity, Packet and EntityMetadata palettes as C# files.
- Routing and protocol updates: update Protocol18 constants, palette routing switch expressions, packet palettes, and version mappings across the codebase.
- Asset regeneration: regenerate block collision shapes, minimap color maps, and entity category mappings when block/entity sets change.
- Validation and compilation: build the solution and validate against a local test server to confirm no ID shifts or metadata parsing failures.
Quick Start
Generate server reports from the target server.jar, run the registry diff script to identify palette changes, run the appropriate gen_* tools to produce new palette files, update protocol routing constants, then build and test against a matching test server.
