The Satisfactory Config Editor built into the LoafHub panel lets you change your dedicated server’s core settings straight from your browser — no FTP client, no SSH, no hunting through the container filesystem. It edits the server’s real on-disk configuration files for you: a friendly grouped form covers the settings people actually change, and raw editors give you full access to Game.ini and Engine.ini when you want it. There is one important rule that shapes how the whole tool works — Satisfactory rewrites these files every time it shuts down cleanly, so you can only save changes while your server is stopped. This guide walks through where to find the editor, the offline-save rule, every setting in the form, the raw editors, and the settings that live somewhere else entirely. It applies to Satisfactory dedicated servers you host with Loafhosts.
What the Satisfactory Config Editor Does
The Config Editor reads and writes the three configuration files a Satisfactory dedicated server keeps under FactoryGame/Saved/Config/LinuxServer — Game.ini, Engine.ini and GameUserSettings.ini. Rather than download those files, edit them locally and upload them back, you open the editor in the panel and change values directly. It is split into two halves: a structured form for the handful of settings that are safe and verified to persist, and raw text editors for Game.ini and Engine.ini when you need to change something the form does not expose. The form only shows settings the panel has confirmed actually take effect on a dedicated server, so you are not guessing which keys work.
Note: The editor writes the server’s real .ini files on disk — Game.ini, Engine.ini and GameUserSettings.ini — not a separate copy
Note: The form covers the common, verified settings; the raw editors cover everything else in Game.ini and Engine.ini
Note: It is the same in-browser editing approach used for our Reforger, Rust and Project Zomboid servers
Finding the Config Editor
Open your Satisfactory server in the panel and look at the left sidebar. Under the Game section you will find a Config Editor item, sitting just below Change Game / Change Location and above your game tools. Clicking it opens the editor in place — the sidebar and the live status header stay where they are, and the page header reads Config Editor with a Satisfactory tag. The item only appears on Satisfactory servers; if you do not see it, the editor is not enabled for that server.
Note: The Config Editor item lives in the Game section of the server sidebar, under Change Game / Change Location
Note: It only shows up on Satisfactory servers, so it will not appear on your other games
Tip: The editor opens over the page without leaving it — your sidebar and the live server status bar stay visible the whole time
The One Rule: Edit While Your Server Is Stopped
This is the single most important thing to know. Satisfactory rewrites Game.ini, Engine.ini and GameUserSettings.ini whenever it shuts down gracefully. If you saved while the server was running, the game would overwrite your changes the next time it stopped, and your edits would silently disappear. To prevent that, the editor only lets you save while the server is fully stopped. You can open the editor and review every current value at any time, in any power state — reading is always allowed — but the Save button stays disabled until the server is offline. A banner at the top tells you which state you are in: a green banner confirms the server is stopped and your changes will apply on the next start, while an amber banner asks you to stop the server first and shows the current state.
Note: Saving is only allowed while the server is fully stopped — the Save button is disabled otherwise
Note: Reading and reviewing the current values works in any state, even while the server is running
Tip: Stop your server, make your edits, save, then start it again — the green banner confirms you are good to go
The Form: Gameplay, Saves, Network and Events
The form groups the verified settings into Gameplay, Saves, Network and Events. Each field shows the file it writes to and a short note explaining what it does, and number fields enforce a sensible range so you cannot save a value the server would reject. The settings are:
- Max Players (Gameplay, Game.ini) — how many players can be connected at once. The default is 4 and you can set it from 1 to 8. Satisfactory is tuned for around four players; higher counts are unofficial and can hurt performance.
- Rotating Autosaves (Saves, Engine.ini) — how many rotating autosave files the server keeps. The default is 3 and the range is 1 to 10.
- Initial Connect Timeout (s) (Network, Engine.ini) — seconds to wait for a brand-new connection to establish before dropping it. The default is 30, the range is 10 to 120, and you raise it for players on slow connections.
- Connection Timeout (s) (Network, Engine.ini) — seconds before an already-established connection is treated as timed out. The default is 30 and the range is 10 to 120.
- Disable Seasonal Events (Events, GameUserSettings.ini) — a toggle that turns off seasonal events such as FICSMAS. It is off by default, meaning seasonal events are enabled.
Tip: Every number field is range-limited, so you cannot accidentally save a value the server would refuse — Max Players caps at 8, autosaves at 10, the timeouts at 120 seconds
Tip: Raise the two timeouts if players on slower connections keep dropping during the join
Note: There is a quirk with Disable Seasonal Events — when you turn it on the engine reads the setting on startup and then removes the line, so after a restart the toggle shows as off again even though seasonal events stay disabled
The Raw Editors: Game.ini and Engine.ini
Above the form are three tabs: Form, Game.ini (raw) and Engine.ini (raw). The raw tabs show the full text of that file, with its path displayed so you know exactly what you are editing. Whatever you type is saved verbatim — anything you set here that the form does not cover is at your own risk, so this is the path for people who know the exact key they want. Like the form, the raw editors are read-only until the server is stopped. Only Game.ini and Engine.ini can be edited raw; GameUserSettings.ini is handled through the form’s Disable Seasonal Events toggle.
Note: Raw content is saved exactly as typed, so a mistake here goes straight to the file — use it when you know the specific setting you need
Note: Only Game.ini and Engine.ini have raw editors; the form is the way to change the seasonal events setting in GameUserSettings.ini
Tip: If a raw file gets editing a single setting wrong, switch back to the Form tab — the form keeps the common values safe and in-range
Saving and Applying Your Changes
With the server stopped, click Save config. The editor validates your form values and writes them to the right file, leaving the rest of each file — comments and anything it does not manage — untouched. It then confirms with an inline message that reads “Saved — start your server to apply.” and a toast that reads “Config saved — start your server to apply.” A Reload button next to it re-reads the files from disk if you want to discard unsaved edits or refresh the view. None of your changes take effect while the server is off — they apply the next time you start it. If the server is no longer offline when you try to save (for example it was started in another tab), the save is refused and the editor refreshes so you can stop it and try again.
Note: Changes are written when you save but only take effect on the next server start
Tip: Use Reload to pull the current files back from disk and throw away any edits you have not saved
Note: If you have sub-users, viewing the config needs the config read permission and saving needs config update
What the Editor Does Not Touch
The Config Editor is deliberately scoped to the safe knob-level settings. Your server’s name, its passwords (the join and admin passwords) and the in-game game rules are not edited here — those live in Satisfactory’s in-game Server Manager, where you set them through the game client when you first claim and manage the server. The editor leaves all of that alone, along with the rest of your config files; it only touches the specific settings it manages, so your comments and everything else stay intact.
Note: Server name, passwords and game rules are set in-game through Satisfactory’s Server Manager, not in this editor
Note: The editor makes targeted edits — it writes only the settings it manages and preserves the rest of each file
Tip: Claim and name your server in-game first, then come back to the Config Editor for the players, autosave and timeout settings