| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
As an added feature, players defaulted to being able to not pick up items if the flag was false. However, since minecraft doesn't normally use the flag on players, the flag was always false.
|
| |
|
|
|
|
|
|
|
|
| |
Adds:
- Getting/Setting equipment
- getting/setting drop rates
- getting/setting ability to pick up items
-- As an added feature, players with this flag start off with a canceled PlayerPickupItemEvent
|
| |
|
| |
|
|
|
|
| |
Fixes BUKKIT-2618 and BUKKIT-2561
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When a mob is marked with the persistent flag (animal or anything with
setRemoveWhenFarAway(false)) the entire block of code for checking if they
should be despawned is skipped. However, one part of this code updates the
mob state if a player is close enough to them. It turns out this state is
used by the AI system to decide if the mob should move around randomly or
not. To stop mobs from being frozen in place we now update this state if
the persistent flag is set as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently when a plugin wants to get the location of something it calls
getLocation() which returns a new Location object. In some scenarios this
can cause enough object creation/destruction churn to be a significant
overhead. For this cases we add a method that updates a provided Location
object so there is no object creation done. This allows well written code
to work on several locations with only a single Location object getting
created.
Providing a more efficient way to set a location was also looked at but
the current solution is the fastest we can provide. You are not required
to create a new Location object every time you want to set something's
location so, with proper design, you can set locations with only a single
Location object being created.
|
|
|
|
| |
Fixes fireballs exploding in the shooter's face and not having a shooter for the projectile. (Two birds with one stone!)
|
| |
|
|
|
|
| |
Thanks for the commit @mrapple
|
| |
|
| |
|
|
|
|
| |
Also set to this value if the persistence hasn't been updated
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The old default for the persistent flag on mobs was false which was then
written out to their NBT data when they were saved. We now use this data
for all mobs, not just non-animal mobs. However, this means animals that
spawned before that change will now start despawning like monsters do.
To avoid this we add a new flag to the mob's saved data to mark if the
data was saved before or after we started using it and ignore it if it
was before.
|
| |
|
|
|
|
|
|
|
|
| |
As of 1.4 mobs have a flag to determine if they despawn when away from a
player or not. Unfortunately animals still use their own system to prevent
despawning instead of making use of this flag. This change modifies them
to use the new system (defaults to true) and to add API for plugins to adjust
this.
|
|
|
|
| |
(Also, fix mistranslation for VehicleBlockCollisionEvent)
|
|
|
|
| |
The answer is 42
|
| |
|
|
|
|
| |
This change affects Endermen and Silverfish, adding a data value for the block change event.
|
| |
|
|
|
|
| |
projectiles. Fixes BUKKIT-3058
|
| |
|
|
|
|
| |
Prior to this, there was no way to tell when arrows trigger buttons
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Fixes BUKKIT-2821
Also some formatting...
|
| |
|
| |
|
|
|
|
|
|
| |
If the player is not in Creative (i.e. does not have the ability to
instantly build) we need to decrement the MonsterEgg item stack when used
on a breedable parent mob.
|
|
|
|
| |
BUKKIT-2781
|
|
|
|
|
|
| |
Stale player references will add a player back into the world when
teleporting them, causing a cascade of issues relating to ghost entities
and servers failing to stop.
|
|
|
|
|
|
|
|
| |
On join we unconditionally add the player to the world they logged out in.
If a plugin teleports a player during PlayerJoinEvent in a way that adds
them to a world (cross-world teleport) we end up with one player in two
places. To avoid this we check to see if the player has changed worlds or
is already added to the world we have we skip adding them again.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is a missed part of the original "[Bleeding] Use case from player data
for OfflinePlayer. Fixes BUKKIT-519" commit. It avoids doing (somewhat
expensive) lookups of player data to find the correct capitalization inside
getOfflinePlayers() as we're already loading their name from the player data
and thus have the correct capitalization.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When sending chunks to a player we use their writer thread to do chunk
compression to avoid blocking the main thread with this work. However,
after a teleport or respawn there are a large number of chunk packets to
process. This causes the thread to spend a long period handling compression
while we continue dumping more chunk packets on it to handle. The result of
this is a noticable delay in getting responses to commands and chat
immediately after teleporting.
Switching to a lower compression level reduces this load and makes our
behavior more like vanilla. We do, however, still give this thread more
work to do so there will likely still be some delay when comparing to
vanilla. The only way to avoid this would be to put chunk compression back
on the main thread and give everyone on the server a poorer experience
instead.
|
| |
|
|
|
|
|
|
|
| |
When an event changes the item to be dispensed we check to see if the new
item has special behavior for dispensing and if so pass it on to that
behavior handler. However, we are actually checking the old itemstack and
passing the new itemstack so this check fails.
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a plugin looks up a player that is offline they may not know the correct
capitalization for the name. In this case they're likely to get it wrong
and since we cache the result even after the player joins the server all
future request for an OfflinePlayer will return one with incorrect case.
When looking up a player who has played on the server before we can
get the correct case from the player data file saved by the server. If
the player has never played before this point we cannot do anything and
will still have the same issue but this is not a solvable problem.
|