I can't think of anything, maybe someone can clarify this. Both seem to do essentially the same things, and seem to be able to do the same things if adjusted appropriately. Can anyone clarify the distinction for me?
That said, I have another question that maybe someone can answer. How do I remove units from points? I've only been able to remove units from regions but not from points. And if you can't remove units from points, then surely this can't be the only difference between points and regions, can it?
region is a region, point is a point. That is pure english. They both define a partial position in space, but point only define the exact location, and region define the area.
so a point is a region with size 0, a region will be a point as center with size.
simple put: when u want to go to the toilet, the toilet will be the region, or the living room is a region. But a point will be your exact position (where u stand).
I've hardly played around with points, and haven't done every last thing with regions, but there are differences.
How about the event, "Unit enters Region"? It's kinda hard to move inside a point. Actually, there is a "Unit enters Point" event, but the way it works is actually "(Units) (enters) within (X) of (point)". One "region" can actually be a conglomeration of regions, creating very complicated shapes that with only points would be a large pain to make conditions. On the other hand, points serve a purpose for simpler tasks. Why make a big circle region if you are only going to use its center point anyway? You could use the region regardless, but I would suspect it's less efficient memory-wise and therefore a bad coding habit to develop.
@Daimon7:
You're basically asking what the difference is between an apple and a peach :) They both are fruits and can be used in similar recipes but they don't have the same flavor !
Eheh, on a more serious basis, you are right, they can do the same thing and be used in the same ways.
But you can use regions of complex shape by adding lots of circle/square and managing their influence (the negative check box on the editor will subtract their shapes).
And if you know how to remove units from region and only have points on your map, just create a region at this point in the triggers with:
Region - Add a Positive circle centered at Center with radius 1.0 to Region
hm yeah i get that but i'm not seeing how they can achieve something the other couldn't without any significant adjustments.
though a region can you give a quick visual on what region you're selecting, an experienced user doesn't necessarily need to see a visual representation, he can quickly figure out the coordinates of the area he wants to affect and adjust the point the same way he could a region (though perhaps i'm underestimating this usefulness as well as overestimating the ability of the user. so choosing whether to use a point or a region seems arbitrary. i'm still not understanding what makes them so different, or why i would choose to use a point in one situation and a region in another situation.
hm that's interesting, yeah, i didn't know you could do that, that's definitely a significant advantage then. I might be missing something but I still don't see why you couldn't just do that with regions or points by themselves but I think for at least being user friendly spltting them up like that seems to offer a significant advantage.
I just did a quick search, as I remembered having to do something of the sort (Killing some units in all the map) and it's actually more simple than what i thought at first !
Unit Group - Pick each unit in (Any units in (Entire map) owned by player Any Player matching Excluded: Missile, Dead, Hidden, with at most Any Amount) and do (Actions)
Actions
Unit - Kill (Picked unit)
You can of course change the filter 'Any' to match your building type, Entire map to the region you want, and 'Any Player' to your liking :)
Here's 2 scenarios, one where you can only use a point and one where you can only use a region:
1) region: Find the number of units within a region. It's impossible to find the number of units in a point since there is a cap of 1 unit per point allowed.
2) point: Tell the AI to cast an ability at a specific location. If you try to Issue an order targeting a region, that's a lot of room for error.
Sure, there are a lot of things can be done with either a point or a region, such as "create a unit at location", but there are also a lot of things that make them distinct.
They're smaller than regions. That's the main thing. Point is X,Y Coords. A Region is X,Y coords, X,Y size and shape identifier. That alone makes it at least double the size of a point. It's possible that it's more work to place something at the center of a region too.
I'm sure the size is negligible for most maps though.
I mostly just use points to comment on the terrain. I think my map references like 5 points in the trigger editor. The rest are just notes to self telling me some doodad or texture looks retarded in it's current location.
I can't think of anything, maybe someone can clarify this. Both seem to do essentially the same things, and seem to be able to do the same things if adjusted appropriately. Can anyone clarify the distinction for me?
That said, I have another question that maybe someone can answer. How do I remove units from points? I've only been able to remove units from regions but not from points. And if you can't remove units from points, then surely this can't be the only difference between points and regions, can it?
region is a region, point is a point. That is pure english. They both define a partial position in space, but point only define the exact location, and region define the area.
so a point is a region with size 0, a region will be a point as center with size.
simple put: when u want to go to the toilet, the toilet will be the region, or the living room is a region. But a point will be your exact position (where u stand).
@Daimon7: Go
I've hardly played around with points, and haven't done every last thing with regions, but there are differences.
How about the event, "Unit enters Region"? It's kinda hard to move inside a point. Actually, there is a "Unit enters Point" event, but the way it works is actually "(Units) (enters) within (X) of (point)". One "region" can actually be a conglomeration of regions, creating very complicated shapes that with only points would be a large pain to make conditions. On the other hand, points serve a purpose for simpler tasks. Why make a big circle region if you are only going to use its center point anyway? You could use the region regardless, but I would suspect it's less efficient memory-wise and therefore a bad coding habit to develop.
@Daimon7: You're basically asking what the difference is between an apple and a peach :) They both are fruits and can be used in similar recipes but they don't have the same flavor !
Eheh, on a more serious basis, you are right, they can do the same thing and be used in the same ways.
But you can use regions of complex shape by adding lots of circle/square and managing their influence (the negative check box on the editor will subtract their shapes).
And if you know how to remove units from region and only have points on your map, just create a region at this point in the triggers with:
Region - Add a Positive circle centered at Center with radius 1.0 to Region
Then you can use this region to remove the units!
@Madlios: Go
hm yeah i get that but i'm not seeing how they can achieve something the other couldn't without any significant adjustments. though a region can you give a quick visual on what region you're selecting, an experienced user doesn't necessarily need to see a visual representation, he can quickly figure out the coordinates of the area he wants to affect and adjust the point the same way he could a region (though perhaps i'm underestimating this usefulness as well as overestimating the ability of the user. so choosing whether to use a point or a region seems arbitrary. i'm still not understanding what makes them so different, or why i would choose to use a point in one situation and a region in another situation.
@HeroicPrinny and Mooyaah
hm that's interesting, yeah, i didn't know you could do that, that's definitely a significant advantage then. I might be missing something but I still don't see why you couldn't just do that with regions or points by themselves but I think for at least being user friendly spltting them up like that seems to offer a significant advantage.
@Moooyaah: Go
hm, turns out i don't know how to remove units from regions haha >.< so i'm not able to take advantage of your advise
edit: figured it out, thanks ^^
@Daimon7:
I just did a quick search, as I remembered having to do something of the sort (Killing some units in all the map) and it's actually more simple than what i thought at first !
Unit Group - Pick each unit in (Any units in (Entire map) owned by player Any Player matching Excluded: Missile, Dead, Hidden, with at most Any Amount) and do (Actions) Actions
Unit - Kill (Picked unit)
You can of course change the filter 'Any' to match your building type, Entire map to the region you want, and 'Any Player' to your liking :)
Here's 2 scenarios, one where you can only use a point and one where you can only use a region:
1) region: Find the number of units within a region. It's impossible to find the number of units in a point since there is a cap of 1 unit per point allowed.
2) point: Tell the AI to cast an ability at a specific location. If you try to Issue an order targeting a region, that's a lot of room for error.
Sure, there are a lot of things can be done with either a point or a region, such as "create a unit at location", but there are also a lot of things that make them distinct.
They're smaller than regions. That's the main thing. Point is X,Y Coords. A Region is X,Y coords, X,Y size and shape identifier. That alone makes it at least double the size of a point. It's possible that it's more work to place something at the center of a region too.
I'm sure the size is negligible for most maps though.
I mostly just use points to comment on the terrain. I think my map references like 5 points in the trigger editor. The rest are just notes to self telling me some doodad or texture looks retarded in it's current location.
You can always switch from region to point anyway within the triggers:
Point to Region:
Variable - Set MyRegion = (Empty region)
Region - Add a Positive circle centered at MyPoint with radius 1.0 to MyRegion
Region to Point:
Variable - Set MyPoint = (Center of MyRegion)
Here's a picture:
Edit: Actually, a point may have a Z coordinate as well.