If you could I would be interested yes
world-pos 1855,88,-833, local-pos 15,88,15 on a chunk border to the +x/+z side, but not on y-physics-chunk border.
placing a block at 15,88,14 the issue corrects itself on the server, but strangely the physics-chunk delta on the client produces a physics-chunk 1-y taller than the server one… removing the block again and the server chunk again has the issue for the original block…
placing a block underneath at 15,87,15 corrects the issue for the original block, but the block underneath now has the issue instead, again client mesh remains correct, and again removing it the server chunk goes back to the original one being broken… rather strange considering its literally the same code being executed.
placing a block above, the server chunk has correct physics for the new block, but the original remains broken. again removing the new block resets to original broken state.
copy-pasting the setup 16blocks along the z-axis, the same block in the new place has the same issues straight away, copy-pasting 16blocks along the x-axis, no issue. Happens even if manually placing the block 16z along, so no weird lingering dodgy block data causing it… still server-only.
should be enough to figure out wtf is going on. aaaand reproduced locally! yay! so not even some crazy linux/windows platform difference since my client is on linux too now.