Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 months ago
All versions
1.2.5b2
Beta
PassivePhantoms 1.2.5b2last year 31
Compatibility
Minecraft: Java Edition
1.21
1.20
1.19
1.18
1.17
1.16
1.15
1.14
1.13
Platforms
Paper
Purpur
Spigot
Changes
Added
- Per-chunk mobcap system: Prevents infinite phantom spawning with a limit of 8 phantoms per chunk
- Configurable mobcap: New
phantom_settings.max_phantoms_per_chunksetting allows server admins to adjust the per-chunk limit - Mobcap monitoring: Enhanced
/passivephantoms statuscommand shows phantom populations per world - Chunk-based spawning: Phantoms now spawn based on chunk limits rather than world-wide limits
- Better distribution: Prevents single players from hogging all phantoms in a world
- Debug logging: Shows chunk coordinates and mobcap status in debug messages. Enable
debug_logging: trueto see when chunk mobcaps are reached.
Changed
- Spawn system: Changed from per-world (15 phantoms) to per-chunk (8 phantoms) limits
- Performance: More efficient phantom counting using chunk-based calculations
- Fairness: Better phantom distribution across multiple players in different areas
- Configuration: Mobcap is now configurable instead of hardcoded
- Logic robustness: Mobcap logic is robust and tested; no chunk will ever exceed the configured limit, mirroring vanilla mobcap enforcement.
Technical Details
- Uses chunk coordinates (
blockX >> 4,blockZ >> 4) for efficient counting - Each chunk can independently have up to the configured limit (default: 8 phantoms)
- Multiple chunks can each reach their limit, allowing higher total phantom populations
- Maintains compatibility with multiple End worlds
- Configurable mobcap supports values from 5 (conservative) to 15+ (generous)
- Mobcap enforcement is logged when debug_logging is enabled
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:zdnQbWA0:ehcEE90o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zdnQbWA0:ehcEE90o"
}

