Minecraft NeoForge Modder

Problem

In Minecraft NeoForge modding, many failures come from project constraints rather than logic: DeferredRegister id setup, datagen entry points, Mixin declarations, choosing Access Transformer over @Accessor, and selecting the right AnvilLib modules all affect whether a build succeeds. For small items, recipes, or entities, over-abstraction and hand-written JSON also make code harder to maintain. This skill keeps tasks verifiable: clarify requirements first, check documentation second, and then generate code that fits the NeoForge workflow.

Capabilities and Workflow

The skill defaults to NeoForge and ModDevGradle, preferring the official registration system and datagen. When adding items or blocks, it lists registration, models, language entries, and texture locations together. For recipes, it uses RecipeProvider to generate output under src/generated/resources instead of hand-writing JSON. When private access is needed, it prefers Access Transformer and recommends Mixin only for more complex injection cases. If using AnvilLib, it selects modules such as Config, Network, Registrum, or Util based on the task, rather than pulling in the Main aggregate by default.

Boundaries and Notes

It fits solo or small-team Minecraft mod development, especially when Chinese comments, Chinese communication, and clear completion criteria matter. It is not a version lookup tool: for current Minecraft or NeoForge versions, documentation should be checked rather than memory. Open-source references must cite sources and respect licenses; GPL code cannot be folded into MIT or closed projects. Generated code still needs validation through builds, client runs, datagen, or tests.