Cameron Craig

I've noticed this bug in back in 1.14.4, and it's still present in 1.15.2 (and 20w12a as far as I'm aware).

This bug is still around in version 1.15.1, someone please get around and fix this before 1.16.