[MC-13838] SMP Mounting Horse NPE

I tried mounting a horse bareback in SMP and the server kicks me: Internal Exception - NullPointerException.

There's no stacktrace on the server console, only me disconnecting and a single line of debug code.

2013-04-18 18:24:12 [INFO] SnoFox[/67.182.0.0:49634] logged in with entity id 1041 at (1026.2139547745503, 68.7000000178814, 600.816943866349)
[GC 339666K->164539K(1034048K), 0.1117042 secs]
2013-04-18 18:24:13 [SEVERE] Reached end of stream
2013-04-18 18:24:13 [INFO] SnoFox lost connection: disconnect.endOfStream
removing player mount

Linked issues

duplicates 1

MC-13628 SMP/LAN: NPE when right clicking horses Resolved

Comments 5

Anon Ymus 2013-04-18T23:46:35Z

Duplicate of MC-13628, please use the search function to see if your bug has already been submitted. Currently over 54% of tickets are being closed as duplicate.

Josh Johnson 2013-04-18T23:59:07Z

Uh, sorry. The search link on the MC dashboard yields all of three results for "Future Version - 1.6". Since the link is unlabeled, I had assumed it was existing issues. After scanning the descriptions for "horse", I decided the bug hadn't been reported yet. However, I didn't notice that the search query is for Resolved + Fixed bugs.

This is somewhat misleading to someone quickly trying to drop in a bug report. Perhaps the search should be labeled to reflect what the link actually leads to.

Anon Ymus 2013-04-19T00:20:21Z

There shouldn't be any bugs for 1.6. They should be filed under 13w16a.

Josh Johnson 2013-04-19T00:26:35Z

In that case, there shouldn't be any Fixed Bugs either. >.>

Torabi 2013-04-19T16:56:28Z

Why not? By marking a bug as fixed in a specific future version, that means that while they may have not fixed it in any public release (stable, snapshot, or pre-release), but intend to do so for that version. However, anyone not on the dev team has no ability to determine whether or not a bug will exist in a future version, and in fact, by reporting a bug, you're decreasing the likelihood of that bug surviving in the future version. Thus, marking a bug as existing in a future version based on its existence in a current version is silly and contradictory behavior. Not to mention makes keeping track of bugs difficult, which works against the whole purpose of having a bug tracker.