Investigations & Spectating

Before spectating

1. Review the report and identify the specific behavior alleged.
2. Enable invisibility using /vanish or /v if your role is permitted to use it.
3. Remove visible cosmetic effects or pets only if the relevant staff tools allow it.
4. Teleport using the approved command and maintain enough distance to avoid interfering with gameplay.
5. Start recording before observing so the evidence includes context.

Never use staff tools to gain an unfair gameplay advantage, spy for friends, or gather war/base intelligence unrelated to a legitimate report.

Potential X-Ray indicators

Look for a consistent pattern rather than a single tunnel. Examples may include direct, repeated routes toward valuable ores without a plausible exploration pattern. Review mined-block history with CoreProtect where available. Mining patterns alone are not proof; consider server context and alternative explanations.

Potential combat-cheat indicators

Observe repeated, clearly unnatural behavior such as implausible target switching, consistent hits outside normal reach, or attacks that appear to ignore normal game constraints. Account for latency, server performance, legitimate client features, and recording limitations. Do not punish based on one unclear moment.

Evidence capture

• Keep footage continuous and unedited; 15 seconds minimum, 30 seconds or more preferred.
• Capture enough context to understand the event, including relevant HUD or latency information when available.
• For chat cases, preserve the full context and timestamps.
• Store the original evidence in the private staff evidence channel and link it to the case.
• Do not upload evidence publicly or share private player data beyond the staff members who need it.

CoreProtect investigation

Use only if CoreProtect is installed and your role has permission.

• /co i — toggle inspector; click affected blocks or containers.
• /co lookup u:<user> action:container — inspect container history.
• /co lookup u:<user> action:kill — inspect kill history.
• /co rollback u:<user> t:<time> r:<radius> — rollback a defined area and time range.

Before any rollback: verify the username, time range, radius, and expected impact. If uncertain or the affected area is large, ask an authorized Manager/Developer to review first. Never run a broad rollback just to experiment.

Investigation outcome

Summarize what was reported, what was checked, what evidence supports the conclusion, and what action was taken. If the evidence is inconclusive, document that and escalate or close without an unsupported punishment.