AlterEgo

AlterEgo

39k Downloads

Frequent ADDON_ACTION_BLOCKED errors when entering combat since 1.0.7.

arcadepro opened this issue ยท 7 comments

commented

This error keeps popping up a lot when entering combat since the last update. (1.0.7) Had zero issues of this nature prior to this.

Probably related to the dungeon teleports/secure action button requirement?

The main window also becomes unusable in combat most of time. Failing to open or failing to close if open. Works fine in 1.0.6.

1x [ADDON_ACTION_BLOCKED] AddOn 'AlterEgo' tried to call the protected function 'AlterEgoWindowBodySidebar:Show()'.
[string "@!BugGrabber/BugGrabber.lua"]:481: in function <!BugGrabber/BugGrabber.lua:481>
[string "=[C]"]: in function `Show'
[string "@AlterEgo/Interface.lua"]:1318: in function `UpdateUI'
[string "@AlterEgo/Database.lua"]:577: in function <AlterEgo/Database.lua:537>
[string "=[C]"]: ?
[string "@AlterEgo/Libs/AceBucket-3.0-4/AceBucket-3.0.lua"]:69: in function <AlterEgo/Libs/AceBucket-3.0/AceBucket-3.0.lua:67>
[string "@AlterEgo/Libs/AceBucket-3.0-4/AceBucket-3.0.lua"]:83: in function `func'
[string "@AlterEgo/Libs/AceTimer-3.0-17/AceTimer-3.0.lua"]:57: in function <...eAlterEgo/Libs/AceTimer-3.0/AceTimer-3.0.lua:50>

Locals:
_ = Frame {
 RegisterEvent = <function> defined @!BugGrabber/BugGrabber.lua:487
 0 = <userdata>
 UnregisterEvent = <function> defined @!BugGrabber/BugGrabber.lua:487
 SetScript = <function> defined @!BugGrabber/BugGrabber.lua:487
}
event = "ADDON_ACTION_BLOCKED"
events = <table> {
 ADDON_ACTION_BLOCKED = <function> defined @!BugGrabber/BugGrabber.lua:553
 ADDON_ACTION_FORBIDDEN = <function> defined @!BugGrabber/BugGrabber.lua:553
 PLAYER_LOGIN = <function> defined @!BugGrabber/BugGrabber.lua:547
 LUA_WARNING = <function> defined @!BugGrabber/BugGrabber.lua:562
 ADDON_LOADED = <function> defined @!BugGrabber/BugGrabber.lua:507
}
commented

@arcadepro Appreciate you taking the time to post this.

Do you have the window open when entering combat? I'll try and reproduce and find a fix.

commented

If the window is open when entering combat if will not be able to be closed. If the window is not open, very often when I charge into combat, or shortly afterwards, I get a bugsack error. Unable to replicate with 1.0.6 or earlier.

Tested mostly using Warriors at the weekly Superbloom event.

commented

If the window is open when entering combat if will not be able to close at all. If the window is not open, most of the time when I charge into combat I get an instant bugsack error.

Tested mostly on Warriors doing the weekly Superbloom event.

Just checking, what version are you running? I can't reproduce what you're describing in the latest version.

commented

The errors were from 1.0.7. I'll test 1.0.8 tonight/tomorrow.

commented

The errors were from 1.0.7. I'll test 1.0.8 tonight/tomorrow.

Thanks. I published 1.0.8 to fix the issue, so let me know if it's still happening after the update :)

commented

1.0.8 seems to be O.K.

commented

1.0.8 seems to be O.K.

That's great :-)
Thank you.