Logs, NODERAsearch and admin audit
Which log to use for chat, squads, lockpicking, mines, destruction or admin intervention and how to work with NODERAsearch.
On this page
Logs help answer the question of what happened, when and on which server. They are intended for checking incidents, moderating and auditing administrator actions. Most pages are read-only and do not change game state.
Start with the right server and time
- Select a server in the top bar.
- Find out the approximate date and time of the event.
- Select a log by incident type.
- Use narrow filters first, then general search.
- Make a note of the relevant record and reason when deciding.
Which page to use
| I need to find out | Page |
|---|---|
| What the player wrote and in which chat | In-game chat log |
| Changes in squads | Squad log |
| Lockpick attempt, result and object | Lockpick log |
| Mine, owner, victim and sector | Mines log |
| Destroyed object, actor and owner | Destroy log |
| Administrator command or teleport | Admin Log |
| Question across related logs | NODERAsearch |
Useful filters
Chat supports text, date, scope Global/Local/Squad/Admin, player and distinguishing player from outgoing system messages. Lockpick adds type, result, object and sector. Mines works with owner, victim, item, sector, flag and live state. Destroy lets you filter by state, type, actor, owner, object, and sector.
Squad timeline is derived from differences between saved snapshots. It is suitable for tracking a change, but may not represent the exact second of a player's entry or exit.
How to use NODERAsearch
NODERAsearch accepts a free text question and an optional date range. It is useful, for example, for checking a lost object, the death or coma of a player, or an incident with a vehicle. The result and history are available in the request detail.
NODERAsearch only searches and explains available records. It does not return items, create vehicles, ban players, or perform damage compensation. The administrator will decide on any intervention in the relevant tool.
Admin Log and internal NODERAudit
Admin Log is a user audit trail of commands and teleports. It can be filtered by date, type, command, administrator, target and sector; the owner also has the protected possibility of removal according to the rules of the project.
NODERAudit is an internal host diagnostic designed especially for serious crashes and operational intervention of the platform. A regular customer server administrator does not need it and may not have it available.
Example from Main
For 30 days until 1 September 2026, Main recorded 4,135 player chat messages, 9,487 outgoing or system messages, 725 lockpick records, 472 mine records, 434 destroy records and 821 administrator events. NODERAsearch had 13 completed requests - most commonly general check and player death. NODERAudit had no crash record during this period.
Secure proof sharing
- Share only the snippet necessary to explain the decision.
- Hide the identifiers, coordinates and data of unrelated players.
- Do not send the full technical content of the request, token, webhook address, or internal server paths.
- In case of ambiguity, state that the squad change or the sought conclusion is derived data.