mcc-dev-workflow

What problem does it solve?

Provides a reproducible, end-to-end development workflow to build, run, and debug the Minecraft Console Client (MCC) against a real local Minecraft Java server so developers can validate login, protocol, command, movement, inventory, and entity behavior with concrete log evidence instead of guessing from static code.

Core Features & Use Cases

• One-step debug session: mcc-debug handles build, temp config generation, server startup, and MCC launch in a tmux-scoped session for fast iteration.
• Shared server / isolated client sessions: Manage shared mc-* server tmux sessions while keeping MCC sessions isolated per worktree or named session to avoid cross-run interference.
• Preflight & resilience: Preflight checks for Java, tmux, dotnet, and python3, plus guidance to retry RCON and wait for server readiness beyond the Done line.
• Repeatable and RAM-optimized builds: Support for tmpfs build routing and temporary configs to keep runs repeatable and non-destructive.
• Log evidence & debugging commands: Captures MCC and server logs, uses /debug state for diagnostics, and documents capture commands for postmortem inspection.

Quick Start

Source the repository's tools/mcc-env.sh, start a local 1.21.11 server, run mcc-build, then run mcc-debug with a temporary session and verify a successful join and an inventory command response.