Thanks. Well, it figures, but am I the only one thinking it’s pretty bad that this happens by default? Surely one of the benefits of breaking some of the engine code out into plugins is that you don’t have to include a bunch of stuff your project doesn’t need, but I bet most people aren’t aware they get all this stuff by default.
I really think the plugin dependencies need some work so there is a distinction made between ‘being enabled when you open the project in the editor’ and ‘being a dependency that gets linked in’. The former shouldn’t imply the latter.
Yep I know plugin objects can have their own config values, but that’s not what I was referring to. This doesn’t allow you to provide overrides for engine level config properties, which would be required for the examples I gave. Ideally, you should be able to add a PluginInput.ini, PluginEngine.ini etc, which would be processed as part of the config hierarchy, after the config files in the engine folder, but before those in a project folder. So plugins could override engine values, but project config files would have the final say.