From FuBar to LDB: Writing Your Own AddOn Loader
In terms of menubar utilities, it appears I’m just a sheep following the lead of the enlighted Mr. Kestrel. It was after one of his posts that I moved from Titan Pannel to FuBar, and it was again after reading his November post on LDB that I migrated from FuBar to LDB (currently using StatBlockCore myself).
One of the small things which have been irking me since the transition, though, is that a certain amount of FuBar plugins (like DurabilityFu) are Load on Demand, and since I no longer use FuBar, there’s no longer anything to demand that these are loaded.
This has been annoying me for a while now, and I finally decided to write my own AddOn loader.
Fortunately, it’s so easy even someone as ungifted for coding as myself can do it. I suspect I might run into issues at some point but for the time being, it works.
And this is how you do it.
First, go to your Interface\AddOns\ folder.
Create a new folder, name it eg. MyLoader
In this folder, we will create just one new text file, called MyLoader.toc
And we will add the following code:
## Interface: 30400 ## Title: MyLoader ## Notes: A little self-made utility to load some load-on-demand addons. ## Version: 0.1 ## DefaultState: enabled ## OptionalDeps: loadondemandaddonX, loadondemandaddonY, loadondemandaddonZ, (...)
Make sure that every AddOn you want to load with OptionalDeps are named exactly as their respective Folder names, save it, and voilà, your own AddOn loader is done.
Clunky, and you’ll have to update the ## OptionalDeps (and ## Interface) information manually if things change, but it does the trick and only requires a minute to make.
Why pick OptionalDeps (Optional Dependencies)? If you use required dependencies instead, the little loader we just wrote will not work if for whatever reason one of the addons you want to load is not enabled or not present.







