Upstream/PhantomSMP
1
0
Fork 0
mirror of https://github.com/chuushi/PhantomSMP.git synced 2024-11-25 03:25:13 +01:00
Code Issues Projects Releases Wiki Activity
Better Phantom handling for SMP
29 Commits 1 Branch 7 Tags 194 KiB
Java 100%
eeeac813e7
Go to file
Simon Chuu eeeac813e7 Trigger warning when player leave event fires without join event being called 
Join event sets up the phantom list for specific player(s).
2019-05-29 02:28:03 -04:00
.idea Add Chunk Unload Event + Update bukkit api and bStats version 2019-05-29 02:06:51 -04:00
src/main Trigger warning when player leave event fires without join event being called 2019-05-29 02:28:03 -04:00
.gitignore Move from Gradle to Maven 2019-04-10 22:04:28 -04:00
.travis.yml Add travis + add bStats as dependency 2019-04-10 21:38:28 -04:00
license Update License year 2019-04-07 00:32:14 -04:00
pom.xml Merge branch 'master' into v1.1.1-snapshot 2019-05-29 02:17:12 -04:00
readme.md Add badges 2019-04-10 22:08:32 -04:00

readme.md

Logo PhantomSMP

Build Status Maintainability

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. In addition, this 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.

Configuration

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.

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