Connor James
- conehead
- conehead
- Europe/Stockholm
- Yes
- No
I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the
identicalobjective names.I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the aforementioned duplicate objective name.
I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the
aforementionedduplicate objectivename.
I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
.I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
Quick edit here: the game also crashes if an objective-deletion packet is received and the client has not been previously informed of the objective
I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
Quick edit here: the game also crashes if an objective-deletion packet
is received and the client has not been previously informed of the objectiveI fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
Quick edit here: the game also crashes if an objective-deletion packet with a name unknown to the client is received
I fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
Quick edit here:
the game also crashes if an objective-deletion packet with a name unknown to the client is receivedI fully realize this may be a silly bug report; a crash like this is likely fully normal for a development snapshot (and this one in particular even useful while debugging the scoreboard). Making sure it doesn't slip through to final release regardless.
If you send two scoreboard objective-creation packets to the client with the same objective names, the game will crash with an IllegalArgumentException referencing the duplicate objective
Quick edit here: The game also crashes if an objective-deletion packet with a name unknown to the client is received, however the game does not crash if you send a scoreboard display packet with a name unknown to the client.
Scores that are displayed in the player list (tab) no longer display properly for a player if he has been assigned to a team with the color option enabled.
I have attached a world file with the exact command block workflow. You will have to use it on a snapshot server, as it seems the player list can not be brought up in SMP (unless you've opened it to LAN and someone joins).
Steps to reproduce:
1. Create an objective
2. Set the objective to display in the player list
3. Give yourself anyarbitrary value for this objective
4. Add a team
5. Set the team color option to anything other than white
6. Add yourself to the teamAt that point, any values you add/remove/set to the player list objective won't be reflected in the player list for anyone in the team.

This has been resolved as of 13w06a.
Affects 13w06a as well.
Still an issue in the 1.5 release.
(to be clear, if you're using the supported Bukkit Scoreboard API you won't get this crash)