Where the logs are
ShooterGame/Saved/Logs/ShooterGame.log is the main log. Crash dumps land in ShooterGame/Saved/Logs/ too. The panel console shows the same lines live. Kowalski can read them: "why did my ARK server stop?"
It stops right after "starting"
- Out of memory: ARK needs 8 GB minimum (Evolved) / 12-16 GB (Ascended); more with mods and big maps. The console shows a kill without an error, the resource graph hits the limit. Upgrade RAM.
- A broken mod: the log names the mod (
Mod ... failed to load). Remove its ID. - Corrupt save:
Failed to loadnear the map name. RenameSavedArks/<Map>.arkand restore the newest dated backup from the same folder (<Map>_dd.mm.yyyy_hh.mm.ss.ark→ rename to<Map>.ark).
It stays on "starting" for a long time
Normal for 2-5 minutes (map loading), longer after updates or with many mods. If it exceeds 15 minutes with no new console lines, kill it and start again; if that repeats, check RAM.
Nobody can see the server
- The list needs a few minutes after start.
- Search by the exact
SESSION_NAMEand with the Unofficial filter; passworded servers hide unless Show password protected is ticked. - Add it as a Steam favourite with the query port, not the game port.
- BattlEye: if players get kicked instantly, set
BATTLE_EYEto0in Startup (or tell them to enable it on their side).