Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published last month
Updated last month
All versions
1.0.0+1.21.1
Release
heroslevels 1.0.0+1.21.12 months ago 7
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Added:
- Initial release. This notes are comparing the last LevelZ version.
- Added a red overlay to all the items you can't use in your inventory/hotbar
- A drop to ingredients in a Furnace/Brewing Stand whenever trying to fabricate a restricted item
- Brewing restrictions (you can drink potions, but not brew new potions)
- Compat with a few mods
- Locked tooltips adds an arrow whenever trying to fabricate a restricted item
- A restriction command to help modpackers
- Added bonus for potions (extra duration effect, lingering potions having more radius and duration)
- Added a configuration for how many XP mod drop when dying
- Added a dynamic drop to XP so that, if losing levels/experience (hard mode), it drops a %percentage of the XP, preventing the absolute loss of the progress for the player
- Added compat for Jade, Curios/Accessories, Enchanting Infuser, Easy Anvils/Magic and Apotheosis (kinda this one)
Changed:
- Now experience farms can work without spawning the mod experience
- Better configuration for colors on text screens
- The player in Skill Screen now is not a "statue"
- Changed the way enchantments is registered, making it compatible with Apotheosis and any mods that adds further vanilla level enchantments
- Using more NeoForge events and less mixin codes, preventing mixin conflicts with other mods
Fixed:
- Fixed an exploit for leveling up when dying and pick up the experience
- Fixed a lot of garbageCollector and trying to optimize the code
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:qnSRByab:SEW1nvDr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qnSRByab:SEW1nvDr"
}

