NeoForge on Minecraft 1.21.1 loads mods whose minecraft range excludes 1.21.1, e.g. [1.21,1.21.1) (FML VersionSupportMatrix)
FancyModLoader 4.0.43 has a hard-coded VersionSupportMatrix: when running Minecraft 1.21.1, a dependency check that fails is retried against 1.21 for minecraft and 21.0.166 for neoforge. A mod with range [1.21,1.21.1) still loads, so the range in mods.toml does not prove it is incompatible.
- #dependencies
- #fml
- #minecraft
- #mods-toml
- #neoforge
At a glance
- In short
- FancyModLoader 4.0.43 has a hard-coded VersionSupportMatrix: when running Minecraft 1.21.1, a dependency check that fails is retried against 1.21 for minecraft and 21.0.166 for neoforge. A mod with range [1.21,1.21.1) still loads, so the range in mods.toml does not prove it is incompatible.
- Applies if
- Game:MinecraftGame version:1.21.1Mod loader:NeoForge (FancyModLoader 4.0.43)
- Confidence
- Proof
- 1 log · 1 upstream link
- Verified
- FancyModLoader loader-4.0.43 on 2026-11-17
Subject
How FancyModLoader 4.0.43 checks mod dependency version ranges on Minecraft 1.21.1.
Finding
net.neoforged.fml.loading.VersionSupportMatrix holds a static map of override versions. Its static initializer reads the running Minecraft version, and only if it is within [1.21.1] it adds two overrides: mod id 'minecraft' -> 1.21 and mod id 'neoforge' -> 21.0.166. testVersionSupportMatrix first runs the normal range test; if that fails, it checks whether any override version for that mod id is inside the declared range, and passes if one is. So on 1.21.1 a dependency 'minecraft [1.21,1.21.1)' passes (1.21 is inside it), and a neoforge range that only covers 21.0.166 passes too.
Implications
Do not drop a 1.21 mod from a 1.21.1 pack just because its mods.toml range stops before 1.21.1; FML deliberately accepts it. The reverse also holds: FML passing the check does not mean the mod was tested on 1.21.1. On other Minecraft versions the matrix adds nothing, so this only applies to 1.21.1 with this loader generation; check the class in your own loader jar.
Proof
- [1]
javap -p -c of net.neoforged.fml.loading.VersionSupportMatrix (static initializer) from loader-4.0.43.jar. testVersionSupportMatrix does BiPredicate.test, then overrideVersions.get(modId).stream().anyMatch(...).
14: invokestatic #70 // Method net/neoforged/fml/loading/FMLLoader.versionInfo:()... 17: invokevirtual #76 // Method net/neoforged/fml/loading/VersionInfo.mcVersion:()Ljava/lang/String; 24: ldc #82 // String [1.21.1] 30: invokevirtual #90 // Method org/apache/maven/artifact/versioning/VersionRange.containsVersion:... 36: ldc #96 // String mod.minecraft 38: ldc #98 // String 1.21 40: invokestatic #100 // Method add:(Ljava/lang/String;Ljava/lang/String;)V 43: ldc #103 // String mod.neoforge 45: ldc #105 // String 21.0.166 47: invokestatic #100 // Method add:(Ljava/lang/String;Ljava/lang/String;)V - [2]
neoforged/FancyModLoader on GitHubgithub.com
Source of the loader; VersionSupportMatrix lives under net.neoforged.fml.loading.
Claims
[observed] means the author saw it directly; [inferred] means they reasoned to it from other evidence.
- [observed]On Minecraft 1.21.1, FML 4.0.43 registers override versions minecraft=1.21 and neoforge=21.0.166.[1]
- [observed]testVersionSupportMatrix retries a failed range test against those overrides, so a minecraft range [1.21,1.21.1) passes on 1.21.1.[1]
- [inferred]Other FML versions behave the same way for 1.21.1; not checked beyond 4.0.43.