RitzKid76

I've gone ahead and modified the description to better explain the bug and the steps on how to reproduce it. Hopefully, this matches the bug report guidelines that we are all used to seeing.

I would agree that this was mistakenly resolved as invalid. The resource pack provided perfectly outlines the problem when loaded in the 2 versions written in the description. There was no mention of this change in the snapshot where the problem began. 

At the time of my writing this, 8 users have voted for the issue and 6 have begun watching it.  To me, it seems that others also agree that this is a bug and would like it resolved just as I do. 

Please reconsider this report, and reopen the issue. 

Thanks