Originally Posted by MunkDev
This example triggers the same shitstorm when only Bagnon is running. Only happens after opening the interface settings, though. I think my workaround is somewhat more robust anyway, but maybe the developer(s) of Bagnon should look into it.
|
Alright, apparently the version of Bagnon that's on wowinterface is a different version than what's on curse.
The version that's on curse does cause this error, so it's something they've managed to do between the version that's on here and the version that's on curse.