
Bagnon running with Outfitter Retrofit addon error
Shalaros opened this issue ยท 1 comments
Which software were you running?
- Addon version name:
- Bagnon 11.1.1
- Same error exists on versions 11.0.24 - 11.1.1
- Classic Wow Anniversary 1.15.6
Have you read the changelog?
Mark if read.
Please describe the bug.
I'm just getting error while running Bagnon and Outfitter. I'm reporting it to you and Outfitter. Not sure who is at fault. These were the only 2 addons enabled.
Please describe how to reproduce it.
If applicable, please add screenshots to help explain your problem.
Just load your addon and outfitter retrofit 4.4.2.1 to reproduce the error code. I used bugsac to capture the error.
Error Logs are Important!
1x bad argument #2 to '?' (Usage: local success = C_CVar.SetCVarBitfield(name, index, value [, scriptCVar]))
[string "=[C]"]: in function SetCVarBitfield' [string "@BagBrother/core/core.lua"]:47: in function
?'
[string "@BagBrother/libs/WildAddon-1.0-2/WildAddon-1.0.lua"]:20: in function <...dOns/BagBrother/libs/WildAddon-1.0/WildAddon-1.0.lua:18>
[string "@BagBrother/libs/WildAddon-1.0-2/WildAddon-1.0.lua"]:56: in function <...dOns/BagBrother/libs/WildAddon-1.0/WildAddon-1.0.lua:53>
[string "=[C]"]: ?
[string "@BagBrother/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:29: in function <...her/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:25>
[string "@BagBrother/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:64: in function Fire' [string "@BagBrother/libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <BagBrother/libs/AceEvent-3.0/AceEvent-3.0.lua:119> [string "=[C]"]: ? [string "=[C]"]: in function
LoadAddOn'
[string "@Blizzard_UIParent/Vanilla/UIParent.lua"]:220: in function UIParentLoadAddOn' [string "@Blizzard_UIParent/Vanilla/UIParent.lua"]:291: in function
TimeManager_LoadUI'
[string "@Blizzard_UIParent/Vanilla/UIParent.lua"]:525: in function <Blizzard_UIParent/Vanilla/UIParent.lua:494>
Locals:
(*temporary) = "bad argument #2 to '?' (Usage: local success = C_CVar.SetCVarBitfield(name, index, value [, scriptCVar]))"
This issue resolution is mentioned here: #2021 (comment)