What happened?

Hi,

I believe the server component built for Neoforge has the wrong javafml loaderVersion of 41 specified in the neoforge.mods.toml file which leads to a server crash on load which looks something like this

net.neoforged.neoforge.logging.CrashReportExtender$ModLoadingCrashException: Mod loading has failed


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Mod loading issue --
Details:
	Mod file: <No mod information provided>
	Failure message: Mod File <server path>\mods\RoughlyEnoughItems-16.0.797-server-only.jar needs language provider javafml:41 or above to load
		We have found 4.0.35
	Mod version: <No mod information provided>
	Mod issues URL: <No issues URL found>
	Exception message: <No associated exception found>

Manually changing neoforge.mods.toml to include loaderVersion of 4.0.35 (used this simply because this was the version I have on my neoforge) makes it launch, seemingly without issues, and Neoforge documentation specifies loaderVersion="[1,)" as the line for javafml loader.

This was checked on Neoforge versions 21.1.115 and 21.1.119 for Minecraft version 1.21.1

What mod loaders are you seeing the problem on?

Neoforge

What do you think this bug is of?

• Visual
• Recipe Lookup
• Cheat Mode
• Plugin Integration / JEI Plugin Compatibility
• Others

Relevant log output

net.neoforged.neoforge.logging.CrashReportExtender$ModLoadingCrashException: Mod loading has failed


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Mod loading issue --
Details:
	Mod file: <No mod information provided>
	Failure message: Mod File <server path>\mods\RoughlyEnoughItems-16.0.797-server-only.jar needs language provider javafml:41 or above to load
		We have found 4.0.35
	Mod version: <No mod information provided>
	Mod issues URL: <No issues URL found>
	Exception message: <No associated exception found>

Anything else?

No response

By submitting this issue, I have included the necessary logs by pasting the contents into the correct location or attaching the file as an upload.

• Yes, and I did not use any paste services other than GitHub Gists.

By submitting this issue, I have confirmed my REI and REI's dependencies are up to date.

• Yes