Load mods that declare explicit 1.21 compatibility as 1.21.1 is a minor bugfix.

This commit is contained in:
LexManos 2024-08-08 14:01:31 -07:00
parent db4d8a4729
commit dc594f196a
No known key found for this signature in database
GPG key ID: 6E90061A7AE1F652
2 changed files with 6 additions and 6 deletions

View file

@ -19,11 +19,11 @@ public class VersionSupportMatrix {
private static final HashMap<String, List<ArtifactVersion>> overrideVersions = new HashMap<>();
static {
final ArtifactVersion version = new DefaultArtifactVersion(FMLLoader.versionInfo().mcVersion());
if (MavenVersionAdapter.createFromVersionSpec("[1.19.2]").containsVersion(version)) {
// 1.19.2 is Compatible with 1.19.1
add("languageloader.javafml", "42");
add("mod.minecraft", "1.19.1");
add("mod.forge", "42.0.9");
if (MavenVersionAdapter.createFromVersionSpec("[1.21.1]").containsVersion(version)) {
// 1.21.1 is Compatible with 1.21
add("languageloader.javafml", "51");
add("mod.minecraft", "1.21");
add("mod.forge", "51.0.33");
}
}
private static void add(String key, String value) {

View file

@ -14,4 +14,4 @@ MAPPING_VERSION=1.21.1
// Set to true before the first build of a new MC version, so we don't do compatibility checks
CHECK_COMPATIBILITY=false
// Set to true to allow for fuzzy patching. Useful during updateing
UPDATING=true
UPDATING=false