Brian Sandall
Comments
Date opened: March 3rd, 2014
Snapshots Since then: 39, plus 2 pre-releases (as of now)
Time it would take me to somehow get the code for and re-verify this issue each snapshot: approx. 30 minutes, times 39 is almost 20 hours, unpaid.
Time it would take a Mojang employee to look at the current code and verify and, if necessary, fix this issue: less than 30 seconds.
Sorry if I sound frustrated, but this is pretty absurd. I pointed out the exact line of code and problem, which would literally take less than 1/2 a minute of somebody's time at Mojang to fix or note that it was already fixed somewhere along the line, and then we could mark this as resolved. Is that so much to ask?
I've updated description with further details on how it can be replicated / tested, since there seems to be no progress yet on verifying and / or fixing this issue. Thanks for reading.
Thanks Searge - that is all I wanted to know. Sorry for the rant, but expecting us to look through the code is pretty unrealistic, since the public does not have ready access to the code. Anyway, it's fixed now, issue closed.