When a player enters an example zone named "Castle_Wars", the following permissions are granted:
- war.playing (Added for any zone)
- war.playing.castle_wars (Added for this zone, formed by the lower case of the zone name)
To grant additional permissions from these, such as 'crackshot.use', you should modify Bukkit's permissions.yml to create a parent node for either war.playing or the zone-specific node with child nodes.
http://bukkit.gamepedia.com/Permissions.yml
Example:
war.playing:
description: Allow use of gun plugins inside war zones only
default: false
children:
crackshot.use: true
war.playing.castle_wars:
description: Allow use of craft book elevators inside Castle_Wars only
default: false
children:
craftbook.use: true
This prevents leaves/mushroom/etc from growing inside flags,
monuments, cakes, bombs, spawns, etc. Trees can still be grown
around the perimeter of such strucures, but all blocks generated
will be in breakable areas.
Whoever wrote the note in LoadoutResetJob about stopping fire knew what
he was talking about. Sadly `git blame` shows nothing due to a refactor.
However, this job was still being run in sync, therefore doing nothing.
So I added a new job that is ran a tick later to clean up.
The more interesting change I made here was the removal of the so-called 're-killing' statements - e.g. setting the health of really dead players to 0 to ensure they are dead. Who knows, it might affect #796 and #778, because I have zero idea what is causing them.
Closes#711, closes#13, closes#11.
Items only drop on kill to prevent players from farming items. Warzone
makers must design their warzone items to fit with this feature if they
choose to enable it. E.g. a warzone might include items that must be
found and then can be stolen on kill.
Thanks to @dylanhansch for testing.
Closes#781
Another bug due to Mojang's new stupid username changing "feature".
Setting the owner requires a web lookup or cache hit for the name in
order to target the correct player. It apparently doesn't like looking
up a blank name.
Closes#793
Please note this is not a simple fix and applies it through a large
series of changes that may need to be noted in case of further troubles
in the future.
To accomplish this correctly, if a player is a really dead fighter, his
state and position will not be updated in a number of places. This is
all handled by the respawn hook for really dead fighters, which by the
way I rewrote because yolo. It makes a (potentially incorrect)
assumption that there is no reason a zone should hold a previous player
state when they join, so it is deleted for safety purposes. If not, and
the player leaves the zone, they may lose items. This may fix other
related inventory reset issues.
Warzones created in worlds that are then deleted can cause a stack
trace to dump in the error log. This replaces the stack trace with
an informative error message.
Closes#774
