CHOOSE THE RIGHT MINECRAFT ROUTE.

Start with Java Edition or Bedrock Edition

Java Edition uses JAR-based code mods with loaders such as Fabric, Forge, and NeoForge. That is the route used by this site's Copper Token exercise. Bedrock Edition uses behavior packs, resource packs, and its scripting API; a Java mod JAR cannot be installed as a Bedrock add-on.

The Minecraft Launcher is not the game engine. Record the edition shown by your actual game profile before interpreting a scan. For a Paper or Spigot server, plugins are another route; they are not interchangeable with client-side loader mods.

Let the target instance decide the loader

If you are extending an existing modpack, use its exact loader and game version. For a new project, choose the loader whose API and dependencies fit the feature you want. Universal Modder supplies the research and coding workflow; it does not convert a Fabric JAR into a NeoForge or Forge JAR.

A few documented combinations

This table records specific source-backed combinations. It is not a universal compatibility list, and none of these rows means “the latest release.” Check your mod's own dependency range before installing it.

A code mod commonly needs a particular game version, a loader range, and one or more library mods. Treat those as a set. A “1.21” label on a download is not enough to establish that it works with 1.21.1, 1.21.4, or a later release.

Check the JVM used by the build and the launcher

Your shell's Java, the IDE's Gradle JVM, and the launcher's game runtime can be different. A launcher-bundled runtime that runs the game is not necessarily a JDK that can compile source code.

java -version
javac -version

.\gradlew.bat --version

./gradlew --version

For the 1.21.1 NeoForge exercise, all development tools should resolve a suitable JDK 21. For Forge 1.20.1, follow its documented Java 17 setup. If the wrapper reports a different JVM, fix the IDE or toolchain configuration before changing game code.

Keep dependencies and instance folders aligned

• Use the instance's real game directory. A modpack can have a mods/ folder separate from the default launcher directory.
• Read the mod metadata. NeoForge uses its neoforge.mods.toml metadata; Fabric uses fabric.mod.json; Forge uses its versioned mod metadata.
• Match required libraries. A missing dependency and an incompatible dependency are different errors; copy their exact names and version ranges from the log.
• Distinguish client and server requirements. A local single-player pass does not establish that a mod is safe to load on a dedicated server.
• Use one version of each mod. Duplicate JARs can collide before the game reaches the menu.

Inspect this Minecraft instance and list the edition, game version, loader name/version, game directory, launcher runtime, Gradle JVM and declared mod dependencies. Compare them with the field note or template I am following. Explain every mismatch before proposing a change.

Pick one route and one finish line

For a new 1.21.1 NeoForge practice instance, the Copper Token tutorial gives you a defined item, recipe, source package, build commands, and installed-JAR checks. For an existing Fabric or Forge modpack, preserve that pack's environment and ask your agent to build a similarly small feature with its matching API.