Configs (Runes)
Edit your mods' config files without leaving the app. BepInEx writes a .cfg file per plugin, and this screen lists them and lets you change them in place.
Every *.cfg file in <server folder>\BepInEx\config, top level only. Click one to open it in the editor on the right. The subtitle says how many there are.
A file with unsaved changes shows a dot beside its name.
If the folder holds nothing, the list shows "no .cfg scrolls found". Usually that means the server has not been started since the mods were installed. BepInEx writes a plugin's config the first time it loads.
New in 1.1.0, a box sits under the Config files / Scrolls label and narrows the list.
Type and the list narrows as you go, with showing 1 of 3 underneath it while there is something in the box. Escape empties the box. Pressing / anywhere on the Configs screen puts the cursor in it and selects whatever is already there.
The matching rule is the one the Mods search uses. What you type is cut at the spaces, and a file is kept only when every piece is somewhere in what that file can be found by, capitals ignored.
A file can be found by three things. Its own name. The pieces of its name on their own, because the name is also split on dots, hyphens and underscores, so extraslots finds shudnal.ExtraSlots.cfg. And the mod that wrote it: where a scan has matched a plugin to that file name, the mod's name, its author and its full Author-ModName are all searchable, so an author's name finds their config even when the file is named after the plugin rather than the person.
With a search on and nothing matching, the list reads no scroll carries that. With no files at all it still reads no .cfg scrolls found. Those are two different problems and they now read differently, so you can tell at a glance which one you have.
The box narrows the list on screen and does nothing else. Opening, reading, saving and reverting all work from the full list and the whole file. It is emptied when you switch to another server profile, since the last realm's search is not this one's.
Open folder opens BepInEx\config in Explorer.
Reload re-reads the list and the open file from disk. If you have unsaved changes it asks first: "Discard changes?" with the file named, and a Discard & reload button.
Save writes the open file. It asks for a second click first: the button changes to Confirm save? for three seconds, then goes back to Save if you do not press it again. A config file is a live server's behaviour, and a stray click on the wrong file is worth one more press.
Switching to a different file with unsaved changes asks the same "Discard changes?" question.
BepInEx reads a config when the plugin loads, which is at server start. Some mods watch their config file and re-read it live, but most do not, and you cannot tell which from here.
The safe rule: stop the server, edit, save, start.
Editing a config while the server runs is not blocked. It just may not do anything until the next start, and a mod that does watch its file will pick up a half typed value if you save mid edit.
A plain text box. No syntax highlighting, no validation, no undo beyond what the text box gives you. What you type is what is written.
BepInEx config format is sections in square brackets, then Key = Value, with comments on lines starting with #. A typical file:
## Settings file was created by plugin Warfare v1.9.7
## Plugin GUID: Therzie.Warfare
[General]
## Enable the new weapons
# Setting type: Boolean
# Default value: true
EnableWeapons = true
Leave the comment lines alone. Some mods regenerate the file and use them.
New in 1.1.0 there is a bar above the editor: a ᚲ rune, a box with find in this file… in it, a count, and a pressable next chip.
Type in it and the first match is marked and brought into view. Enter walks to the next one, Shift+Enter walks back, and the next chip does what Enter does. The count beside the box reads 1 of 7, or no match when there is nothing to find. Matching ignores capitals, it looks for a plain run of letters rather than a pattern, and matches never overlap.
The find bar never touches the file. It does not put the cursor in the text, does not select any of it and does not write to it, so a keystroke meant for the find box can never land in the config, and the file is never left with a selection sitting there waiting to be typed over. Pressing the next chip does not pull the keyboard out of the box either, so Enter keeps walking the matches after you have clicked it. Save always writes the whole document exactly as it stands, whatever the find box happens to be showing.
Escape in the find box empties it and clears the mark.
A plain text box cannot highlight a word without selecting it, and selecting is the one thing this bar refuses to do. So the match is painted rather than selected. A layer behind the see-through editor holds the same words in the same font at the same size, with the same line height, the same padding and the same width, wrapping where the editor wraps, and the mark is drawn on that layer. Where to scroll to is worked out from where the mark actually landed rather than guessed from a line count, and the layer is scrolled along with the editor.
Some housekeeping falls out of that. Typing in the file clears the mark and the count, because they no longer stand over the words they were found in; what you typed stays in the find box, and the next Enter looks at the text as it is now. Opening another file resets the find completely. Resizing the window paints the mark again where the words have moved to, without scrolling, because you are resizing a window and not asking to jump anywhere. A file over 200,000 characters gets the scroll and the count and no paint, so a very large one cannot make the box crawl. Config files run to a few thousand characters, so that last one never happens in practice.
Only a bare *.cfg name in that one folder. A name with a path in it is refused, so nothing on this screen can reach outside BepInEx\config.
You want raids off in a difficulty mod.
Stop the server. Open Configs. The list shows Therzie.Warfare.cfg among others. Click it. The file opens on the right.
Find the key, change EnableRaids = true to EnableRaids = false. The file's name in the list gains a dot.
Press Save. It changes to Confirm save?. Press it again. The toast reads "Rune etched · Therzie.Warfare.cfg saved" and the log records it.
Start the server. Check the Log for the plugin loading without complaint.
My mod's config is not in the list. Start the server once. BepInEx writes the file on the plugin's first load. If it is still missing, the mod may not use BepInEx configuration at all.
Can I edit BepInEx.cfg itself? Yes, it is in the same folder and it is listed. Be careful, it controls whether BepInEx loads at all.
Do my configs survive a mod update? Yes. Updating a mod only touches BepInEx\plugins\<Author-ModName>. Config files are in a different folder. See How mods are matched and updated.
Removing a mod deleted my config. Only if you left the checkbox ticked in the removal dialog. It offers to delete configs whose names look like the mod's, and it copies them into the removal backup first.
Is there an undo? Not in the app. Press Reload before saving to go back to what is on disk.
Can the find bar change my file? No. It marks what it found and scrolls to it, and that is the whole of what it does. It never moves the cursor into the text and never writes a letter. See Finding text in the open file.