2.0.0
Compatibility
Changes
Level System Rework
We have completely reworked the leveling mechanics to make character progression deeper and more engaging.
New features:
-
In addition to health points (HP), each level now also increases your movement speed and your chance to block an incoming attack.
-
The formula for calculating the experience required to reach the next level has been revised, making the progression curve more balanced.
-
A quality-of-life improvement: leftover experience is no longer reset upon leveling up. Any excess XP carries over and counts toward the next level.
New admin commands:
The following commands have been added for better player management:
-
/give_points [player] [number] — grants the specified amount of experience points to a player.
-
/set_lvl [player] [number] — forcefully sets a player's level to the specified value.
Flexible configuration via config file:
A new configuration file — sys_config — has been added, allowing you to fine-tune the level system to fit your server's needs. The following parameters are available:
- "Up" section (level-up bonuses):
Enable or disable the entire level system.
Adjust the amount of health gained per level.
Adjust the movement speed percentage bonus gained per level.
Adjust the block chance percentage bonus gained per level.
- "Experience" section (XP settings):
Change the experience gain multiplier.
Change the multiplier for the base experience required per level.
Change the multiplier applied at higher levels.
Changes:
-
The /lvl_system command has been removed as it was no longer needed.
-
The /get_stats command has been updated to display the new character stats (movement speed and block chance) alongside the existing ones.
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:5SVXOhms:yR0pkSni"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5SVXOhms:yR0pkSni"
}

