MonsieurApple

The MC developers are busy, just give them time. Seriously.

Thank you for reopening. Rory, could you add Minecraft 1.8 pre 3 as an affected version?

I don't believe this is intended for the Ender Dragon. This was the behavior for the wither, but not the ender dragon in 1.7. During the final boss fight, if the ender dragon leaves your view, you can no longer see the boss bar. This is definitely a bug and makes the end fight much harder.

Still an issue in 14w34a and 14w34b. It appears the limit was set to 100 (5x20). The old limit used to be 60 (3x20). 80 might look better (4x20).

Screenshot: http://i.imgur.com/SJyEi84.png

Thank you for the clarification.

Could you please link to the bug tracker rules?

It's clearly an issue. Sure, a hard limit is probably not the best solution. It's just something that was mentioned as a possible solution. Reopen this ticket and let the MC devs figure out the best solution for themselves.

Also, the current behavior in the snapshot is much less ideal than cutting off at more than 60 players. The tab list on large servers goes from displaying most info to completely unreadable.

I'm not at home right now, I'll get the logs once I'm at a computer.

In every other version of MC the tablist is limited to 60 players so it renders properly with large amounts of players. With the snapshot they allowed for the server list to expand dynamically, however, no limit was enforced. The rendering is extremely poor and should be considered a bug. Cutting off players when there are more than 60 players online would replicate the behavior in every other version of Minecraft, however, it's up to the Minecraft devs how to fix this issue. I'm just giving one possible solution to this bug.

Reopening this issue would be appreciated.

@banana478 Please reopen this. Not only is this a valid bug report (not a feature suggestion), but the hard coded limit that I mentioned was discussed WITH Mojang developers Dinnerbone and Grum in IRC.

He was just adding helpful information to the bug report, no need to jump on him

It was fixed in 1.7.8 by allowing expired skin blobs to be considered "valid" when verifying, however, it will fetch a new blob from the server if the blob is expired (as opposed to crashing everyone).

Amaranth: From what I originally saw only the UUIDs were verified to match. However, I suppose this could have changed when Grum decided to push an update today.

Anthony: In addition, the current system does not prevent me from setting my user's skin to Notch then changing my overhead name to Notch (as far as I'm aware).

Anthony: If the real reason Mojang wants this is to prevent fake Notch NPCs, all they need to send with the player spawn packet is some sort of session ID. The client requests the skin using that session ID to see if Notch has actually joined the server. If it doesn't work out, the client falls back to a Steve skin.

Amaranth: The other option is to not serve skins from the server.... there's no way to let the server serve skins without somehow being able to tamper with them and use magnitudes more data than if Mojang just served the skins themselves. For example, right now, I can give my player with a skin a different name or even holdback a skin change for 24 hours. Neither of those would be possible if Mojang kept serving skins themselves.

Skins should not have an expiry time. There's no way (as far as I'm aware) to give skins an expiry time and have them served server side.

Not only does this new method (server sending skins in player spawn packets) use magnitudes more data (skin data must be resent every respawn, move in/out of view, etc), but it also causes issues for players and could possibly let servers hold back skin changes.

Amaranth: Why on earth is it fair to punish a player (kicking them) for playing the game as intended?

AgentK brings up a good point. We have to resend the data every time a player respawns or moves in/out of view. Not sure to what extent the client caches that data, but we shouldn't need to be resending it so often.

Anthony: Disagree partially. Why should users not see skins if they've simply been playing for a while or AFKing? Unverified skins, however, should safely fallback to Steve.