|
I had that issue with Trinity either on the December 2.0 patch, TBC launch, or some major patch after. It turns out there's nothing wrong with the code, but some variables saved was causing it to incorrectly interact with blizzard's combat lockdowns.
Deleting the wtf folder files for Trinity and working it from scratch fixed it. Tedious and unfortunate, but o well :/
For the record, I just logged in post-patch today, zero errors with trinity, forms and combat lockdown.
|