Which is better? Many triggers or one with many conditions

[Dois]

is it better to use a lot of triggers or one trigger with many if,then,elses

e.g.

When unit steps into Region(X) [ive got a lot of regions]
then - attack-move to next region.

OR

one trigger with MANY EVENTS (steps into Region(x or y or z or asd0i02kg)

and then

if Entering Unit's custom value = X then issue orde to triggering unit to attack-move to (another region)
edit: oh yeah and give it a new custom value as well

 

[Tinki3]

Whichever way you choose, it will make no noticeable difference.

I would personally use 1 trigger so that everything is "together".

 

[Dois]

alright thanks

 

[Sanandreasm4]

Maybe you could mke a varible!

Like:
region(1)=street
region(2)=house1
region(3)=house2
etc.
Just put all you regions in it! try to let some regions together:
Like:
reion(1-10)= all about in the mansion
region(10-20)= all about on the street
Just a bit orginazation is that.

Now the trigger(sorry dont have wc3 editor on this comp so i will type it myself):

Event:
A unit enters region - (All regions, are entered as event)
condition - nothing(i dont really use the this condition )
Action -
Loop for integer A 1 to - (-= how many varbiables you got)
if/then/else
If
region(LoopA) contains triggering unit
Then
do actions you want
else
Nothing?

 

[Dois]

oh i know what to do... im doing something else... just wanted to know which way would be better... of course if it eats up less system performance or whatever you measure that in, ill prefer to use that certain way.

but theres gonna be no noticeable difference so ill rather do it in one trigger

 

[AceHart]

> I would personally use 1 trigger so that everything is "together".

I'd use several, as it cuts down on lines per trigger. Easier to read than an endless "if"...

In the end, the conditions need to be checked anyway.
Presumably, "if" might be faster, in the sense that the trigger could stop on the first condition that fits.
Then again... go with whatever makes the most sense to you.

Look at your trigger.
Imagine you'll have to edit something in there three weeks from now.
Do you think you'd still get what it is doing?
If yes: good, keep it up.
If not: ... you need a better trigger.

 

[Dois]

ok