Philosophy
The positions behind the rules
Rules tell you what is prohibited. This page tells you why, because a community whose standards are only prohibitions will spend all its time arguing about edges.
Text is the medium, not a limitation
A written scene commits a character to what they are doing. Speech, /me actions and /do descriptions make intent visible, which is what allows other players to respond meaningfully instead of guessing.
It also makes administration possible. A dispute reviewed on text has evidence; a dispute reviewed on memory has whoever speaks first.
Characters are not avatars
A character has a job, a routine, debts, people they avoid and a reason to be where they are. Development is the ordinary accumulation of that, not a level that unlocks violence.
When a character dies, that is a story event with limits on what the new version of them can know. Loss is part of the setting, and pretending otherwise makes the setting weightless.
Consent is structural
No player may decide the outcome for another player. You may attempt, describe, and demand. You may not declare that a bullet landed or a person submitted.
The boundaries a member states out of character are respected without negotiation. That is not a courtesy extended at staff discretion; it is a condition of playing here.
Consequence over policing
Most conflict in a roleplay community is not a rule violation, it is a bad scene. The first response is coaching, not punishment. Sanctions are reserved for what coaching cannot fix: bad faith, exploitation, and harm.
Every account-level sanction carries a reason, an attribution and an appeal path. Administration that cannot be examined is not administration, it is authority.
The world is shared property
The economy, the property registry and the vehicle records belong to the whole community, which is why players own parts of them rather than the whole. Value is earned inside the world and moves only through authorised actions.
The website never decides what you own. It asks the server, and it shows you the answer.
Advertise only what exists
We do not run a server we cannot operate, we do not promise a platform we do not have, and we do not publish a roster of staff who have not been appointed.
Development is announced when work is merged. Where a milestone slips, the status page says so rather than quietly redefining the milestone.
Engineering follows the same positions
How those beliefs show up in the platform
A persistent world is an engineering claim as much as a creative one. These are the constraints the software is held to.
Text first
Scenes are written. Local speech, /me actions and /do descriptions carry the story, and the interface exists to get out of the way of the writing.
The world persists
Characters, businesses, property and vehicles outlive a session. What a character did last week is still true this week, including the parts they regret.
Consequences are authored, not scripted
Outcomes come from characters acting on each other. Systems validate what happened; they do not decide what should happen next.
Nothing is decided in the browser
The website presents state and submits intentions. Money, ownership and progression are decided by the server, and no client-side check is ever treated as authorization.
Where this is still undecided
Disagree with a position?
These positions are argued for, not assumed. Where a member makes a better case, the documentation changes and the change is announced.