Minecraft Modding (Java)

Consolidated on 2026-08-10 from the 12 temporary mc-* development skills (temporarily/skills/mc-*). This is the loader-agnostic workflow layer: it does not repeat content that dedicated skills in this repository already cover, so implementation topics link out to them instead.

This skill covers the shared Minecraft Java mod development workflow: establishing verified project context, adapting vanilla implementations, following a standard implementation and verification checklist, and diagnosing/fixing defects. It applies to Fabric, NeoForge, and Forge projects and is version- and loader-agnostic: always derive APIs from the pinned version and mappings, never from memory or generic snippets.

Standard Workflow

1. Audit the repository with core-project-context: exact Minecraft/loader versions, mappings, Java/Gradle toolchain, modules, registration style, side boundaries, and project conventions.
2. Find the closest vanilla or in-repo analogue with core-vanilla-reference; copy only patterns compatible with the pinned version and mappings.
3. Define observable behavior, server authority, persistence needs, and acceptance checks before editing.
4. Implement the smallest coherent vertical slice: registration, class/behavior, resource references, and initialization wiring. Register exactly once; keep client-only code out of common/server initialization.
5. Add only applicable assets/data: blockstates, models, loot tables, recipes, tags, advancements, and translations. Prefer data generation over hand-written JSON.
6. Keep every user-visible string in zh_cn, zh_tw, and en_us; derive Traditional Chinese naturally rather than copying Simplified Chinese.
7. Verify: compile/build, run data generation when configured, launch the narrowest relevant client/server test, and inspect logs rather than relying on exit code alone.

Core References