All Categories

Movement icons problem (reinforcements turn into occupations when you attack a repo!)

Movement icons problem (reinforcements turn into occupations when you attack a repo!)

Search
How to join our moderation team?
Oct 3, 2017, 00:5710/03/17
07/31/15
1683

Movement icons problem (reinforcements turn into occupations when you attack a repo!)

Movement icons problem


green shield ---> reinforcement (in and out).

orange flag ----> occupation / attack repos / attack depots / attack MCs / attack HQs.

orange gun ----> you're raiding.

red gun ---------> raid is coming in your base.

red flag ---------> occupation is coming in your base.


Well... now:

Since the last update (which caused also the "unlimited mercenary bug"), another bug has occurred, which no one has reported.

The problem is as follows:

If you send an attack to a repository while you have reinforcements that are traveling in other directions (green shields) ... these "green shields" disappear from the tag-list of the actions in progress, placed on the bottom of the game screen!


Immediately after you sent the attack on a repo, their "status" changes from "green shields" to "orange flags" !!!

Then, they return again "green shields" when the attack to repository (which caused this change on the icons!) come to end.


NOTES:

  •  in the tracking section of command HQ, the reinforcements tags still remains green.
  •  if reinforcements arrive at their destination before the attack to repo, their action will remains to reinforce the target base (not to occupy it!)
  •  after sending the attack to repo (which turned all "green shields" into "orange flags"), if you send a new reinforcement, the "spell is broken" (the bug is broken) and all the green shields that was turned in orange flags, they turn back to be green shields.
  •  if you stop / cancel the attack to repo just sent, the tags return to be "green shields".




Fix this bug ASAP !!
Thanks.

Views
3k
Comments
1
Comments
Oct 3, 2017, 07:4510/03/17
02/29/16
2645

Hello, Sir!

Well, many thanks for such informative bug report. We'll carefully check this bug and fix it ASAP.