No Sign-Up Required!
Play Now!
retreating doesn't fully work
I've had this happen many times now.
I move in units from A and B to attack C. After several turns I choose to retreat. It shows all units can go to A - so I move them there. When I submit my turn there are no units in C. Come next turn I see several units didn't retreat and I'm given the option to retreat them to B. Very annoying!
>maybe the unit on top can retraet but under him not he go to A???... Dont move many units at one time try one by one because some units are from A not goint to B...
This is exactly what's happening. Some of the units in the stack can retreat to A, some to B. Unfortunately, the only way to be sure that they all make it out of there is to split the stack and move them one by one.
Precisely. I've gotten into the habit now, when attacking from multiple territories, to not stack them together but to keep the stacks from each territory seperate, so should I need to retreat later it's easy enough to do so. When in doubt though, one by one is the fail safe way to get it done.
A) http://www.battleforces.com/node/360 All it takes is 30 seconds of searching the forums for similiar problems as your own.
B) I wish I could understand Alexander's language. Is that Russengonese?
C) When you send multiple units from multiple territories into a territory to attack, the game remembers where EACH INDIVIDUAL unit comes from. However, when stacked, it will allow you to retreat the entire stack to the territory where the majority of the stack came from. HOWEVER, it doesn't actually retreat them, even though it shows you retreating them, it will only retreat those who came from there.
Try and remember where each unit came from. When in doubt, grab each unit and move them around the near territories and it will tell you where that unit can retreat to (the arrows show you also).
I understand the workaround but it is still a bug that it allows you to command them to go somewhere and then doesn't execute the command as Jester elaborate in (C).
Hence the bug report.
Again, hence A), its been reported, hasn't been fixed, just like the other 100 bugs reported.
.