View Issue Details

IDProjectCategoryView StatusLast Update
0023811Return of ReckoningDungeonspublic2025-01-15 09:31
Reportercarabon Assigned ToR1CH  
PrioritynormalSeverityminorReproducibilityN/A
Status resolvedResolutionfixed 
Summary0023811: bastion stair
Descriptionjust completed bastion stair, my quests didnt update to each of the 4 big bosses killed,.. others in grp did
TagsNo tags attached.

Relationships

has duplicate 0023863 closedR1CH bosses being locked out despite lockout having expired 

Activities

R1CH

R1CH

2024-12-28 19:08

developer   ~0045853

When did you last run the dungeon? Did you check if anyone was locked out with the ]lockouts command? Were you dead when any of the bosses were killed?
carabon

carabon

2024-12-28 19:11

reporter   ~0045854

not locked out, did dungeon yesterday, my timers were all at nothing. i was not dead. hard to check now as i dont remember who i went in with. i was getting loot from bosses.
R1CH

R1CH

2024-12-28 19:14

developer   ~0045855

During the session when you ran BS, when you logged in did you still have lockouts from yesterday? I.e, did the lockouts expire in the same session as you ran the dungeon?
carabon

carabon

2024-12-28 19:19

reporter   ~0045856

no they ran out before starting or entering the dungeon.
R1CH

R1CH

2024-12-28 19:21

developer   ~0045857

Did they run out while you were logged in, or by the time you logged in had they had already run out?
carabon

carabon

2024-12-28 19:23

reporter   ~0045858

they did run out while i was logged in, but before starting any dungeon
R1CH

R1CH

2024-12-28 19:25

developer   ~0045859

Thanks for confirming. I had the same issue. Unfortunately it looks like there's a bug where if you are logged in when they expire they do not get fully removed.
carabon

carabon

2024-12-28 19:27

reporter   ~0045860

so i wasted a few hours for nothing? because a bug that is known but not known by the people it effects?
Rubius

Rubius

2024-12-28 22:26

developer   ~0045864

Not wasted - this helps us confirm / identify the bug so we can look into getting it fixed in the future!
R1CH

R1CH

2024-12-29 21:07

developer   ~0045870

This should be fixed for the next patch, thank you for the report.

Issue History

Date Modified Username Field Change
2024-12-28 17:30 carabon New Issue
2024-12-28 19:08 R1CH Note Added: 0045853
2024-12-28 19:11 carabon Note Added: 0045854
2024-12-28 19:14 R1CH Note Added: 0045855
2024-12-28 19:19 carabon Note Added: 0045856
2024-12-28 19:21 R1CH Note Added: 0045857
2024-12-28 19:23 carabon Note Added: 0045858
2024-12-28 19:25 R1CH Note Added: 0045859
2024-12-28 19:27 carabon Note Added: 0045860
2024-12-28 22:26 Rubius Note Added: 0045864
2024-12-29 20:30 R1CH Assigned To => R1CH
2024-12-29 20:30 R1CH Status new => assigned
2024-12-29 21:07 R1CH Status assigned => resolved
2024-12-29 21:07 R1CH Resolution open => fixed
2024-12-29 21:07 R1CH Note Added: 0045870
2025-01-15 09:31 R1CH Relationship added has duplicate 0023863