Links
Tags
Creators
Details
5.1.0-mc1.21.11
Compatibility
Required content
Changes
New Versioning-System
The Fable-Mod versioning will change from X.Y.Z to X.Y.Z-mcA.B.C
-
X -> major content changes
-
Y -> minor content changes and balancing
-
Z -> bugfixes and non-breaking changes
-
A, B, C -> Minecraft Version
Version-Checker changes
The version checker now only checks for a newer fablemod version within the same minecraft version. For example if FableMod 5.1.0-mc1.21.11 is the newest release for MC 1.21.11 it will not tell you there is a newer version even if FableMod 5.1.2-mc26.1 is already released.
Balancing
- Nether-Weapons now have the same attack damage like citrin-weapons (change was backported from the 5.1.0-mc26.1 release)
Bugfixes
- Player-Heads no longer appear as Zombie-Heads if you wear them
- Decaying Player-Heads can now no longer be placed, instead of turning all heads into Zombie-Heads when placed
- The player will be notified if trying to place a decaying Player-Head
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:W2mdeQqq:wuLt2Xdd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W2mdeQqq:wuLt2Xdd"
}

