Well, we're talking 10k+ lines of code with interdependent modules that assume a certain chain of events to occur on load. It's the nature of the beast when designing an addon for unsupported peripherals, I'm afraid.
I'll investigate it further tomorrow and try to narrow it down, but generally speaking I name and properly assign everything I use, whether it be textures, widgets or tables of data. It's obviously an issue with the client and not the addon, since this didn't even happen in an earlier build, but I'll try to figure out the culprit so that it can be patched.