-
Notifications
You must be signed in to change notification settings - Fork 74
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
Opening HoA/SoA does not work in v1.1.9 #83
Comments
If you're using wowup, can you quickly update and let me know if it works? I suspect you had a route in actual MDT previously with a partially broken table. In 1.1.8 and 1.1.9, code was added to automatically sync and import routes; looks like this may have caused the issue. I added two type checks on the entry itself, and Let me know if it works. I'll be back in 3-4 hours after a quick nap. |
I was having the same issue and after reading this post I went into my WTF folder and found the saved variables .lua for Mythic Dungeon Tools (no longer installed) and removed those files. Dungeon Tools works fine now. |
I didn't carry anything over from my old MDT SavedVariables, but in DungeonTools v1.1.8, I imported routes which I believe were created in MDT v3.3.4. You can find them here for reference: https://pastebin.com/bjF89xvk I updated my DungeonTools to v.1.1.10, and this issue is still occurring. Regarding Drangleic's suggestion, I already deleted my original MDT SavedVariables while switching over to DungeonTools a few days ago, so that fix would not apply to my particular issue.
|
You should see v1.1.11 showing up soon; the change in it is aimed at fixing this. Whenever you open dungeon tools, it will check and remove any presets that are not deemed valid routes. This should not cause issues as, in your case, an invalid route is a route without a Let me know if this fixes it; if it does I'll push it to curseforge as well. |
v1.1.11 is working a bit better for me in that it doesn't completely black out like v10 did, All of my routes were test routes created in this addon probably in v.6 or .7 (not imported from anywhere),
|
How on earth is The only thing I can think of as to how you ended up in that state is that the What a silly decision to have the |
Where my routes have been emptied out i have multiple |
Got the same behavior, after updating to 1.1.9 I am just getting black screen and lua error. |
I pushed 1.1.11 onto curseforge for now; now that I know where it is coming from (roughly) thanks to @erigul 's comment, I should be able to replicate locally and fix. |
with 1.1.11 now if I choose Theater of Pain
and
|
I got my DT.lua file out of syncthing from a yesterday, which should have my routes that then broke when I upgraded, if that helps with recreating. |
I'm reworking the route storage entirely. This is such a rabbit hole of a problem where a bunch of things are calling on the defaults when they should not be:
All of this stems from hacks to get the menu at the top to function without having to copy part of its state, which I am undoing right now. I will remove both the default route and the new preset element from there, move them as proper virtual objects, and mediate every other call so I can check things when another part of the addon requests a route. This will take me a short while, though. In the meantime, @erigul I've imported your data object and will use it to see if I can fix all the cases in it. |
As a temporary workaround it seems like /reload and selecting existing route on the first displayed map would allow to open those who couldn't be opened. |
I have routes created in a previous version which I believe are set to week 4 affixes (Tyrannical/Inspiring/Necrotic/Prideful), in case that helps with tracking this down. I'm in the middle of a dungeon session right now so I don't have time to track this down, but I'll take a look afterwards.
The text was updated successfully, but these errors were encountered: