@above:
i thought Headcrab was referring to the question about crosshair.
setPosition, used on a player, crashes blockand for some reason.
player.setposition("x y z");
However, position = does not.
player.position = "x y z";
I found out what happens at extreme axis values. Tested on Creek map.
At 1k, nothing. This is a normal, walking-reachable(in about half an hour maybe :P) value.
-Nothing. Just for comparison.
At 10k, almost nothing. Stuff starts vibrating maaaybe a little.
-No visible difference. Almost.
At 100k, water and your player twitch.
-Water twitches
-Player twitches
At 1mil, stuff breaks.
-Hard to build
-Particles are misshapen
-Ground has holes
-Water has holes and is badly misshapen
-Vehicles shake some
-Short bricks disappear almost completely
-A tall column of bricks appears to be bent and twisted
-Player looks odd
At 10mil, a lot of stuff breaks and your blockland freezes eventually.
-Holes in the ground
-Ground collision is separate from ground appearance
-Can't place bricks right
-Projectile trails zigzag crazily
-Can't move until at extreme velocity, then you shift over a long way
-Water has lots of holes
-Terrain and water shift holes and shape crazily
-You can fall through the ground in places
-Can't see bricks right
-Player twitches crazily
-Held item separates from hand
-Other stuff breaks
-Potential blockland crash
-Player resizes crazily
At 100mil, calamity.
-Player resizes to no end
-Held item resizes to no end
-Stuff breaks
-No terrain
-No water
-Falling endlessly
-Can't move
-Can barely see
At 1bil, nothing. Similar to player-deleted.
-Images leave trails
-Can't see because of above
-I think i got some console errors
-Stuff probably breaks
-Can't move
-Can barely see chat
You can't go to 10bil. It sends you back to the start.
-Sends you to 0 0 0
-Possibly gives an error saying how stupid you are