DeletedUser1777
Guest
Game version: v1.22.8-(6f8ed0c) (2017-02-02 9:48)
Game world: beta
Browser + version: chrome Version 55.0.2883.87
Flash Player version: 24.0.0.194
Operating System: win7
Screen resolution: irrelevant
Account name: Flabbes
Humans or Elves: Human
Reproducibility: ?/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: none
Current situation:
select last boost relic from NH chest for next level, no notification for bonus increase, wierd information at bonus overview (calculation in manufactory is updated + correct right away - 653% for 430 relics)
a reload fixes the issue
the missing notification for boost gain is not new (was already fixed, don't find the thread atm), but the "locked" is new
Expected situation:
get notification + see the right % of boost bonus
Reproduction Steps
1. select last boost relic from NH chest for next level
2. notice there is no notification
3. check relics / boost at worldmap
Screenshots of the bug:
after reload it's correct
Game world: beta
Browser + version: chrome Version 55.0.2883.87
Flash Player version: 24.0.0.194
Operating System: win7
Screen resolution: irrelevant
Account name: Flabbes
Humans or Elves: Human
Reproducibility: ?/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: none
Current situation:
select last boost relic from NH chest for next level, no notification for bonus increase, wierd information at bonus overview (calculation in manufactory is updated + correct right away - 653% for 430 relics)
a reload fixes the issue
the missing notification for boost gain is not new (was already fixed, don't find the thread atm), but the "locked" is new
Expected situation:
get notification + see the right % of boost bonus
Reproduction Steps
1. select last boost relic from NH chest for next level
2. notice there is no notification
3. check relics / boost at worldmap
Screenshots of the bug:
after reload it's correct