See what happened.
Across every bot.
Inspect diagnostic reports and line up character activity when a run stalls. Access is private; reports expire after five days.
The plugin does not send diagnostics yet. The receiver accepts only the documented report fields.
Mission diagnostics
Waiting for reports
Shared timeline
0 records| Captured (UTC) | Character | Event | State / reason | Details |
|---|
No reports yet. Sending is not implemented in the plugin; you can read existing local JSONL logs now.
Receiver view shows up to the newest 2,000 matching records from its recent index. Narrow the time range or character to investigate an incident.
What a report contains
Planned sending: a separate Diagnostic plugin build, OFF by default. Each bot sends one initial heartbeat when enabled. Later error or diagnostic-warning reports include up to two minutes of preceding bot state. Debug and Release retain local logging only. This receiver does not enable sending on a plugin.
- Bot identity
- Participating character name, character ID and Leader/Bot role.
- Session & activity
- Plugin version, UTC capture time, random session ID, sequence, mission state/count and Auto/run switches.
- Team grouping
- A random shared group ID links the participating bots in one team/run. Another team/run uses a separate ID. The tester label comes from its send key.
- Movement & holds
- Area ID, coordinates, recruitment/boarding holds and a fixed waiting-reason code.
- Errors
- Fixed error code, exception type and plugin member names. No raw exception message, source filename or personal path.
- Receiver metadata
- Arrival time, record number, report kind and tester label. No client IP is stored in these records.
What is excluded
Chat and tells, passwords and credentials, account information, guest names/rosters, screenshots, personal file paths, unrelated files and complete local logs.
Access & deletion
The viewer key grants reading access. Separate tester keys grant sending access only and can be revoked on Chewypc. HTTPS is required through Caddy for remote access. The receiver removes records after five days, checking every five minutes and on startup. If stopped, overdue records are removed when it next starts. Keys are retained until revoked; deletion of diagnostic records does not remove access keys.
Local-log imports stay in this browser's memory and are never uploaded. Exported records stay wherever you save them; five-day receiver cleanup does not delete exports or original local logs. Internet connections expose the sender's public IP to the server; reverse-proxy logging must also be configured to avoid retaining it.