Implement Scoreboard API. Adds BUKKIT-3776
This implementation facilitates the correspondence of the Bukkit Scoreboard API to the internal minecraft implementation. When the first scoreboard is loaded, the scoreboard manager will be created. It uses the newly added WeakCollection for handling plugin scoreboard references to update the respective objectives. When a scoreboard contains no more active references, it should be garbage collected. An active reference can be held by a still registered objective, team, and transitively a score for a still registered objective. An internal reference will also be kept if a player's specific scoreboard has been set, and will remain persistent until that player logs out. A player's specific scoreboard becomes the scoreboard used when determining team structure for the player's attacking damage and the player's vision.
This commit is contained in:
@@ -126,7 +126,7 @@ public abstract class PlayerList {
|
||||
}
|
||||
}
|
||||
|
||||
protected void a(ScoreboardServer scoreboardserver, EntityPlayer entityplayer) {
|
||||
public void a(ScoreboardServer scoreboardserver, EntityPlayer entityplayer) { // CraftBukkit - protected -> public
|
||||
HashSet hashset = new HashSet();
|
||||
Iterator iterator = scoreboardserver.getTeams().iterator();
|
||||
|
||||
@@ -277,6 +277,8 @@ public abstract class PlayerList {
|
||||
entityplayer1.playerConnection.sendPacket(packet);
|
||||
}
|
||||
}
|
||||
// This removes the scoreboard (and player reference) for the specific player in the manager
|
||||
this.cserver.getScoreboardManager().removePlayer(entityplayer.getBukkitEntity());
|
||||
|
||||
return playerQuitEvent.getQuitMessage();
|
||||
// CraftBukkit end
|
||||
|
||||
Reference in New Issue
Block a user