Ace libraries madness. Why?

When i installed many mods, i get every time when i mine, loot or fight, many Ace library errors.

I take a look in for example AckisReceipeList, and there is /Libs/ directory with Ace files inside.

But... i have already /Ace2/ installed. Why another Ace files added in /Libs/

Removing Ace files from /libs/ and play again. But the errors are not gone. This time from QuestAnnouncer2. Remove it again, restart.

Huh, again error from another mod? There are so many Ace librares?

When i do little search, i'm surprised many mods has /libs/ directories with Ace files inside.

I cannot get rid off Ace errors in Swatter. I must remove all copies to reduce errors, to make sure i use only latest version.

What is that? Why have i installed /Ace2/ library package, even it can run without /Ace2/ ..... And why every mod has "own" libraries files?

Ace /libs/ are found for example in:

- Atlasloot

- AutoProfitX

- BonusScanner

- Clearfont2

- Decursive

- EnchantingSell

- EnchantList

- FishingAce

Actually too much mods.

Tell me, is there no risk for old libraries errors? Is main library /Ace2/ no longer needed?

Only GuildAds seems to have newer Ace 3.0 files.

Surprising, many Ace libraries are identical. Same version, but why do i need so many copies of Ace library? But there are some old versions from old mods. That means i have different Ace libraries installed. That is not good idea.

Have we so many noobs to forgot install /Ace2/ main library?|||ok Ace2 AND all the libs inside those folders are required for the addons to work DO NOT REMOVE them, if you are having trouble with then then id suggest that you download the Ace updater and use that to install your Ace mods.|||Ok, this is gonna be a bit complicated, so let me know if you don't get this.

Every Ace mod has a Lib folder, as you've seen. The problem comes in is that when WoW first loads up, it takes the first instance of a Lib file and loads it and ignores any other "duplicates" it finds along the way since it's already loaded. The problem? If the author of the first loaded mod hasn't updated either his mod or his Libs, it will produce errors and more times than not carry over to other Ace mods.

For example, ModA and ModB both have Lib1. However, ModA hasn't updated their Lib1 where ModB has and adjusted thier code accordingly. WoW loads up and ModA's (first alphabetically) Lib1 is loaded into memory. It then comes to ModB's Lib1 and ignores it cause WoW thinks it's already loaded. When the game fully loads, ModB comes up with an error because it's referencing ModA's outdated Lib1.

Hope that makes sense. To ensure your libs are always up to date, you'll need to use WAU as Lothaer suggested and change some settings.

If you decide to do this, you'll need to go to Edit -> Preferences and UNCHECK "Default Mode WITH Externals". After that, CHECK "Delete Before Updating" (which should always be done anyways) and "Skip Version Check". Hit "OK". Now press F10 and hit "Yes". This will purge all your currently installed mods and reinstall them, BUT this time with all the Libs installed as separate "addons".

The only "problem" is that if you go to your addons folder, you'll see at large clump of "Lib: XXX" which will also show up in the Addons screen in WoW. Unfortunately, that's the price you'd have to pay to make sure all your Libs are ALWAYS up to date. However, 95% of any errors at this point should be mod specific, so you'd only have to contact that specific mod author about it instead of trying to figure out if a Lib is out of date or the mod has a prob.

Hope this helps out. As always, it's up to you.|||A good explanation, I'll just add that you should turn "Skip Version Check" back off afterwards to save time and bandwidth.|||Quote:




you should turn "Skip Version Check" back off afterwards




Yeah, that's probably a good idea. Forgot to mention that (it was 1am here, gimme a break).|||I have tried it (first backup all mods) with WAU. But i have not clicked out Default Mode WITH Externals. After updating all mods (with deletion before) it seems working .... but ... some mods reacts strange. For example ATSW. This mod works good, but not with Enchanting profession. It scans, but shows nothing, no spells, and when i close it, it never open again. Another Tailoring and Cooking has no problems. That is very bad error.

I put all mods back from backup and ATSW works now good with Enchanting profession, all spells are now showed in the window.

Who can tell me about this problem? (all addons are manually installed)|||Any mod from Wowace is beta quality, sometimes you get bugs.|||Personally, I've also had plenty of problems with ATSW. With it's lack of continuous updates and constant errors, I switched over to Skillet (at WoWAce) and have yet to have a problem with it. Similar layout and everything. I'd say give that a shot if you're getting fed up with ATSW.|||Well, when i disable ATSW mod, it still not working with Blizzard Skill window. There is more wrong!|||Quote:








Well, when i disable ATSW mod, it still not working with Blizzard Skill window.




I would certainly hope not, since you turned it off.

Just get rid of it and it's saved variables and get Skillet. It'll save you a TON of headaches, trust me on this one.

http://www.wowace.com/wiki/Skillet