How to Enable the Admin Log on Your ARK Server
Turn on the ARK admin log to record every admin command used on your server. Essential for multi-admin accountability and catching command abuse.
What the Admin Log Does
The admin log records admin activity on your server — who ran which commands, when. On multi-admin servers this is the difference between a trustworthy staff team and one where you have no idea who force-tamed something or demolished a player's base.
Events that get logged include:
- Admin commands executed (cheat summon, force tame, god mode, etc.)
- Structures demolished by admins using admin demolish
- Force-tame events
- Any action taken through the admin console while cheats are enabled
Enabling the Admin Log
Stop your server, open GameUserSettings.ini, and add these lines under [ServerSettings]:
[ServerSettings]
EnableServerAdminLogs=True
ServerAdminLogs=True
EnableServerAdminLogs=True— activates the in-game Admin Logging panel that admins can view from the pause menuServerAdminLogs=True— writes admin actions to the server's log file on disk
Both are worth enabling. The in-game panel is convenient for quick checks; the log file is your long-term record and can be pulled remotely.
Save the file and start the server. A restart is required — this setting does not take effect while the server is running.
Viewing the Admin Log In-Game
Any player with admin access can view the log without leaving the game:
- Press
Escapeto open the pause menu - Click Admin Logging (the toggle button in the top right area of the pause menu)
- The log panel opens — it shows recent admin events in real time
You can keep the log panel open while playing. New entries appear as they happen.
Log File Location
The full server log (which includes admin actions when ServerAdminLogs=True) is written here:
ShooterGame/Saved/Logs/ShooterGame.log
You can open this file from the File Manager in your DustBowl.Games control panel, or download it for external review. On a busy server this file can grow large — it covers all server output, not just admin actions. Search for AdminCmd to filter to admin-related lines.
Why This Matters
Without an admin log, if a player reports that someone spawned in items or demolished their base unfairly, you have no way to verify or deny it. You cannot audit your own staff.
With an admin log, every command is timestamped and attributed to a player. If an admin abuses their powers, it is in the record. This also protects good admins — if they are accused falsely, the log clears them.
For any server with more than one admin, this should be enabled from day one.
Tips
- Review the log periodically, especially after player complaints
- Combine this with a strict
ServerAdminPasswordpolicy — change the password if staff changes so former admins cannot continue using admin access - Consider announcing to your community that admin logging is enabled — it deters abuse proactively