-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New feature: Attack buttons blocked on Rogue only army #866
Comments
hey, client have no information about selected army, only AFTER you click attack foe helper have info about attack army but it is too late! We can block attack button automatically for SECOND WAVE. For example you may need to close manually window and continue second battler (you can recover unit using premium goods...). |
Ok. So what you are saying is that on Second Wave you know if there is only rogues alive and cover the 2 attack buttons? |
Yes, possible for second wave only |
That is good enough for me. That is probably where we mess up 99% of the time. |
If it is a 2 wave battle you need to put 2 real units in your army especially when using auto battle. |
Sometimes both of them die on the first wave. We can thank that lovely "Keen Eye" for that. It doesnt happen always, but when it does.... click... rogue slaughter :( |
@osv Thank you from both of us and anyone else that has killed defenseless rogues! |
This would add or remove a window to cover the "Auto Battle", "Attack" and "Start Next Battle" buttons in the case you only have Rogues in either the starting army and if a second wave, only Rogues left.
Far too many times I and the wife get into a rhythm and dont notice the non Rogue have died and sent the remaining, Rogue only, army onto their eminent deaths.
The text was updated successfully, but these errors were encountered: