I have a problem with my map. I have crated a Mini Game where player 1 can turn it on/off.

The triggers shown below are also for players 3 - 5. When I turn off the Mini Game, it only turns it off for 1 player when it should turn off for all.



Post has been edited 1 time(s), last time on Jul 29 2010, 4:22 pm by Radioactive.

Yeah, you're moving the unit away, which causes the bring condition to only be true once.

If you want to turn on the minigame for everyone, then have Player 1 deaths of cantina be the switch. When you bring a unit to the location, turn it on. When you bring the unit off the beacon, turn it off. If player 1 deaths of cantina is 1, then the minigame can be activated by all players. You can also have this toggle. Make sure you only use one death count to turn on off (ie not player 2 deaths of cantina).

If you want to turn it off individually per player, but still have player 1 control it, you need to figure out a way to differentiate. I doubt you want to do this though.

The first trigger - running for Player 1 - will disable all the rest of the triggers because it moves the Human off the beacon or whatever. If the Human is moved in the first trigger, it won't be there to trigger the remaining triggers.

Post has been edited 1 time(s), last time on Jul 29 2010, 7:53 pm by ImagoDeo. Reason: removed elitist tone - sorry

Not sure what you guys are talking about, the bring condition runs only once but that should be enough. From what he gave us we can only assume that Cantina=0 means it's On, and Cantina=2 means it's Off. When Player 1 brings the human to 'M On', then Player 2's deaths of Cantina=0, so it'd be On, and the same for the other way around.

To me it looks like either another unlisted trigger is affecting it, or you've improperly concluded the On/Off states.

Not sure how you don't assume he's got:
P1 brings exactly 1 human to m on:
p3 has suffered exactly 2 deaths of cantina
set p3 deaths of cantina to 0
move all human owned by player 1 to minigame
which of course will never fire, because player 1 can never bring 1 human to m on if he's in minigame.

Sure it will, player 1 can bring 1 human to M On if it's ordered there. Yes, it'd be moved afterwards, ensuring that the trigger would only run once, but P2's deaths of Cantina was still set to 0, so the minigame is On.

Apparently a couple people in this thread don't understand how the triggers are supposed to work.

As presented, they will work fine, so something's been left out. If you PM me the map, I will tell you what the issue is.

Unnecessary tone bolded for emphasis. This is the UMS Mapmaking Assistance forum, it exists for threads like these. If you don't want to read what you perceive to be stupid questions, then this is not a forum you should be viewing. Ever. If you want to be an elitist embarrassing inexperienced mapmakers, there's plenty of other forums to post in. You're not assisting anyone by talking down to or belittling them like this.

did you even read my triggers? p3's deaths of cantina will never change. I never said a thing about p2's deaths of cantina.

I did, I assumed P3 was a typo, considering how Player 3 isn't mentioned anywhere in the triggers he posted. Why bring up a trigger that has nothing to do with his problem?

Of course Player 3's Cantinas will never change. What does that have to do with anything?

Player 2's Cantina is like a "global DC", that is, a DC that isn't player-specific, such as a Minigame State. That said, I don't know how it could be On for one player and Off for the rest at the same time, it's most likely another trigger effecting something.

Edit: Unless I'm making a huge misunderstanding that those triggers are OWNED by players 1-5, rather than there being 5 duplicates of those triggers, each respective to its owner. In the latter case, Current Player would have done just fine, which is why I might have miscomprehended.

Post has been edited 3 time(s), last time on Jul 29 2010, 7:51 pm by yoonkwun.

If he is using that trigger, it has EVERYTHING to do with the problem.

In any case, a clarification of this point is needed:


If the former is true then I'm correct, the latter then rockz. I'm now leaning more towards his, giving p2 a global state DC seems odd.

I assume that the P2 death count is being used globally, since the action of P1 turning the mini-game on/off is supposed to be a global action. He said the triggers were for P3-5 also, he didn't say he changed every instance of "Player 2" to "Player 3" in the duplicates. As was mentioned, if that was the case, using "Current Player" would have been much more appropriate.

If each player is using their own death count instead of a global one, then that is the issue. Two easy ways to fix this:

1) When P1 brings a unit to 'M On' or 'M Off', have it change the death counts for Force 2 instead of each player.

or

2) Have it change the death counts for Player 1 instead, and base all the triggers off Player 1's current death count.

If that is the case, then either one will fix the problem. The issue isn't that the unit's being moved, it's that the unit moving is a global action and you're both changing and checking death counts player-specifically based on it. It should be an easy fix for you, tweaking one trigger action will solve it.

Edit: If you're still having trouble with it at this point, as I said, PM me and I'll tell you what's wrong. In the future, note that it is helpful to give as much information as possible. In this case, showing an example of both P2's and P3's triggers would have resulted in the problem being solved faster, since there's no way to know which variables are different between P2's and P3's triggers.

Post has been edited 2 time(s), last time on Jul 29 2010, 9:09 pm by Azrael.Wrath.

I solved the problem after post 3. Even if I bring a unit to a location, they meet the same conditions before a trigger moves it away. Are you saying that I can't run multiple triggers at the same time?

Triggers are run sequentially, from top to bottom, one at a time, each cycle.
You can run triggers "at the same time" insofar as they are all checked and executed in the same trigger loop, but triggers can not run simultaneously in a sense that would violate the sequential order. All the effects of executed triggers in one trigger loop will appear to have occurred to us at the same time, but the triggers were still run one at a time from top to bottom.

It's always the same with computers, everything is processed one thing at a time (ignoring multi cores). The same is for StarCraft triggers.
First all of P1's triggers are checked, then all of P2's and so on. This leads to the confusing fact that if you mark more than one player in the trigger overview in ScmDraft that the triggers are not ordered in the way they are checked.