In the ecosystem of Minecraft modding, few files are as critical to a mod’s identity as mods.toml . This metadata file, placed inside a mod’s JAR, acts as its passport, telling the game loader who the mod is, what version it needs, and—most critically— how it should be loaded. For mods built on Neoforge, a successor to the legacy Forge API, one line in this file has become a subtle but important source of confusion and precision: modloader . The choice between specifying modloader="neoforge" or modloader="javafml" is not arbitrary; it defines the mod’s technical lineage, its compatibility, and its place in the evolving history of Minecraft modding.
Is NeoForge compatible with normal Forge mods? : r/feedthebeast neoforge mods.toml modloader value neoforge or javafml
For mod developers, the practical implication is straightforward but vital. When setting up a new project in the NeoForge environment, the mods.toml file should strictly use modLoader="neoforge" . Using the legacy javafml tag in a modern NeoForge mod can lead to warnings, unexpected behavior, or incompatibility as the gap between the legacy Forge codebase and the modern NeoForge codebase widens. The accompanying loaderVersion property must also align with this change, specifying the version range of the NeoForge loader rather than the old FML version. In the ecosystem of Minecraft modding, few files
: While NeoForge is the platform, neoforge itself is typically not the value for the modLoader field in your metadata file; rather, it's often used in the dependencies section to specify the version of the NeoForge API required. Key Differences & Usage When setting up a new project in the
Defines the version range for the language loader (currently version 1 for most projects). e.g., MIT Mandatory field for the license your mod is provided under. Why javafml is the Standard
In conclusion, the value of the modLoader property in mods.toml acts as a handshake between the mod and the game engine. While javafml is a relic of the venerable Forge Mod Loader era, representing years of stability and widespread adoption, neoforge is the banner of the platform's future. The transition from one to the other is not merely a semantic change but a declaration of alignment with the new direction of the modding platform. For developers aiming to build robust, future-proof mods, correctly specifying neoforge is the first step in ensuring their creation is properly recognized and loaded by the next generation of Minecraft modding tools.
Are you migrating an , or are you setting up a new NeoForge project from scratch? Mod Files | NeoForged docs