The map border considered harmful

I am probably mocking Dijkstra but still. The map border is dangerous, stay away from the border! I mean it.

I found out that it is very easy to screw the handle indexes if you create or move units to the map 's border. Specially if SetUnitX/Y natives are involved.

I think that the best thing is simply to let the map's border be away of the gameplay.

You can just use bigger camera bounds (2 tiles per side is enough) and then simply use boundary.

In my case I am gonna make the default border offset for CS_MoveUnit 256, so maps will require to mantain at least 2 tiles of distance from the border as a requirement to use the caster system.

What do you mean screw with? Are there no visible effects? And ha, ha.

I think it is more about SetUnitX and SetUnitY, I thought that 128 was enough of an offset but it seems that it must be at least 256. And what happens is that when you create handle it gets the index of a living handle, like the DestroyTrigger bug or the timer set to null bug

Waaait. So if you move a unit too close to the map border with SetUnitX/Y, the handle id gets recycled and is used by other handles? O.O?

wait!

CS_RectLimitOffset in hydra/ragingcharge map: (cs 13.2) : 128.0

CS_RectLimitOffset in newest caster system: 50.0

It seems that the problem is a little more bizarre than I thought let me see

Yeah map crashes if units get to close to the border, i had that problem in a map, i found it cuz once it crashed for me, the solution is simply increase the map size (if you can)

I agree, map borders are evil. It's the twisting nether!

i think it's crap... or simple make a test move unit to the border and check it's handle index (pereiodicaly) and create new object's (timers) and check it's handles ! if they will be the same you are right ! and i mean the handle of unit and timer must be the same !