Guides
How we handle common situations. Read one before your first ticket of that kind.
AlexModerator- Online
- 42 / 100
- TPS
- 19.8
- Open tickets
- 2
- My points
- 540
- If you seeInspector says "No block data found at this location"The block was never changed by a player, or it happened before logs were kept (logs are kept for 30 days). → Handling a grief report
- If you seeThe "griefer" is on the claim's trust listTrusted players are allowed to build and take items. That's a falling-out between friends, not grief. → Handling a grief report
- If you see"Outdated client! Please use 1.21.x"The player's Minecraft version is older than the server's. → Common player problems
- If you see"Connection timed out: no further information"The player can't reach the server at all. Usually a typo in the IP, their network, or the server is restarting. → Common player problems
- If you see"Failed to verify username!"Mojang's login servers couldn't confirm the account. Usually a stale launcher session. → Common player problems
- If you see"You don't have Pebble's permission to build here."They're inside someone else's claim. Claims are working as intended. → Common player problems
- If you see"My items disappeared after a lag spike"A rollback or crash lost their last few seconds, or they died and didn't notice. → Common player problems
- If you seeDashboard shows "No access"Your Discord role is missing or was just changed. The dashboard checks it on every page. → When staff tools break
- If you seeDuty minutes aren't going upYou're off duty, or you've been AFK for 15+ minutes. → When staff tools break
- If you seeTicket stuck as "claimed" by someone offlineThey claimed it and logged off without closing or unclaiming. → When staff tools break
- If you seeRed "An internal error occurred" after a commandA plugin threw an error. Not something you did. → When staff tools break
- If you seeRollback undid someone else's buildThe rollback was run without u:<player>, or with too big a radius. → Rollbacks