So yeah, I completely misread what you wanted to do here - you didn't want to move units from a unit goup to 20 random points, but have 20 manually selected random points that you can later use to without repeats, so... Yeah, here's how you can do it:
a) Set your region array variable manually:
-
Actions
-
Set PointCount = 19 -- integer; value = n-1, where n is the number of points
-
Set Point[0] = (Center of <Region1>)
-
Set Point[1] = (Center of <Region2>)
-
Set Point[2] = (Center of <Region3>)
-
...
b) Then once you move a unit, do this:
-
Actions
-
Set Number = (Random integer number between 0 and PointCount)
-
Unit - Move <your unit> instantly to Point[Number]
-
Custom script: call RemoveLocation(udg_Point[Number])
-
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
-
If - Conditions
-
Number Not equal to PointCount
-
Then - Actions
-
Set Point[Number] = Point[PointCount]
-
Else - Actions
-
Set PointCount = (PointCount - 1)
Let's explain how this works - we have 20 points (array indexes 0-19). The first thing that happens is that the trigger selects a random index number and by extension a random point from your pre-defined list. It then moves the unit and then removes the point. Let's consider 2 options:
a) The point selected had the maximum index number, i.e. 19 - in this case, Point[19] no longer has any value and we don't want to draw it again, so we decrease the maximum index number (PointCount) that can be selected by 1. The next time the trigger runs, it will pick between region indexes 0-18.
b) The point selected had an index number smaller than the maximum, e.g. 10 - now, the next time this runs, you want to draw any number other than 10 as that point was already used and removed, but how do you tell the game to exclude 10 from the next draw? Well, you can't, but what you can do is move the last point from the array to index 10, so that this index now contains a point that exists and wasn't used before.
However, while we removed an "empty index" from our array, we now have one value that's stored under 2 indexes - the point that was originally stored under index 19 is now also stored under index 10. That's unnecessary, so we reduce the maximum index by 1, thus going back to having a full "list" of unique points numbered 0-18 that we can use to draw from
---
Anyway, since my first answer missed the mark, I also played around with something similar - getting randomly selected points that are at least some distance from each other and storing them in an array for future use - basically the same my first idea, but with no units involved.
I know this isn't exactly what OP wanted, but since I've already done it, I'll post it anyway in case someone finds it useful:
... Dies
Events
Hero - Instantly revive Rezing_Hero_Hev_Var at Rez_Pt_Var[Ran_Num_Rez_Var], Show revival graphics
