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

Are you migrating an , or are you setting up a new NeoForge project from scratch? Mod Files | NeoForged docs

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

: 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.

In a standard NeoForge environment, the modLoader value you should use is .

In the neoforge.mods.toml (or mods.toml ) file, the modLoader value you should use depends on the language your mod is written in, as NeoForge uses this field to identify the responsible for your mod's entry point. Core Values