[Trigger] Better to have one event with lots of actions, or lots of events with a few actions?

[TheBronze]

Currently I use lots of triggers like this for my item system (47 to be exact):

Runed Gautlets
    Events
        Unit - A unit Acquires an item
    Conditions
        ((Triggering unit) has an item of type Gauntlets of Ogre Strength) Equal to True
        ((Triggering unit) has an item of type Circlet of Nobility) Equal to True
        ((Triggering unit) has an item of type Rare Scroll) Equal to True
    Actions
        Item - Remove (Item carried by (Triggering unit) of type Gauntlets of Ogre Strength)
        Item - Remove (Item carried by (Triggering unit) of type Circlet of Nobility)
        Item - Remove (Item carried by (Triggering unit) of type Rare Scroll)
        Hero - Create |cffffcc00Runed Gauntlets|r|n and give it to (Triggering unit)

Now that I have lots of items, should I combine all of those triggers under a single event or just leave them as seperate triggers?

Basically this boils down to: Does the WC3 engine process events or conditions faster?

 

[azlier]

It's good to combine all possible things under a single event. However, GUI conditions are slower than ones hand made in Jass. I am unsure which is quicker.

For simplicity's sake, use separate triggers. Or learn Jass. Pick one.

 

[baassee]

It works but not the best unfortunatly

 

[TheBronze]

Well I've got them in seperate triggers now, but it seems like people don't know the answer which is faster...

Maybe I'll try combining them next release.

 

[Yixx]

I dont think it has any significant difference.

 

[En_Fuego]

Combine. It calls more functions when you separate them. If you have one it just has to run through the same amount, just not at the same time.
The change in speed is minuscule though. It really shouldn't matter.

 

[Saia_Djinn]

if not extraordinaray much actions are used one is faster and more performant because for a second one a second trigger,event ,condition(maybe also an action) are needed which are all handles and so --->leak(or eat some memory because if the trigger is permanent the stay=D=D)
if done to often it will matter but if you have a single trigger copied once it should not make a change