Rules

Etiquette

The primary guideline governing interactions on rEvolution: Don't be a dick.

Be polite and respectful to your fellow players! We're all here to have fun, and we expect our players to treat each other with maturity.

Public Communication

Our game has an R rating; we understand a certain level of violence/language/etc. will come up in the course of scening. On public channels, though, use discretion as to what is and is not going to make others uncomfortable. OOC interaction should be polite!

Consent

rEvolution is a limited consent game. You have control over your character's actions, and can expect to some degree not to have any serious harm come to them without your consent — but always keep in mind ICA = ICC, that is, In Character Actions lead to In Character Consequences. If your character picks a fight with someone, don't be surprised if they get hurt. If they commit a crime, don't be surprised if the cops are looking for them.

The game is focused more on story — character development and plot — than on flashy superpowers and combat. There is no stat system on our game governing combat and skills; in combat situations, we expect players to be responsible and mature about the interactions. Just as you should not powerplay by assuming other character's actions or harming other characters without serious reason or their player's consent, it is also players' responsibility to not use 'consent' as a way to avoid the consequences of their actions. ICCs will happen, and in a disputed situation, the outcome is at moderator discretion.

FCs

Our game values original characters as much as feature characters. In the IC world, characters are equally important, regardless of whether they are canon or original creations. Because Feature Characters are often in high demand among players, and because FCs can change hands over the course of their on-game history, the OOC policies regarding FCs are stricter than those regarding OCs. FCs are limited to two per player and must remain active (see idle policy). Additionally, any serious permanent changes (including, but not limited to, permanent injury and death) to a feature character must have very good reason and be cleared by staff. If staff feels that a player is seriously deviating from the characterization of an FC, the matter will be discussed with the player, and the character may be put back on the FC roster if it continues.

Alts

Currently, each player may have no more than five alternate characters, of which no more than two may be a feature character..

Harassment

rEvolution defines harassment as any unwanted attention that continues after a player has asked for it to stop. This includes but is not limited to paging people who have told you not to, badgering another player for TS, or using any sort of bigoted/abusive language OOCly -- while characters are free to hold whatever IC viewpoints you wish, things like racism, sexism, homophobia, etc. will not be tolerated on this game OOCly from players, ever.

Idling

While we don't expect everyone to be logged on and RPing all the time, characters are expected to remain active.

For the sake of the idle policy, 'activity' is counted as at least one scene in a given week. To count towards activity, a scene must be posted on the wiki. Any character who is idle for a period of four consecutive weeks will receive a notification from the staff (via @mail or, if an email address has been supplied, email) that they are in danger of reaping; if they remain idle for another four consecutive weeks the character may be subject to deletion.

The allowed idle time is half as long for feature characters and adopted NPCs: they will receive notification after two weeks, and be subject to rostering and available for re-application after one month. Players who know they will be gone for an extended period of time should contact staff to prevent reaping.

Style

rEvolution is open to different RP styles, but there are a few guidelines that we’ve found work well for this RP medium.

• Poses should be made in the present tense, third person. (We, you, and I should be kept to dialogue.)
• Try your best to use proper grammar and spelling whenever possible.
• If you are broadcasting telepathy for any reason -- hopefully only when telepaths are actually present -- use << >> to note the thoughts, with a space between the text so that it's easier to post on LJ and other sites.

Note that these are simply guidelines, and not everyone comes from the same RP background.  Be flexible, and talk with the people in your scene if you have wishes one way or another.

Log posting

Unless otherwise discussed before a scene begins, it is assumed that the MUSH is a public place; there is no requirement that players ask permission from others in the scene prior to posting logs. Keeping logs is a great way to keep up with what's going on in the game. While it is not required, we strongly encourage players to submit their logs to the logs section of the wiki.

Player-run Plots

Player-run plots are an exciting and valued component of our game! We encourage players to take their ideas and bring them to life. Players are always welcome to come up with their own events and TPs and run them.

We do ask that if players are going to be running plots, events, or scenes that have far-reaching implications (think, anything that would make the news, affect on-grid locations, or have widespread societal ramifications: i.e., a shooting, destroying a store, inventing new technology) that they clear the idea with staff first before going ahead with it.

If newsworthy events happen in the course of player-run scenes and events, we ask that the player running the plot sends a newspost to the IC News/Gossip board and makes a note in the Current Events section of the wiki, so that everyone can stay up to date with what is going on.

Player Complaints

If any player has complaints that they feel cannot be resolved on their own -- either with another player or with a staff member -- they should contact staff by submitting a post to the Talk To Staff +bboard. Players should include a clear explanation of their problem and, if possible, include logs of what happened.