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

Machine Defense Unit 1-11 uses wrong object ID for container #779

Open
rdw-software opened this issue Sep 27, 2024 · 1 comment
Open

Machine Defense Unit 1-11 uses wrong object ID for container #779

rdw-software opened this issue Sep 27, 2024 · 1 comment

Comments

@rdw-software
Copy link
Member

Source: WowAce

With the latest version of the addon, opening the Awakened Caches upon completion of the machine awakening scenario is giving too much credit for attempts toward the mount. According to Wowhead, only a single object (https://www.wowhead.com/object=464938/awakened-cache) can drop the mount - this is the one for doing all 20 waves.

Instead, multiple opens of the different caches are counting toward mount progress. For an accurate count, this means manually going in and adjusting down the number of attempts.


Rarity doesn't actually use object IDs to detect game objects, but rather tooltip scanning (based on the object's localized name). Unfortunately, that means there's no way to differentiate between the caches by their ID. There was no wowhead data suggesting they'd need to be treated differently and the implementation is based on user reports, because I have no way to test the detection ingame (nor access to TWW content in general).

If there's a way to retrieve the object ID when opening containers, the detection can be improved. However, I'm not aware of one.

@rdw-software
Copy link
Member Author

One vague idea I did have:

Since wowhead seems to be tracking what players received from opening the containers, and they use an addon (called "wowhead looter") for this, there should in theory be a way to figure out what they're doing and reproduce the relevant parts in Rarity.

This might warrant an investigation, although I don't think I'll have time to tackle this anytime soon. Maybe someone else will ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: The time is nigh (Planning)
Development

No branches or pull requests

1 participant