Built in
Server safeguards
Filtered public text
Chat, signs, books, item names, entity names, team names, portal names, and market text pass through family-friendly moderation checks.
Private reports
Reports are rate-limited, visible only to authorized staff, and tracked through an immutable review timeline.
Protected builds
Claims protect blocks, storage, entities, redstone, fluids, fire, explosions, projectiles, and common automation boundaries.
Immediate control: use /ignore <player> to stop seeing a player's public chat, then use /report if staff review is needed.
Accountable response
How moderation works
- A player submits a private report with a clear reason and optional safe evidence reference.
- Authorized moderators review the report, relevant server records, and context. Reports are not decided by popularity.
- Staff choose a proportionate response such as guidance, warning, mute, kick, restoration, or ban.
- Actions and evidence references are retained in an audit trail. Players can submit a private appeal.
Moderator permission is separated from broad administrator power. Economy changes, item restoration, access actions, and claim administration use explicit permissions and audit records.
Less exposure
Privacy choices
- The game uses authenticated UUIDs as identity; player names are not database keys.
- IP bans use salted keyed hashes rather than storing plaintext IP addresses in the custom moderation database.
- Blocked-text alerts record the matched rule, surface, player UUID, and a content hash rather than repeating the blocked message.
- Account linking is disabled while collision, recovery, and consent policy remain unresolved.
- The future public map must not expose precise live player locations by default. Current staging does not approve public map access.
- This website uses no analytics, ad trackers, account forms, or third-party fonts.
Read the full privacy notice before joining when public access opens.
Play together
Guidance for parents and guardians
- Review the community rules together and explain why personal information stays private.
- Use a child account with an age-appropriate Microsoft account configuration and platform privacy settings.
- Start by playing together. Hard survival includes combat, loss, caves, and online social interaction even in a moderated community.
- Encourage children to disengage, use
/ignore, save useful context, and report privately instead of arguing. - Do not rely on staff as babysitters or emergency services. Maintain your own communication and supervision plan.
What we do not claim
Honest limits
- Family-friendly does not mean risk-free, child-only, or a replacement for parental supervision.
- Automated filters cannot understand every context or language and may both miss and over-block content.
- Staff cannot guarantee immediate response at all hours. Public response-time promises will not be made without measured staffing evidence.
- No parental forced-teleport, child-location tracking, or public live-player map is offered.
- Java and Bedrock use different controls and rendering even though both editions share the same world.
- Voice chat is not part of the PlushSMP feature set.