[JASS] filterfunc,conditionfunc,boolexpr ...

[Bribe]

Is there a difference between the three destroyable boolean functions filterfunc,conditionfunc and boolexpr? I imagine the non-destroyable triggeraction causes a handle leak, so my aim is to replace every action with a condition. Can I just use a filterfunc for TriggerAddCondition?

 

[Element of Water]

Yes, all three are the same, but...

native TriggerAddCondition takes trigger whichTrigger, boolexpr condition returns triggercondition

You can't destroy the triggercondition

If you're adding actions to triggers dynamically, you're doing something wrong. Tell us what you're trying to do.

 

[PurgeandFire]

native TriggerRemoveAction  takes trigger whichTrigger, triggeraction whichAction returns nothing

Might help, but I forget whether or not it fixes the leak.

But yeah, the 3 are all the same, the two funcs extend boolexpr. Because of that they can be used interchangeably (either Filter() or Condition(), your choice)

 

[Bribe]

I require a lot of trigger actions and a lot of triggers because (100+) because I need to maintain the exact functionality of the WarChasers map while removing all of its thousands of leaks and there are a lot of specific item drops from specific units.

 

[Element of Water]

Erm, you can do that without triggers, and anyway just do a "any unit drops an item" with a condition.

 

[Bribe]

How do I do that?

Do I have to give every of those units the unit inventory ability and add the desired item to them? Some of them are buildings

 

[Element of Water]

If you select the unit and press enter, there's a dropped items tab...

 

[Bribe]

And if you do that, you generate a trigger and a very complex action each time. That's what I'm trying to avoid.

 

[Pharaoh_]

You can also create a table, that shares the same unit/item id's with the map's Item Table.