| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
This class is a general purpose task execution system, that uses stages
to separate processing blocks for asynchronous and synchronous
executions.
|
|
|
|
|
|
|
| |
When a player has canPickUpLoot set to true the code for mob pickup is
triggerd which does not know how to deal with player inventory. Since
players have their own logic for picking up items we simply disable this
code for them.
|
|
|
|
|
|
|
|
| |
The old flag for picking up loot was default to false, making existing players not able to pickup items. We now use this flag for Players, which gives us the problem we had in 48b46f83.
To fix this, we add an incremental flag that will be cross-examined to check if the data was saved before or after the flag level was introduced.
Addresses BUKKIT-3143
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
org.bukkit.craftbukkit and net.minecraft.server will now include the
minecraft version in the package name. As the internal implementations
are known to change dramatically, this refactor reduces the strain on
support requests due to version mismatching.
org.bukkit.craftbukkit.libs will also have version numbers for each
imported set of packages. These are not dictated by the minecraft
version number. This is done to prevent future incompatibilities.
|
| |
|
|
|
|
| |
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.
|
| |
|