So your META-INF/neoforge.mods.toml file should contain a line like:
Here’s the relevant neoforge.mods.toml entry for modLoader :
It informs the engine how to validate the companion loaderVersion range specified right below it. Supported modLoader Values in NeoForge neoforge.mods.toml modloader value
Requires a public main class decorated with the @Mod annotation. Example Syntax: modLoader="javafml" loaderVersion="[4,)" Use code with caution. 2. "lowcodefml" (The Minimalist Choice)
In this example, the modloader value is set to neoforge , indicating that the example-mod should be loaded using the NeoForge modloader. So your META-INF/neoforge
For Neoforge (and Forge-based mods), the modLoader value must be "javafml" . This tells the game’s mod loading system that your mod uses the standard Java-based FML (Forge Mod Loader) system. Even though Neoforge is a separate project from Forge now, it retains compatibility with the same mod loader specification.
[[mods]] group = "com.example" artifact = "example-mod" version = "1.0.0" displayName = "Example Mod" description = "An example mod" modloader = "neoforge" This tells the game’s mod loading system that
The modLoader configuration acts as a traffic controller during the game boot sequence. It performs several distinct technical tasks:
A common point of confusion for developers is where the modLoader value sits relative to the rest of the metadata. The neoforge.mods.toml layout is explicitly divided into non-mod-specific configurations and mod-specific arrays. Property Category Valid Keys Included Structure Level modLoader , loaderVersion , license , issueTrackerURL Top-level / Global (Must appear first) Individual Mod Metadata modId , version , displayName , description [[mods]] Array blocks Dependency Contracts modId , mandatory , versionRange , ordering [[dependencies. ]] Array blocks Complete Structural Example
Here's an example mods.toml file with a modloader value: