minecraft-modding-workbench

Minecraft modding workflows across Fabric, NeoForge, and Architectury are managed by establishing workspace profiles, running MCP preflight checks, and generating targeted code slices for implementation. This ensures strict loader, version, and mapping discipline throughout development.

MCP preflight in Minecraft modding establishes loader, version, and mapping context before work begins. It is needed when starting registration, datagen, GameTest wiring, or version migration tasks to ensure explicit project provenance and strict version discipline.

GameTest wiring and data generation for a Fabric mod are set up by providing a minimal project profile and requesting a task slice. This generates concrete implementation steps and checklists that guide the datagen and GameTest wiring processes with minimal input.

Version migration and NBT payload remapping are fully supported. The workflow orchestrates these tasks by applying strict version and mapping discipline, ensuring explicit project profiles and provenance guide the remapping and migration implementation steps accurately.

Debugging runtime logs and planning Minecraft mod tasks is best handled by using targeted code slices and checklists. These translate high-level goals into concrete implementation steps, coordinating workspace profiling and reference routing for effective debugging.