You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the Kill Statistic ID is on the old Rivendare from before Cataclysm Classic where the dungeon was remade into two sub dungeons instead of the new version.
Received word from Blizzard support and it seems they're aware of the issue and need to fix the bug but it's not highly prioritised.
I might need to look into making another fix for it.
The text was updated successfully, but these errors were encountered:
aSnejbjerg
changed the title
Rivendares Charger attempts not increasing
Rivendares Charger attempts registering
Feb 28, 2025
aSnejbjerg
changed the title
Rivendares Charger attempts registering
Rivendares Charger attempts not being registered
Feb 28, 2025
A possible solution (that doesn't destroy anyone's past attempts, and works if Blizzard fixes the bug), might involve tracking attempts from multiple sources independently. Rarity may be able to add them all up and we can remove the second source once the bug is fixed. Unfortunately that might still be easier said than done. Some settings could be affected (doNotUpdateToLatestStat).
Computing luckiness percentages would be more complicated. Plus, storing more data adds bloat to the saved variables. Also, no idea how to represent this in the UI. But it's an idea, maybe worth prototyping to see if there are any other pitfalls.
That would more or less be a universal feature that could, if done right, be solving several other issue. See #290 and #160.
It looks like the Kill Statistic ID is on the old Rivendare from before Cataclysm Classic where the dungeon was remade into two sub dungeons instead of the new version.
Received word from Blizzard support and it seems they're aware of the issue and need to fix the bug but it's not highly prioritised.
I might need to look into making another fix for it.
The text was updated successfully, but these errors were encountered: