Skip to main content

plugins.ini

plugins.ini controls which plugins load at startup. It lives in the user config directory alongside settings.ini.

Format​

One plugin-id=state row per plugin, where state is enabled or disabled:

framelift.playlist=enabled
framelift.history=disabled
example.my_plugin=disabled
  • Keys are plugin ids (the dotted id from a plugin's .Plugin.json). Each plugin is one runtime DLL/SO with one id and one row.
  • A plugin absent from the file is enabled. You only ever need to add a row to disable something; the default is always on.

Editing it​

You rarely edit this file by hand — the Settings → Plugins page lists every loaded plugin with a toggle, and writes plugins.ini for you. Changes take effect on the next launch.

Relationship to lean builds​

plugins.ini toggles plugins (the DLLs/SOs in plugins/) at runtime. To remove a built-in host module at compile time instead, use the FRAMELIFT_MODULE_<NAME> CMake options — see Lean Builds. A built-in module that was compiled out is simply not present; it has no plugins.ini row.