In r126 of LibBabble-Boss-3.0 (from November 24), the English "Sjonnir the Ironshaper" was changed to "Sjonnir The Ironshaper" (capital "T" on "the") for all translations, as that's the proper name. That is still current in the latest r134.
The problem is the latest AtlasLoot v5.02.01 (Nov. 22) is referring to that guy as "Sjonnir the Ironshaper" (lower case "t") in its wrathofthelichking.lua file. Which causes errors accessing the AtlasLoot WotLK loot lists:
LibBabble-Boss-3.0-90133 (LibBabble-Boss-3.0):65: LibBabble-Boss-3.0: Translation \"Sjonnir the Ironshaper\" not found.\n...\\AtlasLoot_WrathoftheLichKing\\wrathofthelichking.lua:429: in main chunk:\n<in C code>: in function `LoadAddOn'\nAtlasLoot-|cffFF8400AtlasLoot Enhanced v5.02.01|r\\Core\\AtlasLoot.lua:1079: in function `AtlasLoot_IsLootTableAvailable'\nAtlasLoot-|cffFF8400AtlasLoot Enhanced v5.02.01|r\\Core\\AtlasIntegration.lua:50: in function `AtlasLootBoss_OnClick'\n<string>:\"*:OnClick\":1: in function <[string \"*:OnClick\"]:1>.
Using the USEng WoW client here. This problem has been occurring to many people using different WoW clients over the past 5 days (check the comments for LibBabble-Boss-3.0).
All the errors (for English anyway) were squashed a couple of versions ago, if you are still having problems, try deleting all the old files before upgrading to be sure the old files get overwritten.
No; Babble doesn't save its translation lists in saved variables. I'm not getting this issue. However, looking at the project page, the reason you're not getting the new versions is pretty obvious; nothing has been tagged as a beta or release in quite some time. Manually download the latest version from the wowace project page, and you should be fine. (Just don't let the Curse Client bulldoze it.)
Kicking 4 errors on load, and a 5th on opening AtlasLoot. Latest alpha from wowace (r161); just wanted to make sure this was known.
Note that my alpha builds are never guaranteed to work, that is why they are alphas. I frequently commit half-done stuff in case one of the other guys has time to finish it before I do.
EDIT: Or do you mean alpha BabbleBoss not working with release AtlasLoot? Not sure why that would happen.
[2009/01/19 19:42:14-763-x1]: LibBabble-Boss-3.0-90161 (LibBabble-Boss-3.0):65: LibBabble-Faction-3.0: Translation "Alliance Vanguard" not found.
AtlasLoot-v5.03.01\TableRegister\loottables.en.lua:1034: in main chunk
---
[2009/01/19 19:42:14-763-x1]: LibBabble-Boss-3.0-90161 (LibBabble-Boss-3.0):65: LibBabble-Faction-3.0: Translation "Horde Expedition" not found.
AtlasLoot-v5.03.01\TableRegister\loottables.en.lua:1040: in main chunk
---
[2009/01/19 19:42:14-763-x1]: LibBabble-Boss-3.0-90161 (LibBabble-Boss-3.0):65: LibBabble-Faction-3.0: Translation "Winterfin Retreat" not found.
AtlasLoot-v5.03.01\TableRegister\loottables.en.lua:1053: in main chunk
---
[2009/01/19 19:42:14-763-x1]: LibBabble-Boss-3.0-90161 (LibBabble-Boss-3.0):65: LibBabble-Zone-3.0: Translation "Vault of Archavon" not found.
AtlasLoot-AtlasLoot Enhanced v5.03.01\DefaultFrame\DewDropDown.lua:209: in main chunk
---
And the 5th.
[2009/01/19 19:58:17-763-x1]: LibBabble-Boss-3.0-90161 (LibBabble-Boss-3.0):65: LibBabble-Zone-3.0: Translation "Old Stratholme" not found.
AtlasLoot-AtlasLoot Enhanced v5.03.01\Core\TextParsing.lua:535: in function `AtlasLoot_FixText'
AtlasLoot-AtlasLoot Enhanced v5.03.01\Core\AtlasLoot.lua:601: in function `AtlasLoot_ShowItemsFrame'
AtlasLoot-AtlasLoot Enhanced v5.03.01\Core\HooksandAPI.lua:309: in function `AtlasLoot_ShowBossLoot'
AtlasLoot-AtlasLoot Enhanced v5.03.01\DefaultFrame\AtlaslootDefaultFrame.lua:113: in function `AtlasLootDefaultFrame_OnShow'
<string>:"*:OnShow":1: in function <[string "*:OnShow"]:1>
<in C code>: in function `Show'
AtlasLoot-AtlasLoot Enhanced v5.03.01\Core\Launchers.lua:23: in function <Interface\AddOns\AtlasLoot\Core\Launchers.lua:16>
<in C code>: ?
DockingStation-0.0.25 (Beta)\Frames.lua:250: in function <Interface\AddOns\DockingStation\Frames.lua:248>
---
So yeah, AtlasLoot vs. LibBabbleBoss. It's not bothering me, other than my Bugsack not being green, and just wanted to make sure they were known. I know alphas might not be fully stable, but if you get no feedback on them they tend to stay slightly broken :D.
[edit] Has dropped to 1 on load and 1 on AtlasLoot launch (the Vault and Strat respectively).
Where do you want error reports posted, in this thread, a new thread here, curse ticket or on the atlasloot website? I am also getting similar error messages to those listed above.
The problem is the latest AtlasLoot v5.02.01 (Nov. 22) is referring to that guy as "Sjonnir the Ironshaper" (lower case "t") in its wrathofthelichking.lua file. Which causes errors accessing the AtlasLoot WotLK loot lists:
LibBabble-Boss-3.0-90133 (LibBabble-Boss-3.0):65: LibBabble-Boss-3.0: Translation \"Sjonnir the Ironshaper\" not found.\n...\\AtlasLoot_WrathoftheLichKing\\wrathofthelichking.lua:429: in main chunk:\n<in C code>: in function `LoadAddOn'\nAtlasLoot-|cffFF8400AtlasLoot Enhanced v5.02.01|r\\Core\\AtlasLoot.lua:1079: in function `AtlasLoot_IsLootTableAvailable'\nAtlasLoot-|cffFF8400AtlasLoot Enhanced v5.02.01|r\\Core\\AtlasIntegration.lua:50: in function `AtlasLootBoss_OnClick'\n<string>:\"*:OnClick\":1: in function <[string \"*:OnClick\"]:1>.
Using the USEng WoW client here. This problem has been occurring to many people using different WoW clients over the past 5 days (check the comments for LibBabble-Boss-3.0).
Note that my alpha builds are never guaranteed to work, that is why they are alphas. I frequently commit half-done stuff in case one of the other guys has time to finish it before I do.
EDIT: Or do you mean alpha BabbleBoss not working with release AtlasLoot? Not sure why that would happen.
And the 5th.
So yeah, AtlasLoot vs. LibBabbleBoss. It's not bothering me, other than my Bugsack not being green, and just wanted to make sure they were known. I know alphas might not be fully stable, but if you get no feedback on them they tend to stay slightly broken :D.
[edit] Has dropped to 1 on load and 1 on AtlasLoot launch (the Vault and Strat respectively).