The basic theme is this:

I have 8 locations and protoss beacons owned by neutral player. I want to move a beacon to one of the 8 locations randomly every so often, BUT, only if that location is not already occupied by a beacon or any other units -- if this is the case, then I want to reroll the randomization process and start again so it can put it in an unoccupied location.

The randomization works, but for some reason, about 10% of the time, a beacon will be moved to a location that already has a beacon in it. Either that, or the beacon that already is there isn't getting deleted? I'm not sure which, can't tell.

Anyways, here are the triggers.













So that's basically it. And then those last two triggers are repeated for locations 1-8 (hills 1-8). Any help guys? Thank you!

---

---

SOLVED ... after about 6 hours lol

SO

APPARENTLY

Starcraft does not recognize Protoss Beacons (whether it's protoss beacons in general or just protoss beacons owned by neutral player) in the bring condition using "ALL PLAYERS". HOWEVER, it does recognize neutral owned protoss beacons if they are specified by player.

EX:
Condition:
All players bring at least 1 protoss beacon to X
^if the beacon is owned by a neutral player then StarCraft wont recognize it.

BUT
Condition:
Neutral player brings at least 1 protoss beacon to X
^StarCraft WILL recognize it.


This is weird because you can use things like the Move action to recognize neutral owned protoss beacons.
EX:
Condition:
Whatever

Action:
Move 1 protoss beacon owned by All Players at location X to location Y
^the beacon is owned by neutral and StarCraft will recognize it and move it.


So for some weird reason the BRING CONDITION does not recognize neutral player protoss beacons, but other actions do.

Basically what I had to do is create 5 triggers per random switch result.
So for Switch 1 set, Switch 2 set, and Switch 3 set, I had to create 5 triggers, which are:
1. Reroll if all players bring any unit to location X (used to detect if humans bring marines or whatever there)
2. Reroll if neutral player brings at least 1 protoss beacon to location X
3. Reroll if computer player 7 player brings at least 1 protoss beacon to location X
4. Reroll if computer player 8 brings at least 1 protoss beacon to location X
5. Move beacon because there is nothing in location X

Very tedious, arduous and stupidly random lol. IDK why it works this way but I guess we all know SC is a strange bitch. Oh well, there's one new thing learned lol

Post has been edited 2 time(s), last time on Sep 24 2017, 3:59 am by m.0.n.3.y.

I play a wav file when the hill gets moved successfully so maybe that messes something up?

SOLVED ... after about 6 hours lol

SO

APPARENTLY

Starcraft does not recognize Protoss Beacons (whether it's protoss beacons in general or just protoss beacons owned by neutral player) in the bring condition using "ALL PLAYERS". HOWEVER, it does recognize neutral owned protoss beacons if they are specified by player.

EX:
Condition:
All players bring at least 1 protoss beacon to X
^if the beacon is owned by a neutral player then StarCraft wont recognize it.

BUT
Condition:
Neutral player brings at least 1 protoss beacon to X
^StarCraft WILL recognize it.


This is weird because you can use things like the Move action to recognize neutral owned protoss beacons.
EX:
Condition:
Whatever

Action:
Move 1 protoss beacon owned by All Players at location X to location Y
^the beacon is owned by neutral and StarCraft will recognize it and move it.


So for some weird reason the BRING CONDITION does not recognize neutral player protoss beacons, but other actions do.

Basically what I had to do is create 5 triggers per random switch result.
So for Switch 1 set, Switch 2 set, and Switch 3 set, I had to create 5 triggers, which are:
1. Reroll if all players bring any unit to location X (used to detect if humans bring marines or whatever there)
2. Reroll if neutral player brings at least 1 protoss beacon to location X
3. Reroll if computer player 7 player brings at least 1 protoss beacon to location X
4. Reroll if computer player 8 brings at least 1 protoss beacon to location X
5. Move beacon because there is nothing in location X

Very tedious, arduous and stupidly random lol. IDK why it works this way but I guess we all know SC is a strange bitch. Oh well, there's one new thing learned lol

That's the reason we love Star Craft mapmaking so much! Maybe it's not the beacon itself, but like All Players doesn't include Player 12 in conditions at all?

Also you can do it with at least 9 less triggers and 1 less switch:





Post has been edited 3 time(s), last time on Sep 24 2017, 12:20 pm by Wormer.

Yeah I'm not sure! More testing would be needed to figure out the specifics. I'm just curious WHY it would be that way. There's got to be some logical explanation lol?

Actually I think I need all the triggers, because I need it to be like an OR statement. Where if All Players brings exactly 0 [any unit] to Hill N, OR, Neutral brings exactly 0 Protoss Beacon to Hill N, then reroll the randomization process.

Putting both All Players brings exactly 0 [any unit] to Hill N AND Neutral brings exactly 0 Protoss Beacon to Hill N makes it an AND statement where both of them have to be true in order to fire, right?

This is only the one of the many weird things.

Yes, my trigger has AND. You can do OR with an additional location and 2 more triggers.

Wow this quirks thing is really useful! Wish i had seen this before haha