Okay, so... I think I get it.
Let's say you have a Paladin and 5 Footmen attacking a tower - you want the attacking party to retreat when there's only the Paladin and 2 or less Footmen remaining, is that it? If so, there is one important question to ask here: does the Paladin have to be alive for the retreat to happen? For instance, if the tower focuses and kills the hero first, should the Footmen still retreat when there's 2 or less of them left?
---
Anyway, there are a couple of problems here. For starters, the condition you posted is a mess... I'm sorry, but I really cannot understand the logic behind it. If I understood you incorrectly, please explain to me step by step what you want to happen, because I honestly don't have any other ideas.
Furthermore, one of your conditions states that
the attacked unit cannot be a hero. This means that if the tower attacks the hero the whole time, the trigger will never fire, no matter how many Footmen there are in range. This can lead to a situation where your tower kills Footmen until there are only 2 left, but then starts attacking the hero, resulting in the attacking party not retreating despite meeting the intended retreat conditions, because the "attacked unit isn't a hero" condition not being met.
Moreover, the Hero also counts as a unit, so if you had a unit group with 1 hero and 2 regular units, counting them would return 3, not 2.
And some more general tips:
1. If you have a conditon block containing <condition1>, <condition2>, <condition3> etc. and you want it to pass when all conditions are true, you don't need to use an "And" block, because the condition block by itself is set to only pass if all conditions are true. The "And" block is useful in "condition trees", for instance - if you wanted to do something like this: "if <condition1> or (<condition2> and <condition3>)", i.e. either condition1 is true or both condition2 and condition3 are true.
2. You're not clearing leaks, which in this case is actually pretty huge - each time your version of the trigger fired it leaked 2 points and 2 unit groups just by checking the conditions with the potential for more if the conditions were met. And since that trigger will fire every time any unit is attacked ever, you're going to be generating hundreds if not thousands of leaks and it can eventually add up and cause issues.
3. It's preferrable to use (Triggering Unit), i.e. a unit that did or had something done to it that caused the trigger to fire, where possible and in the case of a trigger with an event "A unit is attacked", the unit that is being attacked is the (Triggering Unit), hence there's no point using (Attacked Unit).
---
If I understood you correctly, your trigger should look like this - assuming that the hero has to be alive:
-
Events
-
Unit - A unit Is attacked
-
Conditions
-
(Attacking unit) Equal to <Your Tower>
-
Actions
-
Set TempBoolean = False
-
Set TempPoint = (Position of <Your Tower>)
-
Set TempGroup = (Units within 800.00 of TempPoint matching ((((Matching unit) is alive) Equal to True) and (((Matching unit) belongs to an enemy of (Owner of (Attacking unit))) Equal to True)))
-
Custom script: call RemoveLocation(udg_TempPoint)
-
Unit Group - Pick every unit in TempGroup and do (Actions)
-
Loop - Actions
-
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
-
If - Conditions
-
((Picked unit) is A Hero) Equal to True
-
Then - Actions
-
Else - Actions
-
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
-
If - Conditions
-
(Number of units in TempGroup) Less than or equal to 3
-
TempBoolean Equal to True
-
Then - Actions
-
Set TempPoint = (Center of <Retreat Region>)
-
Unit Group - Pick every unit in TempGroup and do (Actions)
-
Loop - Actions
-
Unit - Order (Picked unit) to Move To TempPoint
-
Custom script: call RemoveLocation(udg_TempPoint)
-
Else - Actions
-
Custom script: call DestroyGroup(udg_TempGroup)
If you want any other scenario such as this trigger also working for 2+ heroes or the hero not having to be alive for the retreat to happen, let me know. That said, if I understood you correctly then this does exactly what you want, i.e. orders the attacking party to retreat if a) the hero is still alive and b) 2 or less regular units are alive.
--- EDIT:
So I think I actually misundestood - you don't want the whole attacking party to retreat, but just the hero, right? In that case the trigger would look like this:
-
Events
-
Unit - A unit Is attacked
-
Conditions
-
(Attacking unit) Equal to <Your Tower>
-
Actions
-
Set TempPoint = (Position of <Your Tower>)
-
Set TempGroup = (Units within 800.00 of TempPoint matching ((((Matching unit) is alive) Equal to True) and (((Matching unit) belongs to an enemy of (Owner of (Attacking unit))) Equal to True)))
-
Custom script: call RemoveLocation(udg_TempPoint)
-
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
-
If - Conditions
-
(Number of units in TempGroup) Less than or equal to 3
-
Then - Actions
-
Set TempPoint = (Center of <Retreat Region>)
-
Unit Group - Pick every unit in TempGroup and do (Actions)
-
Loop - Actions
-
If (All Conditions are True) then do (Then Actions) else do (Else Actions)
-
If - Conditions
-
((Picked unit) is A Hero) Equal to True
-
Then - Actions
-
Unit - Order (Picked unit) to Move To TempPoint
-
Else - Actions
-
Custom script: call RemoveLocation(udg_TempPoint)
-
Else - Actions
-
Custom script: call DestroyGroup(udg_TempGroup)
Disclaimer: this will only tell the attacking hero to retreat - you used many hero variables, but also said that you want the "AI hero to fall back" (implying a single hero), so it made more sense for me to go for something like this. If that was a mistake and you need help modifying the trigger, let me know.
