Various client messages (and the backend routine to convert graphics<-->world coords) assume graphics coords are 2d (x, y). But all of the graphics' internal logic uses 3d coords (x, y, z). We should settle on one consistently (probably 3d), so the graphics doesn't need to keep removing z coordinates when building messages.
Various client messages (and the backend routine to convert graphics<-->world coords) assume graphics coords are 2d (x, y). But all of the graphics' internal logic uses 3d coords (x, y, z). We should settle on one consistently (probably 3d), so the graphics doesn't need to keep removing z coordinates when building messages.