
[MoP Beta] Bug caused in another addon
Closed this issue ยท 5 comments
This error occurs when I change a setting in Pokemon Trainer NG:
> 2x ...nfig-3.0/AceConfigDialog-3.0-87/AceConfigDialog-3.0.lua:899: attempt to index field 'rootframe' (a nil value)
> [TidyPlates_ThreatPlates/Libs/AceGUI-3.0-41/AceGUI-3.0.lua]:300: in function 'Fire'
> [TidyPlates_ThreatPlates/Libs/AceGUI-3.0-41/widgets/AceGUIWidget-CheckBox.lua]:64: in function <...es/Libs/AceGUI-3.0/widgets/AceGUIWidget-CheckBox.lua:53>
>
> Locals:
> self = <table> {
> checkbg = Texture {
> }
> parent = <table> {
> }
> image = Texture {
> }
> userdata = <table> {
> }
> base = <table> {
> }
> type = "CheckBox"
> AceGUIWidgetVersion = 26
> checked = true
> text = FontString {
> }
> events = <table> {
> }
> highlight = Texture {
> }
> check = Texture {
> }
> frame = Button {
> }
> }
> name = "OnValueChanged"
>
If I disable Threat Plates, the error does not occur.
Issue in Pokemon Trainer NG: GurliGebis/WoWAddon-PokemonTrainerNG#11
This Lua error comes from the embedded Ace3 addon. I guess that Pokemon Trainer NG uses the same library.
I use an alpha version in the Mists version of TP. I will check if there is an update and if the Lua error disapears in that case.
So, I cannot reproduce this error currently. I installed Pokemon Trainer NG and only enabled TP (v12.3.0-beta2) and PT, but changing settings worked fine without any Lua error.
Did the above Lua error occur when changing a certain setting? Can you try if you still get this error only with TP and PT enabled?
The error appears when, in the settings, I chose the tooltip display while I was in frame display.
Edit: I tried reproducing the bug with the latest addons โ Pokemon Trainer NG 11.1.7-20250619-1 and ThreadPlates-12.3.0-beta2-mists โ on MoP Beta 5.5.0.61496, and the errors disappeared. Thanks!
I also got this error now when using a slider in tooltip display:
1x ...dOns/PokemonTrainer/Modules/TooltipCombatDisplay.lua:249: attempt to concatenate local 'abIcon' (a nil value)
[TidyPlates_ThreatPlates/Libs/AceGUI-3.0-41/AceGUI-3.0.lua]:300: in function 'Fire'
[TidyPlates_ThreatPlates/Libs/AceGUI-3.0-41/widgets/AceGUIWidget-Slider.lua]:65: in function <...ates/Libs/AceGUI-3.0/widgets/AceGUIWidget-Slider.lua:56>
But I only got the error once. This error does not seem like an error from TP or Ace3, but something that's happening in the options of Pokemon Trainer. As PT uses the Ace3 version from TP, this is shown as the Ace3 source, but the error should not be from TP.
It could be related to an not completely working version of Ace3 (currently, TP uses an alpha version of Ace3, so that's possible).
I did some testing now and I can still reproduce this error, even without TP being enabled.
- First, I only enabled Pokemon Trainer NG. But this way it's not enabled. /pt does not work. It seems that Pokemon Trainer NG is not loaded at all.
- Next, I installed Ace3 separately. After that, PT did work and I could load the options.
- For the following tests, only Pokemon Trainer NG and Ace3 were enabled.
- I tested two versions for Ace3: r1361-alpha and r1362-alpha, but this did not make a difference (TP still uses r1361-alpha).
- After opening Pokemon Trainer NG, the radio button "Display: Frames" and the menu item "Display: Frames" must be selected. If this is not the case, select these two options, exit WoW, remove all SavedVariables for Pokemon Trainer NG and start WoW again.
- Then, select the menu item "Display: Tooltip"
- Next, select the radio button "Display: Tooltip".
- With that, I get the inital error still:
Message: ...nfig-3.0/AceConfigDialog-3.0/AceConfigDialog-3.0.lua:899: attempt to index field 'rootframe' (a nil value)
Time: Fri Jun 20 13:50:16 2025
Count: 1
Stack:
[Interface/AddOns/Ace3/AceGUI-3.0/AceGUI-3.0.lua]:300: in function 'Fire'
[Interface/AddOns/Ace3/AceGUI-3.0/widgets/AceGUIWidget-CheckBox.lua]:64: in function <...ns/Ace3/AceGUI-3.0/widgets/AceGUIWidget-CheckBox.lua:53>
So, it's not related to TP, but to how Pokemon Trainer NG uses Ace3 and it still seems to be happening with the newest alpha version of Ace3. I did not test it with the latest stable version of Ace3. Maybe that works.