-
Notifications
You must be signed in to change notification settings - Fork 35
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
Attempts aren't tracked in Mythic keystone dungeons #713
Comments
Current hypothesis:
If this works, it could later be generalized and provided as a new method (similar to NPC, boss, etc.) |
This mount might also later become available via M+: https://www.wowhead.com/item=225548/wicks-lead Edit: And the quest starter for this one https://www.wowhead.com/item=221765/stonevault-mechsuit There could be others, but I'm not in the loop. Should probably implement a prototype so that people can test by season 2? |
The new dungeon items should also be available from M+ runs, at least according to the journal. I'll generalize this issue. |
Based on Tracking the Opening spell with tooltip scanning and differentiating based on map ID might then be the only viable option. |
Another option worth investigating: Popular M+ addons should have code that reliably tracks the end of the dungeon run. |
Source: WowAce
I believe there were some old issues related to Mythic+ and even some partially-working experiments, but it's still relevant:
As a starting point, a reliable and non-intrusive method of detecting M+ completions would have to be added. Later on, this could be generalized and be provided as a separate method of detection, e.g.
ENCOUNTER
(forENCOUNTER_END
events),SCENARIO
(assuming M+ uses this event? TBD), or similar. Unfortunately, I can't test this ingame even if I blindly implemented such code.For now, I see two avenues to make some headway and possibly support M+ properly in the future:
/etrace
event log, for both the completion and chest opening sectionLooking into the first part should be relatively easy, so this is already actionable (I think).
The text was updated successfully, but these errors were encountered: