Skip to content

Rivendares Charger attempts not being registered #828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aSnejbjerg opened this issue Feb 28, 2025 · 1 comment
Open

Rivendares Charger attempts not being registered #828

aSnejbjerg opened this issue Feb 28, 2025 · 1 comment

Comments

@aSnejbjerg
Copy link
Collaborator

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.

@aSnejbjerg aSnejbjerg changed the title Rivendares Charger attempts not increasing Rivendares Charger attempts registering Feb 28, 2025
@aSnejbjerg aSnejbjerg changed the title Rivendares Charger attempts registering Rivendares Charger attempts not being registered Feb 28, 2025
@rdw-software
Copy link
Member

Adding this to #670 :)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Soon™
Development

No branches or pull requests

2 participants