firerock
Enchanter
Game version: __0.22.258-92eb3d1-(master) (2015-08-11 9:20)
Game world: __Arendyll
Browser + version: __IE11 11.0.9600.17914 (update version 11.0.21)
Flash Player version: __18.0.0.209
Operating System: __Windows 7
Screen resolution: __1920x1080
Account name: __firerock
Humans or Elves: __Elves
Hardware Acceleration: ON
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) N/A
Current situation:
When I go to the fellowship list and select a player to visit, I polish something, then click his fellowship list, click on their name again, and it tells me "You cannot visit an inactive player.".
Expected situation:
__The player is active, so should either re-display their town or have no mouse over text, or say something like "Already at players town"
__
Reproduction Steps:
1. __ click on fellowship list
2. __visit any player
3. __click on their fellowship list
4. __click on that player again to get message
5. __
Screenshots of the bug:
Game world: __Arendyll
Browser + version: __IE11 11.0.9600.17914 (update version 11.0.21)
Flash Player version: __18.0.0.209
Operating System: __Windows 7
Screen resolution: __1920x1080
Account name: __firerock
Humans or Elves: __Elves
Hardware Acceleration: ON
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) N/A
Current situation:
When I go to the fellowship list and select a player to visit, I polish something, then click his fellowship list, click on their name again, and it tells me "You cannot visit an inactive player.".
Expected situation:
__The player is active, so should either re-display their town or have no mouse over text, or say something like "Already at players town"
__
Reproduction Steps:
1. __ click on fellowship list
2. __visit any player
3. __click on their fellowship list
4. __click on that player again to get message
5. __
Screenshots of the bug: