mcc-dev-workflow

Build, run, and debug Minecraft Console Client against a local Java server.

2.1k|471|Updated Jul 18, 2013
One-click install
npx skills add https://github.com/MCCTeam/Minecraft-Console-Client --skill mcc-dev-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcc-dev-workflow
Source: https://github.com/MCCTeam/Minecraft-Console-Client/tree/main/.skills/mcc-dev-workflow
Command: npx skills add https://github.com/MCCTeam/Minecraft-Console-Client --skill mcc-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mcc-dev-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug the Minecraft Console Client against a local Minecraft Java server?

To debug the Minecraft Console Client against a local Minecraft Java server, use a tmux-scoped session to compile MCC, start the server, and launch the client for reproducible end-to-end validation. This workflow captures concrete logs for login, protocol, and command behavior.

What tools do I need to run an end-to-end Minecraft Console Client debug session?

An end-to-end Minecraft Console Client debug session requires Java, tmux, python3, and dotnet. The workflow performs preflight checks for these tools to ensure builds, temporary configs, and server lifecycles run correctly on Linux, macOS, or WSL.

How do I manage shared server and isolated client sessions when debugging MCC?

Managing shared server and isolated client sessions involves keeping mc-* server tmux sessions shared while isolating MCC debug sessions per worktree or named session. This avoids cross-run interference during end-to-end validation.

Can I validate Minecraft protocol and login behavior locally without guessing from static code?

Yes, you can validate Minecraft protocol and login behavior locally by running MCC against a real local server. The workflow generates temporary configs and captures MCC and server logs, providing concrete evidence instead of relying on static code analysis.

Why does my Minecraft Console Client session fail to connect after the server logs the Done line?

A Minecraft Console Client session may fail if RCON is not ready despite the server logging the Done line. The debug workflow provides resilience guidance to retry RCON connections and wait for full server readiness before launching the client.

What is the best way to capture logs for postmortem inspection during a Minecraft Console Client debug run?

The best way to capture logs during a Minecraft Console Client debug run is to use the tmux-scoped session's documented capture commands. This records both MCC and server logs, and uses /debug state for diagnostics to enable thorough postmortem inspection.