Unit Group Leak question

[RobertMKD]

Do I need to clear the leak of a unit group I use only for a condition?

 

[SAUS]

You only need to clear it if you create it. If it is created in an if statement, destroy it in the if statement. Destroying a destroyed group may also cause a crash, but I'm not sure.

 

[RobertMKD]

For example: If I check the number of the units in region, do I have to clear the leak for that Unit Group?

 

[SAUS]

I think so. What does the trigger look like? Is there something like (Units in region (myRegion))? That creates a group, so you would need to clear that leak.

 

[RobertMKD]

Yes, it's not a variable, I felt so lazy to create a variable just for a check like that, but it seems I'll have to.

Thanks!

 

[SAUS]

No problem

For most cases, you can use the same group variable. Just call it tempGroup or something. It's not so bad once you start using the variable by default. It makes cleaner code as well.

 

[Arad MNK]

OR use:

• Custom script: set bj_wantDestroyGroup = true

 

[RobertMKD]

I know that function, but what does it actually does?
I can only see that it's a boolean..

 

[Arad MNK]

It destroys the Group right after the creation and It's loop actions.
That's why you don't use it when you have a Variable.(?)

 

[Wietlol]

When you do a ForGroup action or "Pick every units in <unitgroup> and do action(s)" then it will also destroy the group if bj_wantDestroyGroup (a global boolean variable) is set to true.

This works with both variables and direct groups but this custom script cannot be placed in conditions as custom scripts are not allowed there.

This only works with the Blizzard.j ForGroupBJ function and not for ForGroup from Common.j (for people who understood what I just said.)