Safely handle relocation Y values above maxHeight

I haven't observed it, but I worried that using != instead of <= in the comparison could lead to infinite loops or null pointer exceptions on large player Y values, if it ever occurred.