LUA Error latest version


#1

Date: 2018-07-18 21:17:48
ID: 1
Error occured in: Global
Count: 1
Message: …AddOns\AskMrRobot\Libs\AceEvent-3.0\AceEvent-3.0.lua line 33:
Attempt to register unknown event “FORGE_MASTER_OPENED”
Debug:
[C]: RegisterEvent()
…AddOns\AskMrRobot\Libs\AceEvent-3.0\AceEvent-3.0.lua:33: OnUsed()
…bot\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:168: RegisterEvent()
WoWDBProfiler\Main.lua:983:
WoWDBProfiler\Main.lua:976
(tail call): ?
[C]: ?
[string “safecall Dispatcher[1]”]:9:
[string “safecall Dispatcher[1]”]:5
(tail call): ?
…AddOns\AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0.lua:558: EnableAddon()
…AddOns\AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0.lua:651:
…AddOns\AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0.lua:636
[C]: LoadAddOn()
…\FrameXML\UIParent.lua:445: UIParentLoadAddOn()
…\FrameXML\UIParent.lua:564: TimeManager_LoadUI()
…\FrameXML\UIParent.lua:1187:
…\FrameXML\UIParent.lua:1085
Locals:
None
AddOns:
Swatter, v7.7.6000 (SwimmingSeadragon)
AskMrRobot, v61
AucAdvanced, v7.7.6000 (SwimmingSeadragon)
AucFilterBasic, v7.7.6000 (SwimmingSeadragon)
AucStatHistogram, v7.7.6000 (SwimmingSeadragon)
AucStatiLevel, v7.7.6000 (SwimmingSeadragon)
AucStatPurchased, v7.7.6000 (SwimmingSeadragon)
AucStatSimple, v7.7.6000 (SwimmingSeadragon)
AucStatStdDev, v7.7.6000 (SwimmingSeadragon)
AucUtilFixAH, v7.7.6000 (SwimmingSeadragon)
DBMCore, v8.0.0
DBMDefaultSkin, v
DBMStatusBarTimers, v
Details, v
DetailsDmgRank, v
DetailsDpsTuning, v
DetailsEncounterDetails, v
DetailsRaidCheck, v
DetailsStreamer, v
DetailsTimeAttack, v
DetailsTinyThreat, v
DetailsVanguard, v
LibSharedMedia30, v3.0-91
SlideBar, v7.7.6000 (SwimmingSeadragon)
Stubby, v7.7.6000 (SwimmingSeadragon)
WeakAuras, v2.6.0
WoWDBProfiler, v
BlizRuntimeLib_enUS v8.0.1.80000
(ck=376)


#2

This is not an error with our addon – it is an error with another addon that is using the same shared library. Our addon never used the event “FORGE_MASTER_OPENED” anywhere.

Sometimes when addons use the same shared libraries, the first addon to load will show up in the stack trace.


#3

Not 100% sure, but WoWDBProfiler might be the addon that is the real source of the error here.