
Mob Limiter
ArchivedSet per-chunk and world limits to manage mob spawning and prevent overcrowded farms.
22.2Kdownloads
11followers
22.2Kdownloads
11followers
Mob Limiter has been archived. Mob Limiter will not receive any further updates unless the author decides to unarchive the project.
All versions
1.1.0
Release
[v1.1.0]last year 13.4K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Server-side
Singleplayer
Changes
Added
- JSON5 Configuration: Replaced TOML with a more flexible JSON5 format.
- World Limits: Added global mob caps for world-wide restrictions.
- Vanilla Despawn Control: Introduced
vanilla_despawnsettings (vanilla,custom,disabled) to manage mob persistence. - Removal Types: Added
removal_type(despawnfor silent removal,killfor loot drops) for both world and chunk limits. - Priority System: Chunk limits now follow a clear priority: specific mob → category → namespace → default.
- Asynchronous Processing: Mob limit checks and cache updates now run asynchronously.
- Commands:
- Added
/moblimiter infoto display current settings. - Removed
/moblimit debugand/moblimit statsfor a simpler command structure.
- Added
Changed
- Config Structure: Reworked into
world_limits,chunk_limits, andvanilla_despawnsections, with the ability to enable/disable each. - Default Removal: Set to
despawn(previously removed silently) to avoid unintended loot drops. - Command Namespace: Updated from
/moblimitto/moblimiterfor consistency.
Fixed
- ConcurrentModificationException: Resolved crash during mob removal in high-load scenarios.
- Config Parsing: Improved error handling for invalid mob IDs and config formats.
- Config Duplication: Fixed duplication of config file after reloading with
/moblimiter reload.
Note
- Existing TOML configs (
moblimiter.toml) must be migrated to JSON5 (moblimiter.json5). Check the new config file for updated structure and examples.
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:GBTZ8qN6:g8icbA63"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GBTZ8qN6:g8icbA63"
}
