![]() That said, The "offending" code in DBM was changed to work around that issue in dragonflight so I doubt it's still happening (at least not from DBM, probably still tons of other mods). We've been working around blizzard bugs for over a decade we get blamed for so it's nothing new. That taint was likely related to UIDropDown taint that's actually blizzards fault, but it is true that DBM probably triggered it (but so would a dozen other addons that were PROPERLY using the API but blizzards whole taint system is a jumbled mess). Home News Servers Installers Clients Patchs Guides Tools Sandboxs Divers Alpha Project List of clients available for download with WoWDL Clients Name Size Downloads Alpha et Beta World of Warcraft 0. ![]() All other addons were on and zero errors.Īt least now I know it's a core DBM thing that's causing the issue, and can share with everyone (even if it's only here and not on Curseforge, where the addon author disabled comments). WoWDL is a website that allows you to download many files from the World of Warcraft game. Only turning off the DBM Sepulcher addon fixed it. I already unticked the two DBM boxes related to Wild Seeds, but the problem persisted. So I'll assume the error will still occur when I do that fight again. Specifically, when the green friendly Wild Seeds adds appeared. The patch has been on the PTR since the beginning of December. ![]() I turned off the DBM addon, and the problem disappeared.īut the problem first in the Sepulcher Prototype Pantheon fight. The Shadowlands 9.2: Eternitys End update is set to arrive on February 22 (23 for EU realms). Whenever those friendly green-nameplated Fated Zereth Mortis essences appeared, the error would spam and keep spamming. I thought it was a nameplate issue and fiddled around with those addons accordingly, but it never helped. If I zoomed in and they were out of eyesight, the error spam would stop. Posting this for anyone else googling the issue.Įvery time a Green "friendly" add appeared in a boss fight, I would get these errors that would keep spamming my screen until I pointed the camera away. ![]()
0 Comments
Leave a Reply. |