Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 months ago
All versions
1.2.5b1
Beta
PassivePhantoms 1.2.5b1last year 21
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
Fixed
- CRITICAL: Fixed phantom targeting issue where Phantom aggresion would randomly break
- CRITICAL: Fixed phantom aggression persistence - phantoms now stay aggressive after being hit
- Changed event priority from LOWEST to HIGH for better compatibility with other plugins
- Improved phantom damage event handling to ensure immediate aggression
- Fixed targeting logic to properly handle null targets for aggressive phantoms
- Added immediate re-targeting for aggressive phantoms when they lose their target
- Fixed variable scoping issues in lambda expressions
Added
- New
/passivephantoms debugcommand to toggle debug logging in-game - New
/passivephantoms statuscommand to check plugin status and aggressive phantom count - New
/passivephantoms listcommand to list all aggressive phantoms and their current targets - Enhanced debug logging with phantom UUIDs for better troubleshooting
- Tab completion for all
/passivephantomscommands with smart filtering - Comprehensive tracking of when phantoms are added/removed from aggressive set
Changed
- Updated version to 1.2.5 to reflect critical bug fixes
- Improved command help messages with new subcommands
- Enhanced targeting event logging to show target information and aggressive status
- Better error handling and safety checks for phantom targeting
Technical Details
- Aggressive phantoms now re-target immediately when they lose their target (null)
- Re-targeting uses next-tick scheduling to avoid event conflicts
- Only re-targets when phantom actually loses target, not constantly
- Preserves natural phantom AI attack cycles while maintaining aggression
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:1mtvTbKK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zdnQbWA0:1mtvTbKK"
}

