This bug is still in 16w06a, is there any plan of it being changed or is it stuck in the game, unable to be resolved?
Oh I thought I looked up before to see if it was a duplicate issue, but didn't see anything about it. Sorry for taking up your time.
This bug is still in 16w06a, is there any plan of it being changed or is it stuck in the game, unable to be resolved?