Say P1-P4 are in force 1. Now say P3 leaves.

Conditions:
W/e.
Actions:
Set deaths for Force 1 to 5 for Cantina

Does P3 have 5 deaths of Cantina?

As long as the trigger isn't under Player 3, then yes, the player should get the deaths.

The trigger will not, however, execute for player 3 once player 3 leaves. If the trigger was, for example, set deaths for current player under force 1, player 3 would not be affected. Just clearing that up; it's pretty unclear above.

You should avoid using a "force" grouping in both the owner and the body of a trigger because it is bad form and risks multiplication errors. (e.g. force 1 // add 5 deaths to force 1 would add 5 deaths per player, probably not what you are expecting).

Ah yea, it was for "Force 1"
But P1 is still in the game, so it WILL set the deaths for P3 even thought P3's trigger won't run, correct?


As for the "bad form" comment, there's no such thing as "form" lol, there's only what works correctly, and what does not work correctly.

I particularly avoided the "add deaths" command in using the Force rather than individual players, but I'm hoping to be able to simply make a Force trigger to save myself some work, so I will not avoid using Force unless I have to. Thanks for pointing that out though, because it might Set it to 5 four times, whereas I might only want it Set once.

I would disagree. While there isn't really universally accepted and standardized "form" or convention which mappers adhere to, following certain conventions allow for easier to follow triggers as well as limiting the possibility for error such as the one DTBK pointed out. Avoiding forces is also a good idea if trigger order matters. Overall it avoids confusion in the long run. In the end it's entirely your choice to whether to follow "form" or not, but you can't say it does not exist, even if what you think is bad form is different from what DTBK thinks. However, if you're comfortable with using forces and know what you're doing then by all means do it.

Avoiding forces also doesn't mean it takes more time to create the trigger, instead of applying the trigger to a force you just apply it to the players in the force (checking them off). This is so what you can see each copy of the trigger in the list of each player's triggers.

It's really no different than actual programming languages.
http://en.wikipedia.org/wiki/Programming_style
http://en.wikipedia.org/wiki/Code_conventions

No.
It will set P3's death if you use Player 3 explicitly but when he left he won't be included in triggers affecting the force.

Are you certain of that Nude? It's not under Force 1, it's adding the deaths TO force 1, otherwise I would think the same thing.

I am certain.
At least when the player was never there, and I'd say it's safe to assume that the triggers won't work differently if the player was there but isn't anymore. Unfortunately I can't test trigger behavior of leavers when I'm alone.

That's all I meant.

I might as well just go test this myself, no offence Nude but I'd rather not assume it's the same.

Fat lot of help you guys were
I'm only joking, thanks for your consideration

Why?
There's no sign in any other trigger behavior known to me that Neutral Players (Leavers) have different rules than Ghost Players (Open Slots). Why should this case be any different?
The only difference is that leavers have units which are given to another player (P12) where open-slot-players do not get any units created to give to P12.
So I'm positive triggers affecting the force won't affect leavers. Period.

But if you create a unit under a force for Ghost Players, it creates it for all players, those there or not, so I assume that it will still run the trigger since it's affecting the player, he has it AFFECTING them, not running it FOR them.

If you REALLY want to make sure, make a test map and I can test it(I have 2 computers)

Testing yourself is always the best and most conclusive option, and most of the time the fastest especially when it comes to little things like this.

I don't even remember a lot of these things offhand, when I usually just test for little things like this when I need to use them.

creates 1 unit when there is only 1 player in the game.

Post has been edited 1 time(s), last time on Apr 22 2008, 5:11 pm by rockz.

Do you have multiple players under Force 1, and did you try testing it when a player leaves vs. when they aren't there to begin with?

I think you can imitate leavers by executing defeat to computer player.

I've made a test map. Results are surprizeing. CreateUnit and SetDeaths behave differently in this situation.
Just have a look the test map.

Attachments:

OUPS, double post, sorry. Deleted.

Just to say, while form is not required, it is often necessary in any kind of group environment. Form is the difference between this (bad)



and this (good)



The compiler doesn't really care which one you use, but most people consider it a poor job not to use some form.

Good idea with a leaver. It's no difference if a human player or a comp leaves the game.

But in what way were the results surprising?
I got both units created AND the deaths message for me (P1), the regular teal comp playing (P3) and the neutral orange comp (P5).
That's pretty much what I have expected. Players defeated, at open slots and without Start Location neither got created a unit nor had a death added.

Btw. Falk, take this map as the requested test map, it has 2 human slots and kindly tell us if it made any difference. Be sure to leave with one of your computers within 5 seconds (or increase the time of P8).

I've tested this on single player and got messages disagree with created units. I didn't remember quite well now (and can't check it now) but, for example I have not got the message for neutral player...

Interesting. Obviously the rules are different in single player and bnet.