Closed fraerie closed 1 year ago
I am still getting the unregister/jostle issue I've been having since 10.0.5, even with the new Ace 3.0 release and a fresh install of Chocolate Bar and having blown away the saved variables file for CB and reconfiguring it from scratch.
There are two Mainline.toc files
In order to stop the CB_playedtime error I had to comment out the modules in the second file. I noticed that it also didn't have the jostle2 module listed, whereas the first toc file did. When I added the jostle2 module to the list it stopped throwing the jostle error that's been bugging me since 10.0.5
I don't see those two Mainline.toc files, only one (the one with the underscore), and it does have both jostle and jostle2 listed. Is it possible that ChocolateBar-Mainline.toc is left over from some earlier version or something?
As a separate note, I found a different workaround to get ChocolateBar "running". I removed line 4, instead inserting the following. WoW changed the GetAddOnMetadata function to fail if the addon is not found in 10.1, so this just catches that.
local ok, version = pcall(GetAddOnMetadata, "CB_PlayedTime","X-Curse-Packaged-Version")
if not ok then
version = ""
end
@WPettersson see #29
@fraerie how do you install ChocolateBar? Are you using an package manager app?
@fraerie how do you install ChocolateBar? Are you using an package manager app?
most recently I have downloaded it directly from this github repository and a zip file - I am not using a package manager, normally I grab it from Curse
If you got a ChocolateBar_Mainline.toc and ChocolateBar-Mainline.toc you may not have deleted the folder before updating.
Its best to delete the whole folder before updating in case something has changed via the packaging script. Your config data is not in that folder anyway. Apparently the script changed to create a ChocolateBar_Mainline.toc instead of a ChocolateBar-Mainline.toc some time ago.
The one from GitHub has only one toc file and no interface version in it. It should will work fine except showing as incompatible in the addon list. Its the dev version that I am using for all game versions.
The version from Curse, has several toc files one for each release to show as compatible in the game.
What game version did the bug occur in?
Retail
Troubleshooting
Describe the bug.
LUA errors as listed below on log in
Steps to reproduce.
Log into WoW 10.0.1 with ChocolateBar v3.10
Expected behavior.
Not get a bunch of errors on log in
Note - the Unregister error has been persistent since 10.0.5, has been previously tested with no other addons loaded (except Bugsack to capture the issues)
I have manually updated Ace3.0 which appears to be the problematic library across all other installed addons and the issue persists.
Errors