Skip to content
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

Bug: iLVL display wrong number on toast #67

Open
Ghaan opened this issue Aug 21, 2024 · 5 comments
Open

Bug: iLVL display wrong number on toast #67

Ghaan opened this issue Aug 21, 2024 · 5 comments

Comments

@Ghaan
Copy link

Ghaan commented Aug 21, 2024

bild

As you can see here it is displaying the wrong ilvl on the toast itself vs what ilvl the item actually has.

@Taizunz
Copy link

Taizunz commented Sep 1, 2024

Just here to confirm this.
image

@ls-
Copy link
Owner

ls- commented Sep 2, 2024

It's a known bug. Blizz have 3 APIs that can return an item level, I use the second best one, but I can't use the most precise one. Potentially, I could scan tooltips, but it can be rather laggy and that's not something I'm fond of, some people with weaker machines already complain about stutters when a bunch of toasts spawn, but I may change my mind later.

@ls-
Copy link
Owner

ls- commented Sep 12, 2024

I reported this issue to Blizz yet again, but this time around via a trusty comrade who has contacts inside Blizz, so maybe they'll finally fix this bs 😅 For now we can only hope because it's been broken for years at this point 🙏🏼

@Ghaan
Copy link
Author

Ghaan commented Sep 12, 2024

If that lead doesn't pan out, I know the addon Baganator had a similar issue that ended up being resolved. Can't say in which way, but may be worth looking into if the report to Blizz doesn't work out.

Baganator/Baganator#169

@ls-
Copy link
Owner

ls- commented Sep 12, 2024

Yeah, I'm aware of that API, that's what I meant when I said that I was using the second best option. The best option is what baganator uses, at least when it can, but it's not something that can be used for toasts.

The only accurate alternative to that is parsing tooltips which I'd like to avoid because it comes with its own host of issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants