: 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
: The modLoader field specifies the "Language Loader." Since most NeoForge mods are Java-based, javafml is the default provided in the NeoForge MDK .
Historically, the value javafml was the standard for mods developed for the Forge Mod Loader (FML). FML was the underlying loading system that powered Minecraft Forge. When a developer wrote modLoader="javafml" , they were explicitly telling the engine to use the standard FML loading mechanism, which relied on Java annotations to identify the mod's entry point (typically a class decorated with @Mod ). This value signified that the mod was a standard Java-based modification compatible with the Forge ecosystem, distinguishing it from other potential loader types that might have existed in a more modular future.
Why does this matter to the average modder or server admin? Because misusing this value leads to the classic "loader mismatch" errors. A common mistake is to copy a mods.toml from an old Forge mod, change the name and description, but leave modloader="javafml" . When loaded in a pure Neoforge environment (especially one that has disabled legacy fallbacks), the loader may reject the mod or attempt to run it in an incomplete legacy mode, causing cryptic crashes or missing features. Conversely, setting modloader="neoforge" for a mod that still relies on old Forge internals will cause the Neoforge loader to look for entrypoints or behaviors that don’t exist. Therefore, the rule is straightforward: neoforge mods.toml modloader value neoforge or javafml
To understand the distinction, one must first recognize that javafml is the legacy value. FML, or the "Forge Mod Loader," has been the engine powering Forge mods since Minecraft’s early days. For nearly a decade, virtually every Forge mod declared modloader="javafml" . This string told the Forge-compatible loader to initialize the mod using the standard FML system, which expects certain entrypoints (like a class annotated with @Mod ) and follows a well-worn lifecycle. When Neoforge forked from Forge in mid-2023, it initially retained compatibility with javafml mods, allowing thousands of existing mods to run unchanged. However, as Neoforge began diverging—removing deprecated APIs, refactoring the core loader, and introducing new features—it became necessary to distinguish between mods designed for the old Forge ecosystem and those built explicitly for Neoforge’s modernized architecture.
A standard configuration in META-INF/neoforge.mods.toml looks like this:
NeoForge was born as a fork of Minecraft Forge, inheriting many of its foundational systems. The javafml loader is the default mechanism that looks for the @Mod annotation in your Java classes. : While NeoForge is the platform, neoforge itself
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.
From a technical standpoint, the shift toward the neoforge value represents a move toward a more distinct identity. In the current NeoForge environment (specifically for versions 1.20.4 and newer), the expected value in the mods.toml is neoforge . While the loader is often sophisticated enough to recognize javafml for backward compatibility in transitional versions, using neoforge is the correct standard for modern development. It signals to the game engine that the mod utilizes NeoForge-specific features, optimizations, and the updated loading pipeline. It ensures that the mod is treated as a first-class citizen within the new ecosystem, avoiding potential ambiguity in a landscape that now contains multiple competing loaders like Fabric and Quilt.
Other specialized loaders exist, such as lowcodefml for "low-code" or no-code modding, but for 99% of developers writing standard Java or Kotlin mods, javafml is the requirement. Common Pitfalls and Version Differences FML was the underlying loading system that powered
When configuring your mod for NeoForge , the neoforge.mods.toml file (formerly mods.toml in Forge) is the heartbeat of your mod's identity. One of the most critical fields is the modLoader value, which tells the game exactly how to interpret and boot your Java code. The Direct Answer: neoforge vs. javafml
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.
neoforge.mods.toml file to use in your project? Copy Creating a public link... Good response Bad response 7 sites Mod Files | NeoForged docs javafml and @Mod javafml is a language loader provided by NeoForge for the Java programming language. The entrypoint is defined ... NeoForged Documentation Mod Files | NeoForged docs The language loader used by the mod(s). Can be used to support alternative language structures, such as Kotlin objects for the mai... NeoForged Documentation Mod Files | NeoForged docs The language loader used by the mod(s). Can be used to support alternative language structures, such as Kotlin objects for the mai... NeoForged docs Mod Files | NeoForged docs Mod Entrypoints Now that the neoforge. mods. toml is filled out, we need to provide an entrypoint for the mod. Entrypoints are es... NeoForged Documentation [Solved] Forge failing to load mods.toml (Setup wasn't correct) Mar 28, 2020 —
In a standard NeoForge environment, the modLoader value you should use is .