Server overview
A low-noise view of recent player behavior with direct links to raw evidence.
Collecting recent activity…
What players are doing
Classification is calculated from recent logged actions and does not replace the raw player logs.
Recent activity
Grouped into compact events so block actions do not flood the dashboard.
Alerts requiring attention
Cautious prompts for human or LLM review—not automatic findings.
Active and recent PvP
Timeline underneath.
Where activity is concentrated
Activity feed
Recent actions grouped by player, category, area, and short time window.
Players and evidence
Open a dashboard profile or jump directly to the username-based raw log.
All player log files
Player history by day
Choose a player and review a daily summary generated from the complete retained username log.
Activity dates
Combat Center
PvP incidents with initiator analysis, review flags, health state, result, and raw hit timeline.
Alerts and review signals
Combat flags and activity-pattern alerts, sorted by severity and recency.
Server activity insights
All numbers cover the current in-memory window and reset after a plugin restart.
Classification totals
Recorded event totals
Frequently active areas
Ranks chunks by visits, work, block changes, and combat. Nothing is rendered as a map or written to a database.
Search all logs
Searches player logs, the server log, and completed combat files. All entered terms must appear on the same line.
Readable text logs remain primary
Normal actions stay in logs/players/<username>.log. UUID history stays in logs/players/_uuid-index.csv. PvP incident files stay in logs/combat/.
No database or movement flood
Disk writes use a background writer thread. Dashboard summaries are kept in memory. Movement is used only for chunk-level context and is not written line by line.
Flags are not verdicts
The plugin cannot know voice-chat warnings, permission given elsewhere, or every off-server fact. Alerts point reviewers to evidence.