Region Offsets

Thats about the size of the region I am using (in-game).
What I want to do, is create a gravestone around a unit so they can't move much, but I don't know much about offsets. I just played around with them and I am pretty sure it can make it so a gravestone spawns around all of the edges of that region. I have to go to sleep now so I'll check this in the morning.

If anyone knows how I can do this, please post.

Thanks.

Offsets require a grasp of cartesian coordinate system. lets say you wanted the box dimensions to be 500 x 500. This essentially means that the north edge gravestones all have the same Y coordinates, so you just need to find the Y coordinate of the center.

Take the Y coordinate of the center and add (or offset if you will) by 250. All gravestones on the north side will have this Y coordinate, but differing X coordinates. So if I created a gravestone at every 50 distance, I would place them at origin location offset by (-250,+250), (-200,+250), (-150,+250), (-100,+250)...(0,+250), (+50,+250)...and (+250,+250). For the south edge I would repeat this with the X offset, but instead of offsetting the Y by +250, I would offset it by -250.

For the east and west edges, the X remains the same while the Y changes. So in this case, the offset would look like this (+250,-250), (+250,-200), (+250,-150)...(+250,0), (+250,+50), (+250,+100)...(+250,+250). Once the opposite side would use -250 for the X offset instead of +250.

Hopefully that gives you an idea of what you were asking.

That gives me a better idea, yes. But how do I find out exactly how big the region is?

In gui you can set a real variable to the proper values, min and max of both x and y. Which will give you what you need.

Ok I made a region variable, I have this code:

And it makes them like this:
Where X is the target, and the +'s are the gravestones.
Why is that??

I'm not sure why it's doing that, but instead of using regions, try using locations. If you are needing regions to know when units are entering a location, you can just as easily use coordinates

just set RVariable = Target Point of Ability Being Cast and use that as your location instead of center of region.

I changed the variable to a point, and it does the same thing..

It happens due to collision of units. Just set physical size of graveyard unit to 0 (field "collision" in OE) and enjoy.

K so thats what I got, and its massive, it lags for about 2 seconds when cast.


Two problems:
The lag, I need to make it so it doesn't lag as much, how can I do this?

I set the spell so I can cast it on my allies, it stuns them, and I cannot walk through the gravestones.
But when I cast it on an enemy, and they attack me, and I run away, they can run right through them and get me... How can I fix these problems?

Thank you.

Loops are your friends:
That also fixes your location (point) leaks. "TempPoint" is a point-type variable; "Offset" is a real-type variable.

The problem with running through them is that in order to create the units at the proper spot the units need to not have collision, but then they can be walked through. The only solution is to give the gravestones back their collision and then use some Custom Scripts:

Your lag is the unfortunate side effect of using gui. It is inefficient if you haven't already try learning jass because you can do this very easy, organized and with little to no delay.

Use Pyro's answer it should work!

I get this error with 'jasshelper':
Cannot convert rect to location

On this line:
call SetUnitX(bj_lastCreatedUnit , GetLocationX(udg_TempPoint))

here is my code...:

That's an odd error.... I can't see why that would occur. Unless "TempPoint" isn't defined as a point variable in the variable editor. I think this line needs to be changed:
To this:

Also, you've mixed up a line; your line for creating the GreaveStones should look like this:

Ugh ok I changed some confusing variables; It semi-works. It creates 3 at the location but they are a bit messed up, and then it makes the rest at the center of the map..

This line should be the last of the trigger, not inside the loops: