#Placement error, unit still on cooldown

7 messages · Page 1 of 1 (latest)

rotund venture
#

I think my description was deleted automatically ? I'll repost it here once time allows (at work presently)

#

I've been speedrunning my archer to get it to 30.

There's a bug where, if you place in rapid succession (using meat to refresh the units), you'll get an error that the unit is still on cooldown - it then boots you back to the home screen.

It goes as follows:
1 - Place archer with captain 1
2 - Unit is exhausted. Use meat to refresh archer. Place archer with captain 2
3 - With captain 3, the archer shows as available (no refresh needed). When you try to place, you get an error that the unit is still on cooldown
4 - It then kicks you back to the home screen, where you have to load it again

This happens on the newest version of android, in Chrome (added Stream Raiders as a dedicated app on the home screen). I can get you more details about my system a little later but I only have 1 minute left in my break at the moment.

tribal rock
#

Thank you for the report. We will look into this. But it's useful to know that the game takes a little bit to refresh its states. So if you try many actions too quickly it may produce an error.

rotund venture
#

If it's not possible to fix, then can it be changed so that when this error shows, you stay on the placement screen and it prompts for meat (instead of booting back to the home screen)? I should also note that I can wait a few minutes between placements and it still happens.

rotund venture
#

I found that if you go to "Home" after each placement, then the next, the bug doesn't happen.. It only happens if you go directly from one battle to the next.

I also just tested something- I waited 1 minute (used the timer on my phone to count down) after a placement before switching to the next captain. After the second captain, i waited another minute before switching to the third captain- the error still happened (unit placement error)

I suspect this is a software bug that needs to be fixed.. It's not caused by network sync issues

tribal rock
#

Thank you. We're still investigating this.