What is not acceptable
Harassment, hate content, threats, stalking, doxxing, sexual exploitation, scam behavior, and coordinated dogpiling are not welcome here.
- No real-world threats.
- No hate or slur content.
- No exposure of private information.
How we keep the city usable
Community Standards
This page sets the baseline for harassment, exploitation, scams, roleplay boundaries, AI misuse, staff respect, and how enforcement works when someone drifts outside that line.
🤝
Respect is requiredPlayers do not get to hide real abuse behind roleplay or platform distance.
required 🎭
Roleplay still has boundariesScenes can be intense without turning into harassment, coercion, or hate behavior.
enforced 🧠
AI misuse countsTrying to trick LISA or connected tools into exposing protected information is treated as misuse.
logged Respect is required requiredRoleplay still has boundaries enforcedAI misuse counts loggedRespect is required requiredRoleplay still has boundaries enforcedAI misuse counts logged
💬 Respect and safety
The community is meant to feel premium, serious, and alive. That falls apart fast if people normalize contempt, baiting, or dehumanizing behavior.
How to behave in shared spaces
Discord channels, support lanes, stream spaces, public city feeds, and shared scenes should feel usable to the broader community, not dominated by the loudest person in the room.
- Do not bait other players into breaking tone.
- Keep public spaces readable and purposeful.
- Treat staff and community tools like shared infrastructure.
🎬 Roleplay boundaries
Serious roleplay does not mean anything goes. The point is to create strong scenes, not to justify cruelty or ruin the experience for everyone else.
Scene boundaries
Scenes can include danger, crime, enforcement, and conflict, but they still need consent-aware pacing and a respect for the human being on the other side of the screen.
- No harassment disguised as RP.
- No forcing scenes that break community safety rules.
- No using OOC pressure to win IC outcomes.
Economy and bug abuse
Exploit-driven wins damage the whole city and will be treated as abuse even if they looked clever in the moment.
- No duplication or hidden exploit use.
- No abusing economy bugs.
- No manipulating systems you know are broken for gain.
📡 How to use tools and automation
The connected tool stack is there to make the city stronger, not to give people new ways to annoy, expose, or game each other.
LISA and Syntra misuse
Do not try to prompt, trick, overload, or social-engineer connected tools into revealing restricted information or bypassing process.
- No privacy-boundary probing.
- No automation spam.
- No using AI to fake staff authority.
Support and reporting lanes
Use the correct channel for reports, support, and disputes instead of turning every issue into a public performance.
- Use ticket or review flow where offered.
- Do not spam duplicate requests.
- Do not weaponize public channels during a review.
🧯 How enforcement works
Standards only matter if enforcement is real. Staff can step in, limit access, reverse outcomes, or remove people when the health of the ecosystem requires it.
Possible responses
Warnings, removals, feature restrictions, city corrections, bans, role removal, or account action may all be used depending on severity and history.
- Severity matters.
- Pattern matters.
- Safety matters more than convenience.
Review and appeals
Some actions can be reviewed through structured appeal paths. A review does not mean the original action was wrong or that reversal is automatic.
- Use the official review door.
- Bring facts, not heat.
- Respect final decisions where no further appeal exists.
References
This page follows the source references captured in the Prozilli Website Legal Manual and updates as the operating systems behind the city grow.