NPC healtbars on Kui

[Neric]

As shown on this screenshot Kui hides hides healthbars on enemy players, but not on enemy NPCs: https://imgur.com/a/3IDnKij
Apparently there is an option to do it in combat: https://imgur.com/a/ZHIK4yG

So the big question is: How to disable NPC healbars - or any healthbars for that reason - always?

[Neric]

Fun fact: This only seems to be the case in Dalaran so far, with enemy NPCs that cannot be attacked. Out of town enemy NPCs don't have a healthbar. Bug maybe?

[Neric]

Oh btw, does someone know how to fix this, because Bkader went MIA:

4x Kui_Nameplates-262CoreCore.lua:376: attempt to index field 'fonts' (a nil value)
Kui_Nameplates-262ModulesNameOnly.lua:92: in function <Kui_NameplatesModulesNameOnly.lua:78>
Kui_Nameplates-262ModulesNameOnly.lua:157: in function ?'
CallbackHandler-1.0-7:145: in function <...ameLibsCallbackHandler-1.0CallbackHandler-1.0.lua:145>
<string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[2]":13: in function ?'
CallbackHandler-1.0-7:90: in function `SendMessage'
Kui_Nameplates-262CoreLayout.lua:339: in function <Kui_NameplatesCoreLayout.lua:296>

[SomeGuy1111]

I tested https://github.com/bkader/KuiNamepla...heads/main.zip on a clean profile and I didn't get any errors at all.
"fonts" leads me to believe that for some reason LibSharedMedia-3.0 is not giving the fonts to KuiNameplates. Maybe someone more knowledgeable can help.
I'd recommend...
1. downloading a fresh copy of the addon
2. move the addon's wtf files so they are regenerated (to test if it's causing some problem)
3. enable addons one at a time, if you still get the error. (to test if there is some addon conflict)

[Neric]

This lua-errors only occur after reloading_ui, which makes it weird. To test possible conflicts I disabled all addons except for Kui and bugsack, but it still happened.

[Neric]

The lua-errors even change. This time I got an issue "display" after reloading_ui.

4x Kui_Nameplates-262ModulesNameOnly.lua:88: attempt to index field 'display' (a nil value)
Kui_Nameplates-262ModulesNameOnly.lua:157: in function `?'
CallbackHandler-1.0-7:145: in function <...ameLibsCallbackHandler-1.0CallbackHandler-1.0.lua:145>
<string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[2]":13: in function `?'
CallbackHandler-1.0-7:90: in function `SendMessage'
Kui_Nameplates-262CoreLayout.lua:339: in function <Kui_NameplatesCoreLayout.lua:296>

[SomeGuy1111]

I think both errors seem to be related to the libraries. I think that one may be ace3 related. I think it may be a loading problem, not a code problem. I think the libraries may not be loading properly or maybe the addon is not loading properly. Maybe you could try some standalone libs.

1. add "## OptionalDeps: Ace3, LibSharedMedia-3.0, LibDualSpec-1.0" to the toc. (example)
2. download standalone libs.

I could try making a completely embed lib free version. (standalone libs)
Of course I could totally be wrong and I'm not an expert.

[Neric]

It seems to be a pretty common issue, because you can find countless examples with Google, like this one:

https://stackoverflow.com/questions/...ex-a-nil-value

So my best guess is that it's just a similar declaration problem.

[SomeGuy1111]

I doubt it will fix the errors but I went ahead and uploaded a version with standalone libs. Maybe it's worth a shot.
I tested it. It seems to still work, so maybe I did it right. (?)

https://www.mediafire.com/file/bikhd...lates.zip/file

[Neric]

Nope, still beeps.

[Neric]

It seems like the attempts to fix it outside of the code are futile. This means that either Bkader can fix it, except he is missing in action, or someone else with lua-knowledge, which is rather unlikely. On a sidenote: Bkader has a pre-release of his last Skada on discord, but that one produces lua-errors as well. This makes me believe that he patched his own system in a way that he doesn't even notice these bugs, because they simply don't appear on his screen. Similar to that is using NoM0re's WA 4.1.2 which is absolutely fine, except if you export your WAs and upload them to Wago, people who download them get their 4.0.0 WA bricked. With all this awesomewotlk and ElvUI-**** around, nobody has a clean state to work with anymore, so no wonder it's all a complete mess with errors everywhere.

[SomeGuy1111]

I've got one last idea and then I'm out of ideas on how to fix it. It's a very bootleg solution that I'm not even sure applies with "/reload"

add
## LoadWith: choose the last addon to load (alphabetically)
to the toc file.
The idea is to load libs and other addons before Kui_Nameplates. (so the libs are already loaded)

[SomeGuy1111]

I tested the addon on two different servers and I still didn't get an error. I don't think it's the addon or the libs. I think it's something about your specific setup that may be giving the errors. Maybe I'm not testing enough. Do the errors happen right after reloading or do you play a while?

[Neric]

Actually during reloading. Initially it thought it could happen because of addonloader, but even if I disable everything except Kui and bugsack it happens.

[SomeGuy1111]

Sorry. I can sometimes get a little too "focused" on programming/computer related stuff. I'm probably done posting about it. I think I may be out of ideas on how to fix it anyway.