: The modLoader field specifies the "Language Loader." Since most NeoForge mods are Java-based, javafml is the default provided in the NeoForge MDK .
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
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. neoforge mods.toml modloader value neoforge or javafml
: This is the standard value for most developers. It tells NeoForge that your mod is written in Java and uses the @Mod annotation to define its entry point.
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 : The modLoader field specifies the "Language Loader
Are you migrating an , or are you setting up a new NeoForge project from scratch? Mod Files | NeoForged docs
: When using javafml , the loader looks for a public class with the @Mod annotation. The value of this annotation must match one of the modId values defined in your TOML file. Why javafml is the Standard Historically, the value
Beyond mere functionality, this distinction reflects a broader philosophical shift in the community. Forge’s javafml represents a decade of accumulated compatibility, for better or worse—including technical debt and deprecated patterns. Neoforge’s decision to introduce its own modloader value is a statement of independence, prioritizing clean breaks over backward compatibility. It allows the new loader to evolve without being eternally bound to the quirks of FML 1.x. For players and pack developers, checking the mods.toml of a suspicious mod has become a quick diagnostic: neoforge tells you the mod author is up-to-date and intentional; javafml might indicate an older mod that could be unstable on modern Neoforge versions.