Admin
SCUM server logs and audit
Searchable gameplay, chat, kill, administrator and system logs create a traceable history for support, moderation and operations.
SCUM server logs and audit bring important events into a searchable history. Administrators can verify what happened in the game, chat or during a staff action without manually reading raw files on the server.
One timeline for the question: what happened?
Different log types keep their domain meaning, but authorised users can find them in the same administration and the correct server context.
Evidence available to the team
The exact coverage depends on sources enabled for the server and capabilities available through NODERAgent.
- gameplay, chat and kill events with time and available player context
- administrator commands, targets and confirmed operation results
- lockpick, damage, mine and other supported module events
- system and agent records required for operational diagnosis
Using logs for support and moderation
Logs become most valuable when a team needs to verify a claim or reconstruct an event sequence.
- investigate a player report by time and server
- find communication surrounding a conflict or rule
- check who started an administrative operation and its result
- relate a gameplay event to an alert or support ticket
A clear view without losing source meaning
Nodera normalises supported events into filterable views while retaining safe source context in the detail. A parsing failure cannot be presented as a valid zero result.
Records remain separated by server. Community-wide policies such as bans use an explicit shared model rather than accidental mixing of logs between servers.
Decisions that can be explained later
Support and moderators work from a timeline, while administrator actions remain traceable for the authorised team.
Need more information?
We will show you how this feature can work on your server. Contact us or join us on Discord.
