maxiqbert
Well-Known Member
Game version: v1.104-beta.11-(2f3a787) (2020-05-04 15:26)
HTML5 Yes/No: yes
Game world: beta
Browser/IOS/Android + version: firefox 75.0 (64 bits)
Flash Player version: NA
Operating System or Mobile Device: windows 10
Screen resolution: 1920x1080
Account name: maxiqbert
Humans or Elves: elves
Reproducibility: 5/5 (1/5 = happened once; 2/5 = happens randomly; 3/5 = happens sometimes; 4/5 = happens often, but not always; 5/5 = happens always)
Quest title: (if applicable)
Current situation:
__ when in the spire, if you choose different kind of troops, you don' t enter the fight, you get a message error (see screenshot)
__ after you close the error window, you cannot go back to the fight, you must first leave the spire
Expected situation:
__ the fight should be resolved
__
Reproduction Steps
1. enter the spire
2. select fight
3. select various troops (it doesn't happen always if you select only one kind of troops)
4. click autofight
5. get the message
Add more steps if needed. Include only ONE action for each step!
Screenshots of the bug:
HTML5 Yes/No: yes
Game world: beta
Browser/IOS/Android + version: firefox 75.0 (64 bits)
Flash Player version: NA
Operating System or Mobile Device: windows 10
Screen resolution: 1920x1080
Account name: maxiqbert
Humans or Elves: elves
Reproducibility: 5/5 (1/5 = happened once; 2/5 = happens randomly; 3/5 = happens sometimes; 4/5 = happens often, but not always; 5/5 = happens always)
Quest title: (if applicable)
Current situation:
__ when in the spire, if you choose different kind of troops, you don' t enter the fight, you get a message error (see screenshot)
__ after you close the error window, you cannot go back to the fight, you must first leave the spire
Expected situation:
__ the fight should be resolved
__
Reproduction Steps
1. enter the spire
2. select fight
3. select various troops (it doesn't happen always if you select only one kind of troops)
4. click autofight
5. get the message
Add more steps if needed. Include only ONE action for each step!
Screenshots of the bug: