Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 months ago
Updated 3 weeks ago
All versions
1.0.7
Release
LevelZ Refabricated 1.0.73 weeks ago 132
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
1.0.7
Fixed
- Fixed mob farm anti-cheese incorrectly counting a kill whenever a mob had merely been damaged by a player at some point, even if it actually died from another cause (fall damage, drowning, fire, other mobs, environmental damage, etc). Chunk kill counters now only increment when a player deals the actual killing blow.
- Fixed the same issue affecting modded XP drops: XP was previously granted regardless of who/what killed the mob whenever the anti-farm check didn't apply cleanly. Modded XP is now only ever granted when the killer is a real player — kills by Create saws, other mobs, environmental damage, etc. no longer drop XP.
- Changed the mob-farm kill counter from per-player to global per-chunk, so multiple players killing mobs in the same chunk now correctly share and hit the same kill limit (e.g. 3 players each killing 30 mobs in one chunk now correctly hits an 80-kill cap instead of tracking each player separately).
- Fixed
/level <player> get allthrowing/failing instead of returning the player's stats, caused by the command incorrectly trying to resolve "all" as a skill key.
Changed
/level <player> get allnow prints a full breakdown in order: player name header, overall level, modded XP progress (current/next), skill points, then every skill as current level / max level.
Added
- New command
/level chunk, usable by any player (no admin permission required), showing the mob-farm kill status of the chunk they're standing in: current kill count vs. the configured limit, and — if decay is enabled — the time until the next decay tick and how many kills will be removed.
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:Z7fqrQW5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WoSRL735:Z7fqrQW5"
}

