TBC classic error

Question

TBC classic error

Nillx opened this issue 3 years ago · 4 comments

Heya, do you plan to update the addon for TBC Classic? Currently getting this error:

1x ...erQuestTracker\QuestWatchHelper\QuestWatchHelper.lua:164: attempt to index upvalue 'BlizzardTrackerFrame' (a nil value)
[string "@ButterQuestTracker\QuestWatchHelper\QuestWatchHelper.lua"]:164: in function `KeepHidden'
[string "@ButterQuestTracker\ButterQuestTracker-1.9.27.lua"]:58: in function <...aceButterQuestTracker\ButterQuestTracker.lua:43>
[string "=[C]"]: ?
[string "@Attune\Libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:70: in function <...aceAttune\Libs\AceAddon-3.0\AceAddon-3.0.lua:65>
[string "@Attune\Libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:527: in function `EnableAddon'
[string "@Attune\Libs\AceAddon-3.0\AceAddon-3.0-13.lua"]:630: in function <...aceAttune\Libs\AceAddon-3.0\AceAddon-3.0.lua:615>

opusaug · Answer 1 · 2021-06-28T05:16:04.000Z

This (or something similar) is also happening on Classic-Era:
Questie\Database\QuestieDB.lua:582: attempt to call field 'QueryQuest' (a nil value)
Questie\Database\QuestieDB.lua:582: in function GetQuest' ...tterQuestTracker\LibQuestHelpers\LibQuestHelpers.lua:178: in function SetIconsVisibility'
...tterQuestTracker\LibQuestHelpers\LibQuestHelpers.lua:153: in function RefreshIconsVisibilityForQuests' ...tterQuestTracker\LibQuestHelpers\LibQuestHelpers.lua:139: in function SetAutoHideQuestHelperIcons'
...aceButterQuestTracker\ButterQuestTracker-1.9.27.lua:146: in function <...aceButterQuestTracker\ButterQuestTracker.lua:145>

cecilia-sanare · Answer 2 · 2021-06-28T16:13:12.000Z

Unfortunately I don't have an active WoW subscription to work through these issues otherwise I definitely would.
I'm currently fairly tight on money right now and an active subscription for a game I don't play just isn't in the cards for me.

If someone is interested in maintaining this add-on feel free to message me, otherwise I'll be putting up a notice later this week that this add-on is no longer maintained.

cecilia-sanare · Answer 3 · 2021-06-28T19:12:11.000Z

Hey @opusaug!

I don't plan on deleting the repository or anything drastic like that!
I was just going to put notices on the README and CurseForge so that people know it's looking for a maintainer.

opusaug · Answer 4 · 2021-06-28T18:36:12.000Z

Hi Ceci, I'm an IT pro who specializes in business systems support and database management. My coding skills usually don't go beyond SQL queries and VBA macros, which is a long way to say I don't *really* consider myself a programmer. I joined GitHub last night because I was playing Classic, got a bunch of errors, and ButterQuestTracker is the last problem addon I'm dealing with. For a few minutes earlier today, I considered pulling it from my installation and using the one built into Questie, but then I enabled that and remembered all the reasons why I wasn't using it. If someone magically appears to volunteer for you, it's unlikely they'll have less experience than me, so you should give them the project. But you probably know as well as I do how precious volunteers are. Since I'm unemployed at the moment, and I'm desperate to bolster my coding skills right now, digging into the addon may at least help me learn my way around GitHub. I don't have any illusions that I can do enhancement requests, but maybe I can at least get it to stop the errors. That all said, if I were in your shoes, I might still put up the notice and tell me to fork it and put it under a new name. That way the original project could remain out there for someone more capable to pick up if they choose. It's up to you, of course. Best regards, Chris

…

On Mon, Jun 28, 2021 at 12:13 PM Ceci ***@***.***> wrote: Unfortunately I don't have an active WoW subscription to work through these issues otherwise I definitely would. I'm currently fairly tight on money right now and an active subscription for a game I don't play just isn't in the cards for me. If someone is interested in maintaining this add-on feel free to message me, otherwise I'll be putting up a notice later this week that this add-on is no longer maintained. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#98 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUUTJWKCAKTZ6OJHJ26CI2LTVCNSFANCNFSM45FDQTVA> .

Share to