search

AcidWeb / CurseBreaker

TUI/CLI addon updater for World of Warcraft.
GNU General Public License v3.0
764 stars 72 forks source link

RuntimeError: This feature requires the Wago Addons API key. #359

Closed AHrubik closed 1 year ago

AHrubik commented 1 year ago

As of this morning my client seems unable to read my addons that were installed from WoW Interface and is insisting that I enable the Wago Addons API to use the client.

Is this an intended change?

Version: CurseBreaker 4.3.4

AcidWeb commented 1 year ago

There was no change. Please show me output of status command.

AHrubik commented 1 year ago

Here is what I see.

Command Shell Screenshot https://i.imgur.com/Jiw5XkR.jpg

Addons folder showing addons present https://i.imgur.com/ZT12Quj.jpg

AcidWeb commented 1 year ago

Ah. You using CB for a first time?

I really should push the release that improve this error message: https://github.com/AcidWeb/CurseBreaker/commit/562790de399421dac6ac82491b844d4b94a41ff5

AHrubik commented 1 year ago

Nope. I've been using it for quite awhile now even before the CurseAPI/Overwolf debacle. In fact I used it as recently as the WoW 10.0.5 update to grab newer version of my addons.

AcidWeb commented 1 year ago

In this case something nuked your settings. Do you maybe replaced your WTF directory? In WTF-Backup you should find some recent backup to restore the CurseBreaker.json file.

AHrubik commented 1 year ago

Ahhh ... The recent WoW update required me to delete my Cache and WTF directories to be able to connect again. This explains the issue. I was able to restore the JSON from December and after some brief (re)uninstalling and (re)reinstalling of some addons already removed and installed everything is working again.

Thank you for the help.

AcidWeb commented 1 year ago

Happy to help.