Goblin King and Tower room display bugs

Bug Reports
5

Just noticed that the Tower of Doom room name bug is definitely still present in version 4.3.5 (much less 4.3).

Here are the steps I took:

  1. Entered Tower of Doom mode, clicked on the Fight tab.
  2. Clicked on a couple of room randomly (I think).
  3. Checked Guild Chat to see which rooms were useful.
  4. Clicked on each room in turn (2,3,4,5,6) to see and record which room it was. Results were: Hidden Nests, The Bone Pile, Fell Nest, Ice Cave.
  5. Entered room 3 and constructed a team, then immediately fought the battle, receiving a Valraven and a Scroll of Haste.
  6. Clicked on room 5, then Fight. Instead of displaying “Ice Cave”, it says “The Bone Pile”.
  7. Click “To Battle!” It continues to say “The Bone Pile” during the loading screen.
  8. On winning the fight, the Victory screen also erroneously says “The Bone Pile.”
  9. Clicked on the Boss room, then Fight. It correctly says “Doom of Darkness”. Also correct on the Victory screen.
  10. View and record the contents of each room again (Alt-Tabbing to and from Excel).
  11. Fight the Bat Cave in II for a Power Scroll.
  12. The Icy Coven is correctly labelled in room IV.
  13. Change one troop in my team and return to the ToD map.
  14. Back into room IV, edit team (back to what it was) and fight. Forgot to check the name.
  15. At the end of the battle, the Victory screen erroneously displays Bat Cave (along with two more Valraven Sigils and an Unlock Scroll). Screenshot shows the error, though it’s not clear in isolation.
    image
    image960×540 236 KB
  16. Repeat steps 13 and 14 for the Doom of Stone.
  17. Battle is correctly labelled “Doom of Stone” when showing the teams.
  18. However, as soon as I click “To Battle!”, the following screen is clearly incorrect:
    image
    image960×540 256 KB
  19. The incorrect label also displays at the Victory screen (as before).

There you go, totally reproducible, no Valravens required – just a team change.

Given how many bugs you have had (and still have) throughout the team editing interface, I’m hardly surprised that’s what triggers this bug. :frowning: