1.0.1
Compatibility
Required content
Changes
Fixes
Fix 1 — XP progression formula
Fixed incorrect level-up loop in ServerPlayerEntityMixin.java where the XP cost
was read before and after addExperienceLevels(1) in the wrong order, causing
overflow XP to be scaled incorrectly. This made levels cost significantly less
than configured, allowing players to level up much faster than intended.
Fix 2 — Server config not applied on client
The client always used its own local ConfigInit.CONFIG to calculate and display
XP requirements, completely ignoring the server's configuration. Added
ConfigSyncPacket which is sent to the client on join, overwriting the local
XP-related config values (xpBaseCost, xpCostMultiplicator, xpExponent,
xpMaxCost, overallMaxLevel) with the server's values.
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:WoSRL735:9AhocKIT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WoSRL735:9AhocKIT"
}


