Bye. It is you who refuses to understand. I'm telling you and everyone else who has the misfortune of shovelling through this crap that I have TESTED it and it does desync. We tested it MULTIPLE TIMES TO BE SURE. Does it desync in the most recent patch? I don't know. but it did 1-2 months ago. I adopted/created a synced GetZ that solves this problem permanently and efficiently, so this isn't an issue for me anymore, but it might be for some other people. For those who are curious what exactly can desync in the map here is the boiled down test case: Fire a missile (Missile.j) over this terrain segment and then walk your units around (probably to trigger a movement update event in the netcode). result was a near instant desync. This requires someone using reforged and someone using classic. This particular terrain was created with steep cliffs in WE JNGP. In reforged GetLocationZ will return (0-0.5) difference for some reason in some of the "squares regions in the grid" on the decline portion of the terrain.