*There will be a new version coming out soon with some additional features as well as detection for some leaks I missed.

Is either of those the code you are talking about? I haven't used WE in quite a long time.
At the end of the scan I have also made it display a link to some Memory Leak tutorials.
I want to say yes, but right now I'm sure there are some leaks that are not being detected. The only way for me to fix that is for people to report any leaks not being detected that they know of.can this check every possible leak?
There are colors in the new version coming out soon. No worriesWhat? No colors?
With colors, I can see better.
(and prettier)
It should detect Covert Player to Player Group or at least the test I have done has detected it.Anyway, the only Player Group leak it actually detects is Convert Player To Player Group (ignores all others). It would also be nice if it could detect if the mapper tried to destroy (All players) and warn that it's a very bad idea to do that.
Code:
call DestroyForce(GetAllPlayers())
Code:
Player Group - Remove all players from (All players)
I have set the default option for showing suggested fixes to off. I have also made it display a warning when turning it on.I also recommend that you get rid of the suggested fix thing.
A lot of people completely rely on this fix as the ultimate and only solution while they often don't know how to use it ("where is the Set MyLocation action?") or can sometimes be wrong due to a bug/improper use (in conditions for instance).
Instead you can just make it say, for example, "Unit Group Leak, click here for more info" where clicking would result in a window with information on Unit Group leaks and a couple of examples on how to remove them (and possibly a link to emjlr3's tutorial) showing up.
At the end of the scan I have also made it display a link to some Memory Leak tutorials.