Most Ace2 dependencies are optional because you can run them embedded, so they don't behave like that. As such, you can run an Ace2 addons without any libraries, but it'll die on load. The errors are usually pretty clear.
If you want, you can look in the .toc file of the addon to find out it's dependencies. Or use embedded libs and forget about dependencies!
While we're discussing this I have a related query. Is there a quick way to find out what libraries your entire load up of Ace2 addons require? I've noticed I've gained 6 more libraries from the !!!standalone package (auto-unpacking is a neat feature), and using *every* library under the sun seems to against the reason I disembedded in the first place (rather and load multiple copies of one library I know have libraries I'm not sure I even use, both as bad as each other).
So I want to remove the libraies I don't use.
Should I just look at each ace2 mod .toc? Or is there a quicker way that has escaped my notice.
Can someone tell me the benifit of breaking blizzards dependancy system is?
I have been looking for documentation for the end user on the wowace standards for installing mods but am fairly confused.
I see some !!!standalone packages, some packages with externals that get installed in the same directory without externals, some addons that don't work correctly without externals. Some that are packages... some addons that duplicate the functionality of others and then cause errors. I am lost.
I will gladly help where I can but am questioning the whole process atm because of the problems I am having just getting working packages.
I am not sure that the load on demand works since I couldnt get half the mods to work that way and MCP says that they cant load on demand
Well, we haven't broken Blizzard's dependancy system. It's working as intended.
Now, if you were downloading and installing as intended, there wouldn't be any issues whatsoever. However, if you're using Standalone or disembedded libraries, then you're not using it as intended =)
All ace2 addons with libraries come with the libraries embedded. Thus no dependancies are required. If you then go and unembed them, you're not using them as originally intended, and so there are dependancy issues. We try to make this possible through OptionalDependancies, so that they still load up if the libraries exist, but if we set them to dependancies, you will -have- to download the external libraries, and we won't do that, as it ties you to a single methodology usage.
Is there a quick way to find out what libraries your entire load up of Ace2 addons require?
Fastest way I can think of: uncheck all your libraries aside from Ace2, log in, make a list of your "missing library" errors. Log out, enable the ones your addons just spammed you with errors about, leave the rest disabled. Afterward if you delete the unused ones and the !!!StandaloneLibraries directory, WAU will update your standalones the same way it updates non-library addons (instead of as a package), and not restore the ones you deleted.
On a side note, I really don't understand the recent trend toward "embedded is intended, standalone is not, kthx". I've used standalone libraries the beginning of Ace2, and the only problems I've ever had were the direct result of an addon author forgetting to add a library to the OptionalDeps in the .toc. :S
Edit: Another thing you could do would be to get an editor like UltraEdit that will search and replace through files in a directory, and replace "OptionalDeps" with "RequiredDeps" in all *.toc files.