Better Phantom handling for SMP
Go to file
2019-03-30 01:29:26 -04:00
.idea Complete test plugin 2018-08-11 00:07:11 -04:00
gradle/wrapper Initiate Gradle files 2018-08-11 00:06:54 -04:00
src/main Refactor Code 2019-03-30 01:29:26 -04:00
.gitignore Initiate Gradle files 2018-08-11 00:06:54 -04:00
build.gradle Fix configuration version node 2019-03-29 23:08:36 -04:00
gradlew Initiate Gradle files 2018-08-11 00:06:54 -04:00
gradlew.bat Initiate Gradle files 2018-08-11 00:06:54 -04:00
license #1: Add License and Links 2018-08-11 04:31:36 -04:00
readme.md Refactor Code 2019-03-30 01:29:26 -04:00
settings.gradle Initiate Gradle files 2018-08-11 00:06:54 -04:00

Logo PhantomSMP

Better Phantom handling for SMP

Configuration

There are two 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.

Permissions

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.

Disallowing Phantom Spawn

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.

External Links