Where Does BepInEx Store Configs and Plugins?
BepInEx lives inside each game's own folder: configs in BepInEx/config, mods in BepInEx/plugins, generated on first run.
Last updated
BepInEx installs per game, not per system. Everything sits in a BepInEx folder inside the game's own root directory: configs, plugins, patchers, caches, and logs. Two installs of the same mod loader in different games never interact, which is exactly what you want.
The folder starts nearly empty and fills itself in. Launch the game once and BepInEx generates BepInEx.cfg plus the subfolders. From then on, plugins go in plugins and their settings appear as .cfg files in config.
Where BepInEx stores this, by platform
[GameFolder]\BepInEx
The game root is the folder with the game's .exe. Main config is BepInEx/config/BepInEx.cfg; logs land beside it. Plugin configs are named by plugin GUID in the same config folder.
[GameFolder]/BepInEx
The game root holds the .x86 or .x86_64 binary. Steam games need a launch-option tweak to run through run_bepinex.sh; after that the folder layout matches Windows exactly.
[GameFolder]/BepInEx
The game root is where the .app bundle sits. Edit run_bepinex.sh to name the game app (with .app extension), make it executable, and launch through it to generate configs.
Frequently asked questions
There is no BepInEx folder. What went wrong?
Run the game once with BepInEx installed. The first launch generates BepInEx.cfg, the plugin folders, and the log file. No BepInEx folder at all means the files went into the wrong directory.
How do I install a BepInEx plugin?
Drop the plugin file into BepInEx/plugins and launch the game. Its .cfg appears in BepInEx/config after that first run. The ConfigurationManager plugin adds an in-game editor beats hand-editing files.
Notice an outdated path? Let us know.