Prism Griefer / Troll Response Checklist
Prism v4 — quick, step-by-step guide

Checklist for staff responding to grief/troll incidents. Follow: confirm → preview → apply → ban. Replace parameters before pasting into-game.

Tip: keep precise coordinates and timeframes in your incident notes.

0. When you first suspect someone

  1. Teleport or visit the area to gather context.
  2. Run a quick nearby check for recent activity.
/pr near

1. Confirm what this player did

Start small in radius/time; broaden only if necessary.

Small radius (last hour) 
/pr lookup p:<player> r:10 since:1h
Larger search 
/pr lookup p:<player> r:50 since:6h
Example 
/pr lookup p:_Clarth_ r:10 since:1h

2. Lock in the radius + timeframe you want to undo

Use the same values for preview and rollback to avoid surprises.

/pr lookup p:<player> r:100 since:24h

3. Always preview the rollback first

Preview shows what will change — never skip if unsure.

/pr preview-rollback p:<player> r:<radius> since:<time>
Example 
/pr preview-rollback p:<player> r:100 since:24h

4. Apply the rollback when preview looks correct

Apply only after verifying the preview.

/pr preview-apply

Direct rollback (not recommended without preview):

/pr rollback p:<player> r:<radius> since:<time>
Example 
/pr rollback p:<player> r:100 since:24h

5. Ban the player

Use your normal ban commands and include a concise reason like "Griefing". Attach evidence if available.

/ban <player> Griefing - all actions rolled back
/banip <ip> Griefing

6. Quick variants

Last hour, small area

/pr preview-rollback p:<player> r:10 since:1h
/pr preview-apply

Last 24h, large area

/pr preview-rollback p:<player> r:100 since:24h
/pr preview-apply

Double-check afterwards

/pr lookup p:<player> r:100 since:24h
/pr near

Examples (for _Clarth_)

Rollback command
/pr rollback p:_Clarth_ since:1h r:10
Lookup what was done
/pr lookup r:100 p:_Clarth_
Notes
  • Always preview before applying a rollback.
  • If unsure, ask another staff member to confirm.
  • Keep a short incident log: coordinates, timeframe used, and staff involved.

Note: In November 2025 we migrated to Prism after CoreProtect moved to a subscription model. That change made CoreProtect impractical for a small, community-run server with little or no donations, so we chose the open source plugin Prism to provide dependable rollback tools without ongoing licensing fees. Running a Minecraft server is expensive and this decision helps keep the server sustainable while continuing to protect players' builds and the community.