Skip to content

Logs and investigations ​

The framework has several log sources. Choose the one that records the event you are investigating; no single console view is a complete audit trail.

Log sources ​

SourceContainsAccess
Game log.txtRuntime messages, startup diagnostics and configured engine outputHost / agent console
Player/game log tablesGameplay events recorded by AddLogEntry and related helpersACP player logs and character/account detail
admin_action_logsSupported ACP mutations, actor/target/reason and request metadataACP Admin Actions
Staff/report/refund recordsTheir dedicated staff workflowsACP Audit tabs
SMS recordsRecorded phone message dataACP SMS view
Web process outputApplication errors, SMTP failures and audit-write diagnosticsHost service/container logs
Database server logsConnectivity/engine faults and configured SQL diagnosticsDatabase administration

Investigate a player issue ​

  1. Record the account, character and approximate event time.
  2. Open the player/character record and establish the correct IDs.
  3. Search the relevant gameplay or communication logs.
  4. Check staff/refund/admin-action logs if a correction or penalty was applied.
  5. Compare with runtime logs if a crash, restart or failed service may explain the result.
  6. Record the conclusion and any corrective action through a logged tool.

Use the same timezone when comparing records. Some tables store Unix seconds; some older administrative records use formatted server-local dates. Changing the host timezone can affect how a human reads those formatted values.

ACP action audit ​

The web helper records actor account/name/rank, action type, target type/ID, description, optional reason, client IP/user agent and a timestamp. Current server-side mutations call this helper where implemented.

The helper logs a failure to web output rather than rolling back an otherwise completed action. Therefore a missing audit row is not proof an action did not happen. Investigate logAdminAction failed: errors and database permissions promptly. If you require strict transactional auditing, extend the mutation/audit design accordingly.

Proxy IP information ​

Request metadata depends on trusted proxy headers and host configuration. Restrict direct access to backends and configure the proxy correctly before treating a forwarded IP as evidence. Shared IPs need context.

Retention and backups ​

Logs can contain player communications and identifiers. Set your community’s retention/access policy, protect backups and restrict investigative views to appropriate staff. Database logs and runtime files need separate backup coverage. Test restoration rather than treating the console stream as long-term storage.

Do not publish real log exports, account dumps or production .env files in the source repository or documentation.

Open-source roleplay foundations for open.mp. Bring your own world.