In a standard NeoForge environment, the modLoader value you should use is .
The introduction of NeoForge as a fork of the original Forge project necessitated a re-evaluation of these identifiers. Initially, NeoForge maintained backward compatibility, continuing to recognize javafml to ensure that the vast library of existing mods would not immediately break. However, the NeoForge team eventually introduced the neoforge token as a way to explicitly declare that a mod was built against the NeoForge toolchain and APIs, rather than the legacy Forge ones. This shift serves two primary purposes: branding and technical specificity. neoforge mods.toml modloader value neoforge or javafml
In conclusion, the modloader field in mods.toml is far from a mere formality. The choice between "neoforge" and "javafml" is a declaration of technical allegiance and a practical key to compatibility. While javafml preserves the legacy of a generation of mods, neoforge opens the door to a cleaner, more forward-looking future. For any mod developer working with Neoforge today, setting the correct value is not just good practice—it is the first step in telling the loader, and the world, exactly what your mod is made of. In a standard NeoForge environment, the modLoader value
Are you migrating an , or are you setting up a new NeoForge project from scratch? Mod Files | NeoForged docs The choice between "neoforge" and "javafml" is a