Blocks are placed in the wrong location if camera axis moves during placement

Or, to put it another way: The mod acts as if it is computing block locations server-side when actually placing, rather than client-side. This is particularly obvious with slabs: If there is any latency at all, then if I’m rotating and/or moving the camera (Steve) while placing slabs, they will almost always end up in the wrong location.

When this happens, the primary block placed (the block that would be placed even without the mod, as opposed to the extras in e.g. array mode) is placed correctly, but the others are often off by half a block or more.

Assuming my analysis is correct, a correct fix would be to compute the placement locations client-side and send them to the server for verification (e.g. using a custom packet), rather than attempting to run the same code client-side and server-side.

Comments (3)