Better Phantom handling for SMP
This plugin was created to combat phantom issues in the survival Multiplayer server environment.
Normally, phantoms spawn above players who had three or more Minecraft days of restlessness. After the phantom(s) spawn, when the player uses the bed or is killed, phantoms will continue to haunt the same player until they cannot find the player! While they still exist, they will move on to assault any other players regardless of if they rested.
In single player, the above will not be any problem since the lone player can skip the night and let the sun kill off the phantoms. However, that's not the case on multiplayer servers where players have to endure phantom attacks until the next sunrise.
This plugin addresses this issue. Features:
- Phantoms will ignore players who used the bed within last three Minecraft days. (The duration is configurable)
- Phantoms will ignore or despawn on players who uses the bed or is killed. This is configurable as well.
- Control if the phantoms should despawn when they try to target a rested player using a configuration option.
There are three core configuration options that you can set.
remove-targeting-rested: Default: true. Remove phantoms that try to target players who recently rested.remove-when-sleeping: Default: false. Remove phantoms as soon as player gets in the bed.disallow-targeting-for: Default: 72000. Ticks since player's last rest before a phantom starts targeting them.
For additional information, check config.yml.
All permission nodes are not applied by default, even to server operators.
phantomsmp.disallowspawn: If given, phantoms will not spawn on this player.phantomsmp.ignore: If given, phantoms will essentially ignore this player.
For additional information, check plugin.yml.
The Bukkit API does not allow for directly checking which player caused the
phantoms to spawn. Therefore, if disallow-targeting-for is greater than
72000, phantoms will spawn in for a few seconds until they start targeting a
player. When the very first target of the phantom is a well-rested player,
they will despawn immediately. The same happens when the player is given the
phantomsmp.disallowspawn permission.
