If I want to write a anti-scanner code for the position system in a RTS (or any other app )
how about, the map is
( x,y )
x = 1~100000
y = 1~100000
yet the real size of the map is only
( x,y )
x = 1~1000
y = 1~1000
and then the unit and buildings would have their positions randomnize a lot, like this
on the visual map, a unit is actually at x = 50000, y = 50000,
but it wouldn't make a difference in fact, because it's position number is changed around a lot, but it doesn't change to a value larger than what would be considered a real move by the player, the values simply change around a lot..
I sound like a broken record, but how about this:
the map is (x,y) and x =1~100, y=1~100,
and then unit would have ( 50.1234234, 50.2341231 )
what keeps changing around is the numbers behind the decimal, in this case as long as it's only behind the decimal, the unit actually stay put.
how do you solve this trick ?