Configuration
This guide covers configuration for a Frags4u-managed Palworld dedicated server. It is written for the Frags4u managed environment, so the server identity, allocated resources and network values shown in the Panel take priority over defaults copied from a generic self-hosting guide.
Palworld operational notes • Configuration: Persistent settings live under Pal/Saved, including PalWorldSettings.ini for supported dedicated-server configuration. • Backups: Back up Pal/Saved before game updates, world transfers, experimental mods or broad settings changes. • Startup: The managed Linux startup uses PalServer.sh and the server's allocated resources/network settings.
Recommended checks
- Take a recovery point before a broad settings change.
- Prefer Panel-managed settings wherever Frags4u exposes them.
- Change one logical group at a time so the result is attributable.
- If syntax is damaged, keep the ticket attached to the server; AI remediation is limited to approved bounded files and preserves a snapshot first.
When to stop changing things If the failure persists after one controlled test, avoid repeated restarts, broad file deletion or unrelated configuration changes. Preserve the newest evidence. A clean process start, a listening game endpoint and a successful client connection are separate signals; record which one is failing.
What to send Support Include the affected server, approximate failure time, exact error text, the last change made and whether the problem affects startup, connectivity, performance, updates or mods. Technical tickets remain bound to the selected game server so staff and AI Support can inspect the correct managed context rather than guessing.
Backups and recovery Before destructive maintenance, keep a verified recovery point. For Palworld, the persistent save/world and configuration areas described above should be treated separately from replaceable base-game assets. Do not use a wipe, reinstall or deletion of runtime files as a first troubleshooting step.
Frags4u AI Support safety boundary AI Support can only use approved typed support actions inside the customer's server boundary. It has no root, sudo, general shell, SSH or node-administration access. Any bounded repair requires customer consent, creates a protected snapshot first, remains limited by the existing remediation policy, and is followed by restart/post-repair verification where a restart is required.