| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
For more information please see http://www.spigotmc.org/
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit centralizes event handling to where damage is actually applied
to the entity to avoid bugs that have resulted from nodamageticks,
modifications to damage after the event has been called, and similar
mishaps. This also implements new API for getting and setting of
modifications made to the damage amount actually applied to the entity.
This is done by storing the change in the damage amount as each modifier
is applied by vanilla code.
The method that actually damages the armor worn by an entity has been
relocated beneath the event called as to not apply durability loss when
the event has been cancelled.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Allows for interesting things to be done with world.spawn()
|
| |
|
| |
|
|
|
|
| |
BUKKIT-2781
|
|
|
|
|
|
|
|
|
|
|
| |
When a block creates a falling entity the block is not immediately removed
from the world. Instead, the falling entity is responsible for removing it
but only if the block still exists. Due to certain piston mechanics it is
possible to move the block before this check happens and thus the block is
not removed. This should be fine as the entity will kill itself in this
situation. However, the code does not stop here and continues running the
rest of the entity logic which includes either placing a block in the world
or placing a block item in the world depending on the circumstances.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We know these updates (can) break plugins bypassing Bukkit. They are needed for
smooth updates however. There will be another one right before before 1.1-R1.
|
| |
|
| |
|
|
|