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.
Woodland Cats remains optional. A player who does not create a fictional cat profile keeps normal survival unchanged. Its roleplay chat requires explicit opt-in to send and receive, remains public rather than private, and uses the normal family filter, ignore choices, moderation, and rate controls. Fictional cat names, biographies, clan descriptions, and relationship notes must not contain real personal information. Read the Woodland Cats guide.
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
- Account identifiers support persistent gameplay without making private identifiers public.
- Public map features do not expose precise live player locations by default.
- Optional roleplay profiles should never contain real personal information.
- This website uses no analytics, ad trackers, or third-party fonts.
Read the full privacy notice before joining.
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 crossplay are available now.
- Voice chat is not part of the PlushSMP feature set.
plushsmp.com using Java port 25565 or Bedrock UDP port 19132.