| Commit message (Collapse) | Author | Age | Lines |
|\
| |
| |
| |
| |
| |
| | |
~GENAZT/craftbukkit:bugfix/SPIGOT-20 to master
* commit 'cc0d8bb32722bce9ea87b60c8353f070eb51aa7d':
Update the correct Scoreboard Criteria when a health change comes in. This fixes SPIGOT-20
|
| |
| |
| |
| | |
fixes SPIGOT-20
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
~GENAZT/craftbukkit:bugfix/SPIGOT-58 to master
* commit 'c8a76994dcad959b306d6e84e0b73f23571f3e14':
Horses spawned under Y 0 cause CraftBukkit to crash. This happens a lot since people keep using bugged Horses for Holographics
|
|/
|
|
|
|
| |
since people keep using bugged Horses for Holographics
Remove out of bounds horses, fixes an vanilla bug. Fixes SPIGOT-58
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
~GENAZT/craftbukkit:bugfix/SPIGOT-46 to master
* commit '1e8a3f192f78aebad26c3ed9dcdd27d61d51e130':
Corrected WorldData patch file
Rewrite the level.dat properly. This fixes SPIGOT-46
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
~GENAZT/craftbukkit:bugfix/SPIGOT-44 to master
* commit '4d0f5edb05f371f1294d5991e3379a3ed688428e':
Just only hold the last BlockState update for the same location. This fixes SPIGOT-44
|
|/
|
|
| |
SPIGOT-44
|
|\
| |
| |
| |
| |
| |
| | |
~MIKEPRIMM/craftbukkit:mikeprimm/SPIGOT-30 to master
* commit '46922049214f37fbc6369a6f1391f3963ff2d3be':
SPIGOT-30: Fix restoring of WorldData when loading worlds
|
| | |
|
| |
| |
| |
| |
| | |
Worlds already loaded in 1.8 can still be saved by this but tile entities will
be lost
|
|/
|
|
| |
Somewhat of a lazy way of doing it but it will do for now
|
| |
|
|
|
|
| |
command. This fixes SPIGOT-12
|
|\
| |
| |
| |
| |
| |
| | |
~MIKEPRIMM/craftbukkit:mikeprimm/SPIGOT-29 to master
* commit 'dd33bcf6a53149d3813d128d5e93b5bf5ca69711':
Fix chunk snapshot generation (needed for Dynmap)
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit d6e3dff7d88b3b4275108071704a1ef18d8484c5.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
For more information please see http://www.spigotmc.org/
|
|
|
|
|
|
|
|
|
|
|
| |
Up until Minecraft version 1.5 it was not possible to teleport entities
within vehicles. With the 1.5 update came the change in the Minecraft
teleportation logic to dismount before teleporting the entity, if
applicable.
This commit ammends the existing CraftBukkit logic for rejecting
teleportation for entities in vehicles to permit the action. Due to this
change, CraftBukkit is now in-line with Minecraft 1.5 teleportation logic.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a player dies their inventory is normally scattered over the the area
in which they died. Plugins should be able to modify this behaviour by
defining whether or not the player's inventory will be dropped on the ground or waiting for the player when they eventually respawn.
This commit implements the methods included in the Bukkit half for the new
behaviour by acting upon the boolean flag. The boolean flag is tested
prior to clearing the inventory as well as prior to dropping the items on
the ground. If the flag is true (indicating "keep inventory"), the items
are not removed from the player's inventory and are not dropped on the
ground.
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using a "vanilla" Minecraft server using the "pick block" key on a
command block yields the invoker with a command block within their
inventory while in creative mode. Implications of the invalid items set
containing the command block also include having a "ghost" item that
cannot be placed due to it not actually existing.
This commit resolves the problem and brings Craftbukkit closer to vanilla
behaviour by removing the command block item ID, 137, from the invalid
items set.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this commit cancelling the PlayerFishEvent would cause various
states of the fishing routine to be incorrectly or wrongly fired. This
incorrect behaviour was due to the miscommunication between the server and
client regarding the fishing state. When the event was cancelled, the
bobber entity was removed and caused the client to incorrectly determine
what the "next state" was to logically be.
This commit resolves the issue by ensuring the client is made aware of the
correct changes at the correct time regarding the bobber entity, therefore
keeping the logical steps of "fishing" proper and in-tact.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Up until this commit the PlayerDropItemEvent, if cancelled, would return
items to the first available slot in the inventory - which is clearly
undesirable as a player and plugin author to deal with.
This commit changes that by ensuring that the item is returned to where
it came from in the player's inventory. This still supports modifying the
drop from the player and will default to "first available slot" if the
item has changed since the event was fired. Other remaining behaviour of
the event is still in tact and has not been modified.
|