Appearance
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
| Source | Contains | Access |
|---|---|---|
Game log.txt | Runtime messages, startup diagnostics and configured engine output | Host / agent console |
| Player/game log tables | Gameplay events recorded by AddLogEntry and related helpers | ACP player logs and character/account detail |
admin_action_logs | Supported ACP mutations, actor/target/reason and request metadata | ACP Admin Actions |
| Staff/report/refund records | Their dedicated staff workflows | ACP Audit tabs |
| SMS records | Recorded phone message data | ACP SMS view |
| Web process output | Application errors, SMTP failures and audit-write diagnostics | Host service/container logs |
| Database server logs | Connectivity/engine faults and configured SQL diagnostics | Database administration |
Investigate a player issue
- Record the account, character and approximate event time.
- Open the player/character record and establish the correct IDs.
- Search the relevant gameplay or communication logs.
- Check staff/refund/admin-action logs if a correction or penalty was applied.
- Compare with runtime logs if a crash, restart or failed service may explain the result.
- 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.