View Issue Details

IDProjectCategoryView StatusLast Update
0023377Return of ReckoningGeneralpublic2024-10-23 08:38
ReporterR1CH Assigned ToMaxHayman  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0023377: Dungeon lockouts persist after expiration without re-logging
DescriptionSomewhat related to my previous report - https://bugs.returnofreckoning.com/view.php?id=23376

If you see the screenshot there, the main GB lockout is negative and the rest are soon to expire. I relogged shortly after taking that screenshot, and the main GB lockout no longer appeared in the UI, however other lockouts continued counting down and eventually caused the error mentioned in that bug report once they reached zero / negative. Once all of them were negative, I did ]lockouts which seemed to refresh them - all my GB lockouts disappeared as expected.

I then found a GB group and the boss kills on Masta Mixa and 'Ard Ta Feed gave me no credit or loot, it said I was locked out for me and also created a new 18h lockout timer. Glomp did give me credit, however I don't recall if I relogged before or after that lockout timer ran out - presumably after. Also after Masta Mixa did not give me credit, I used the ]lockouts command to verify no one in my group was locked out from 'Ard Ta Feed because I needed that credit, and I don't recall seeing anyone lockouts, myself included. No one else in the group complained about missing credit or loot so I'm pretty sure it only affected me.

I think the lockouts I had on my character persisted after expiring while logged in, and relogging was the only way to get things back into a proper state. Other players are most likely relogging once the Invalid Command spam starts which somewhat mitigates the issue.
TagsNo tags attached.

Activities

MaxHayman

MaxHayman

2024-10-20 23:30

administrator   ~0044859

This should be fixed in the next patch. If not could you please let me know here.
MaxHayman

MaxHayman

2024-10-23 08:38

administrator   ~0044875

Patch 23/10/2024

Issue History

Date Modified Username Field Change
2024-10-06 22:46 R1CH New Issue
2024-10-19 05:07 Emissary Assigned To => MaxHayman
2024-10-19 05:07 Emissary Status new => assigned
2024-10-20 23:30 MaxHayman Status assigned => resolved
2024-10-20 23:30 MaxHayman Resolution open => fixed
2024-10-20 23:30 MaxHayman Note Added: 0044859
2024-10-23 08:38 MaxHayman Note Added: 0044875
2024-10-23 08:38 MaxHayman Status resolved => closed