If the user has a custom IF listed in their config.ini, the interface will be loaded even if they have selected to "disable plugins".

I do not particularly want this fixed, even if I accept that this is a bug through unintended behavior. For most pilots, it won't affect anything, but as my Neoloader project tries to provide a different mechanism for loading plugins (independently disable individual mods, load mods in order of declared dependencies, safety-net the loading process to keep the game playable even in the event of a plugin error, amid other functioality), I like to think some pilots may find benefit in turning off the default loader while leaving mine active.

If you choose to leave this system as-is (pretty please?), I will add default compliance to your config entry option, so the end result is the same unless the user specifically configures my system otherwise. I'm not aware of anyone else using this system, but compliance would be up to them.

Thanks for the report. I don't have a burning urgency to immediately fix this, as the Disabled Plugins option was more of a Quality-of-Life thing that came in from Suggestions.

That being said, long term (and it could be some time.. but I'm not sure), this will probably be "fixed" or generally made more restrictive, as we're likely to eventually add our own safety-nets to disable plugins if they throw errors, etc.

kay, understood. I'll add the compliance functionality "until then", at least.