4x Couldn't open bestride\libs\AceDB-3.0-26\AceDBOptions-3.0-15.xml

Does the file exist at the location?

No. There's no suffixes (i.e. "-26" and "-15" on any of the included Ace libs

Could you.try uninstalling and reinstalling the add-on, competely?

Do you have any other add-ons that embed ace or do you have ace3 globally?

And now the error with the fresh install has changed a bit. And now that I'm really looking at it, shouldn't the options XML file be loading from the options directory, rather than the DB directory? Weird.

3x Couldn't open bestride\libs\AceDB-3.0-26\AceDBOptions-3.0.xml

Ite reverts to the intial bug once I reload the rest of my addons.

I did a fresh install, and made sure to only have bugsack and bestride enabled. I do not have Ace installed globally, although bugsack looks to have a few Ace libs. Bestride is still throwing that error. Somehow the minor version number is being appended, and there's no other info in the bugsack than that single statement.

Managed to grab the error having BugGrabber (part that BugSack relies on and hooks the LUA errors) and BugSack.

I can reproduce the error with a number of addons, specifically before the client has access to the queried folder/file and retries. Normally it'll silently fail. On load, Ace goes through and looks at the major-minor revisions to check if there were any upgrades from last run.

Example:
2x Couldn't open ChatTextures\

That "addon" does literally nothing except list itself in the Addons list. no libs, no script, nada.

So, it would seem BugGrabber is hooking way early in the load process and catching the retries, which would be an issue on their end.

Good to know. I was supremely puzzled at the behavior. I guess I was just lucky that only one of my addons was making it do that. Should I refer this to the BugGrabber people, or have you already done that?

FWIW, technically BugGrabber is doing what it's supposed to. Those are technically errors. Are they, "OMG the world is burning!" errors? No.

Ultimately, it's likely an issue on Blizzard's end with the client as these popped up regularly on the Beta and showed up as regular LUA errors on Live until one of the hotfixes earlier in the week.

Can report it to BugGrabber, but be prepared for the "Working as intended. Blizzard's fault." answer.

@DanSheps Might wanna freshen the Libs anyway just to be safe.

hehe...I will let it drop then, since it's really just a cosmetic issue for me at this point. No harm being done on my end other than having to look at a red bugsack icon. Thank you for taking the time to discuss this with me. :)

Just for the sake of posterity:

Woke up and decided to see if I could break things. Only loaded my dummy addon.

Logged in, no errors. After a /reload, it threw the "Couldn't open...".

Log to character select and back in. Same error.

Log out completely and back in. No error.

So, something is going whacko with the client and addons.

I really hate those earworms that crawl in and whisper....but, but....I need to KNOW. They've been responsible for more 3am coding sessions than I care to think about anymore.