DeletedUser2768
Guest
Game version: __ v1.32.3-(b3c05843b) (2017-06-27 10:41)
Game world: __Elcysandir
Browser + version: __Chrome
Flash Player version: __26.0.0.131
Operating System: __WIndows 10
Screen resolution: __1366x768
Account name: __RosehawkATA
Humans or Elves: __Elf
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: _N/A_ (if applicable)
Current situation:
See an applicant in the Aspirants tab, but told that there is a wait time before so-and-so can join. They then disappear from the list, only to reappear once the fellowship window has been closed and reopened.
Expected situation:
Applicants that are already in a fellowship are either automatically removed from the queue, or I get a notification that they're already in another fellowship.
Reproduction Steps
1. __Click on fellowship icon
2. __click on Aspirants tab
3. __Accept application
4. __cool down notification
5. __applicant disappears from queue
6. Close window
7. repeat step 1
Screenshots of the bug:
Game world: __Elcysandir
Browser + version: __Chrome
Flash Player version: __26.0.0.131
Operating System: __WIndows 10
Screen resolution: __1366x768
Account name: __RosehawkATA
Humans or Elves: __Elf
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: _N/A_ (if applicable)
Current situation:
See an applicant in the Aspirants tab, but told that there is a wait time before so-and-so can join. They then disappear from the list, only to reappear once the fellowship window has been closed and reopened.
Expected situation:
Applicants that are already in a fellowship are either automatically removed from the queue, or I get a notification that they're already in another fellowship.
Reproduction Steps
1. __Click on fellowship icon
2. __click on Aspirants tab
3. __Accept application
4. __cool down notification
5. __applicant disappears from queue
6. Close window
7. repeat step 1
Screenshots of the bug: