When logging back in after a crash, currently active Bard songs will flicker in the buff window as if fading or ending soon, despite being permanently active.
Steps to reproduce:
Create a dirge and acquire level 2
Cast Harl's Rousing Tune
Crash the game
Log back in and look at your buff window to notice the flickering
Recast Harl's Rousing Tune to fix the issue.
Expected Behavior: Buffs properly persist through relogging/crashing visually.
From eq2emulator forums: https://eq2emulator.net/phpBB3/viewtopic.php?f=13&p=35692#p35692
When logging back in after a crash, currently active Bard songs will flicker in the buff window as if fading or ending soon, despite being permanently active.
Steps to reproduce:
1. Create a dirge and acquire level 2
2. Cast Harl's Rousing Tune
3. Crash the game
4. Log back in and look at your buff window to notice the flickering
5. Recast Harl's Rousing Tune to fix the issue.
Expected Behavior: Buffs properly persist through relogging/crashing visually.
this was likely fixed by some other change, there were some fixes around linkdead just this past week which resolve reconnect issues, the player has a bunch of packets it uses to diff the new 'content' to send to the client, those need to be reset since the new client coming in doesn't have that prior data.
this was likely fixed by some other change, there were some fixes around linkdead just this past week which resolve reconnect issues, the player has a bunch of packets it uses to diff the new 'content' to send to the client, those need to be reset since the new client coming in doesn't have that prior data.
git issue was resolved here https://git.eq2emu.com/devn00b/EQ2EMu/issues/364
From eq2emulator forums: https://eq2emulator.net/phpBB3/viewtopic.php?f=13&p=35692#p35692
When logging back in after a crash, currently active Bard songs will flicker in the buff window as if fading or ending soon, despite being permanently active.
Steps to reproduce:
Expected Behavior: Buffs properly persist through relogging/crashing visually.
this was likely fixed by some other change, there were some fixes around linkdead just this past week which resolve reconnect issues, the player has a bunch of packets it uses to diff the new 'content' to send to the client, those need to be reset since the new client coming in doesn't have that prior data.
git issue was resolved here #364