minecraft-project-conventionslisted

# Minecraft Project Conventions ## Purpose A Minecraft mod is not written against "Minecraft". It is written against one exact combination of **mod loader + Minecraft version + mappings**. That triple is a single indivisible fact: change any one of the three and class names, method signatures, registration timing, resource paths and JSON schemas all move. This skill establishes that fact from the project's own files before any other Minecraft skill is allowed to produce code, and describes the Gradle and resource layout that follows from it. ## When to use - The repository contains `fabric.mod.json`, `neoforge.mods.toml`, `mods.toml`, `quilt.mod.json`, or a `build.gradle` mentioning `fabric-loom`, `net.neoforged` or `architectury`, and any work is about to start. - Someone asks to "add a block", "add an item", "make a mod" and no loader or version has been stated yet. - A build fails with `cannot find symbol`, `method does not override`, or `NoSuchMethodError` at runtime, which almost always means code from the wrong version or loader was pasted in. - A new mod project is being scaffolded and the toolchain has to be chosen. ## When NOT to use - Server plugin work (Bukkit, Spigot, Paper, Velocity). Those are a different ecosystem with no mappings problem of this shape and no client side. - Datapack-only or resource-pack-only work with no Java. The version still matters, but the Gradle and loader material here does not apply. - Once the triple is resolved an