|-||Marioanius||13m||Hamilton wrote, the other 51!|
|-||Jameson||51s||making the eternal black firmament my side bitch|
|-||Newbs21||14s||We're all crazy here!|
|-||Chrissl1983||2h||Really enjoying this awesome game to the fullest!|
|a||Cerberus||9h||Head Builder & GM when I need to|
|j||Johnny||58m||New Code Written Nightly. Not a GM.|
|And 30 more hiding and/or disguised|
Our programmers are not perfect and some of the code they write will have errors, tracebacks (TBs) and various 'holes' in them. If you discover one of these 'holes' it is your duty to @bug it. It's understood that you won't always know a bug when you see one, but intentional abuse of these 'holes' is against the rules.
When your character finally permanently dies, you are sent to char-gen to make a new character. You are, at that time, a completely new character with absolutely no relation to or memory of the past character. It is against the rules to directly or indirectly pass items or money from an old character to a new one.
Since this is a game, not everyone can win, not everyone can see or do everything. We need to maintain a certain level of intrigue and 'newness' to the game and by finding ways to locations/places you are not supposed to be or doing things which would interrupt the normal IC flow can seriously harm that. Logging on as a guest once you have a character or during character death is not allowed under this rule.
Having more than one character, by any means, is against the rules. Different characters with the same email address are not allowed. Different characters with different email addresses that are played by the same person are not allowed. Having an alt makes it too easy to break Rule 1.C. Additionally, having multiple characters limits the number of players the game can support, which isn't fair to others.
The game is not perfect and due to either code constraints or database constraints, we can not always prevent things that would normally be prevented in the real world. Exploiting these gaps is forbidden. One example of this would be to spam door codes in order to get access to a room or area that your character does not know the access code to, this type of behavior is strictly forbidden. If you have a question or are unsure what this section covers, please ask an admin for clarification before attempting.
Metagaming is the act of crossing IC/OOC lines either passively or actively. For instance, using information you as the player know to benefit (or even hinder) your character is active metagaming as is circumventing IC factors (such as SIC dead zones) via OOC methods. Passive metagaming is the sharing of IC information through OOC means, such as discussing IC events through OOC channels and also altering your character's behaviour towards another character due to your OOC relationship with that character's player.
While foul language is not against the rules, there is a point where too much of it directed at a person (player, admin, guest, or otherwise) becomes a problem. It is understood that IC actions may sometimes result in OOC feelings, but there are healthier ways to vent your frustrations.
Ok, this is really simple... You cannot threaten another player with real world misgivings. This pretty much covers the whole legal gamut. In cases like this, we would be forced to involve outside authorities. If you find yourself wanting to threaten someone, go for a walk, open the blinds, see a movie (something happy, and NO, 'The Matrix' is NOT happy) and rest for a little while.
As this is a game, some amount of sex will, in all likelihood, enter into your character's life or part of it at some point, however, if someone OOCly asks you to stop with the sexual comments, requests, actions, etc, you need to stop. Additionally, sexual conduct in the OOC rooms does not have to be tolerated at all.
Text rape is defined here as any instance in which something explicitly sexual is directly forced on a character. Rape RP is any RP that revolves around an instance of text rape, including the rape itself and any in-character discussions about it.
Rape RP requires the direct, explicit OOC consent of ALL participants, including witnesses. Failure to obtain consent violates this rule.
This means that you should never engage in rape RP, including both perpetration and discussion, in public locations, over SIC, or on the grid, because it's impossible to obtain OOC consent of everyone, including admin, who may witness the RP. If you are involved in rape RP, a player or admin can express non-consent at any time. If this happens, you are required to stop the rape RP immediately.
We really recommend that you avoid this kind of RP altogether. (see also: 'help rape' and rule 2.C. above on "Sexual Harassment")
Making OOC comments about a character or player's race are not tolerated in any way. While IC comments are part of the IC world, if any player objects to a character's comments, they must stop as with any other form of harassment.
Stacking commands so that you shout something 30 times is considered spam. Spam is like noise pollution on the MOO and is not allowed. Granted, our keys do 'sometimes' get stuck, but repeat incidents are bogus.
Administrators are not to be abused, accused or harassed on-MOO or off-MOO firstname.lastname@example.org is for making respectful complaints about personal problems with specific admins or engaging in long-form communication at the request of a specific admin. Bans will be levied against anyone that breaks these rules.
Don't be a dick. Occasionally, a player's dickishness becomes so serious that it impacts the entire game, even if they are avoiding the specifics of other stated rules. If a player cannot de-escalate misbehavior after repeated communications with admins, they will be removed from the game for an extended (and exponential) period of time.
Any action that causes extreme lag or stops/denies other players from connecting due to bandwidth consumption is a denial of service attack. Actions like this will not be tolerated, as they could bring down the whole game.
Each player account has a password for a reason. Using software or guessing someone's password to play under their account is against the rules. If you do forget your password, email email@example.com to get the issue resolved.
When you are bad, you will be punished. When you are punished, you need to comply with that punishment. You are more than welcome to defend yourself before your punishment is issued. After the fact, if you feel you have been treated unfairly, email firstname.lastname@example.org and explain your situation.
Remember from Rule 1.B., character death is final. The name of your dead character is pretty much forever unusable again. Naming your new character like your old one is not allowed. Additionally, the same character history and description are not allowed. If a bug killed your character, email email@example.com to have it looked into. If you have to be away from the game for an extended period of time (6 weeks+), you can ICly put your character in cryogenic stasis and the character will not be removed for inactivity.
Client side triggers or macros are not permitted for any purpose of automating character activities or to provide rapid responses to MOO output. Client side triggers and macros may not be used to allow your character to perform activities in your absence, wether you be AFK or just off window. In-MOO support for both is available (type @macros) and can be used to your benefit while you are present and actively playing the game.
Effective immediately, single action hotkeys (e.g. - that let you press a letter on your keyboard and a whole 'east' or 'west' or 'north' or 'south', etc is input and sent for you) are banned. This includes the mushclient feature where the number pad lets you navigate around.
Due to the way the MOO handles experience, use of any system to keep your character connected to the MOO in your absence is not allowed. Characters are permitted to idle 24 hours before being disconnected from the game. Bypassing this disconnect timer in any way to stay connected in your absence will result in us breaking your connection and preventing auto-reconnection. Your character will remain unmoved after disconnect and you are solely responsible for any IC consequences of where your character ends up 'sleeping'.
xhelp is a means with which players communicate with admin. Sindome is an immersive game and is meant to be played without breaking character. That is not always possible due to bugs, and other circumstances. These cases usually result in a player xhelping to get an admin to help them with their situation. There are only a few acceptable reasons to xhelp:
- Your character is stuck somewhere due to a bug. - You need to report cheating or meta gaming - An admin initiates the conversation - For discussions that involve plot information and info that needs to be private and thereby cannot be sent on the Game-Help channel (changing codes for vehicles, apartments, etc.) and plot approvals. - You are confirming we received a donation There may be one off cases that do not fit these parameters but for 99% of cases you should be asking for help on xgame (which has both players and admin). You should not xhelp to ask ANY of the following:
- A question that should be asked in character (generally these types of questions start with 'where is' 'who is' and 'how do i' - A request for a puppet / animation of an NPC (if you want to talk with an NPC (non player character) then please -talk- to them. If an admin is available they will pick up the puppet. You are free to repeat your query to the NPC every 5-10 minutes if you do not get a response. When an admin is available they will help you. If you still cannot get ahold of the NPC then @request-puppet and/or leave an @note about it. - Complaining because something does not go your way - Questioning of how an NPC/PC knew something, found you, did something - Complaining that an NPC is not being animated fast enough
Stacking commands in the lines of disarm/flee/pickpocket etc, is not allowed on the MOO. In reality you could only attempt these actions once every few seconds. Players should not and will not be permitted to proceed with this type of actions. Repetitive and unnecessary stacking causes lag, and no one wants that.
In the world of Sindome death is a daily occurrence and with this players are allowed to breath life into this portion of Sindome life. When players start controlling the population of Sindome by killing everyone and everything that they see then their version of population control becomes negative to the MOO. In this situation some players might find that they have just been eliminated by a crack JUDGE team without notice. Please feel free to kill those that your character would have a reason to, but ensure that when you terminate their life force you do it with flare and with a touch of reality.
NPCs that run stores for players, while they are out and about, tend not to be the greatest thief catchers. If players insist on continuously 'lifting' items from stores, they should keep in mind that the Judges will start full-scale operations to apprehend suspects. This will lead to massive character searches on the streets. When players are caught with stolen items that have been reported their characters will be judged and sentence will be passed on the spot. Other kinds of theft will be treated the same.
$support_GM (Support GM) - Checks Grid Mails, Basic Puppeting
$watcher (Training GM) - Training, Most Puppeting
$creator (GM, Builder) - GM, building, basic coding
$agent (Senior Staff) - Staff / Player Management
$justice (Executive Staff) - Senior Management
Conversations between players and administration made over xhelp or email are considered private between player and the administration as a whole, unless otherwise specified.
In instances of players reporting potential admin issues, the conversation will be kept in the strictest of confidence and will only be discussed with the necessary parties involved. All administrators are OOC entities. They do not converse with players in an IC manner, obviously, and cannot pass information on to another player except in an OOC manner. Passing such information along is breaking rule 1.C., above.
The game is based around conflict, without which we would be left with a happy fluffy bunny moo. This conflict may not always be resolvable through IC means. When an administrator steps in to resolve these conflicts, they must be fair and impartial at all times. If an administrator cannot handle the situation due to OOC association, they should give the conflict to another administrator to be handled.
Without the administration, the game wouldn't last too long. Administrators are expected to login on a regular basis. If an administrator cannot login due to real world issues, they should let a $justice know so they are not removed for not logging in. After 6 months of inactivity, administrators will be reaped. $Justices are excluded.
Upon returning to the game after an extended absence all admin are required to read, review, and absorb along with abide all the rules, goals, and statements made in the admin-guide located on the website in the admin section. Ask another admin if you are unaware of the URL.
Failure to read and abide by the rules will result in an admin being stripped of their bit by senior staff, regardless of the returning admin's previous place in the game. This is due to the fact that the game evolves and if you aren't around to evolve with it you may come back with a vastly different idea about the way the game is played or administrated due to not being around for the major changes. It is your responsibility to not undermine the current staff or direction of the game. Failure to do so results suspension of you as an admin.
Giving help, money, stat boosts, gear, or information to a friend or your alternate character is considered cheating. Involving a friend in an approved plot where gear, money, help or information is issued is OK but must be RP'ed. The characters created for these plots fall under the same guidelines as any other character.
No administrator shall answer questions or make statements for the game unless directed to by Johnny. General statements about personal enjoyment, theme or features are fine as long as they are not too in-depth.
At no time will source code from the game be displayed to players, guests, or extra-MOO entities. No code will be ported, dumped or used from a non-Sindome author without approval from that author, and a $justice. If an author cannot be contacted, and it is uncertain if the code is public domain, it is not to be used. No code will be ported, dumped, or used from Sindome, without the express consent of the Author and $justice. Any code written for Sindome, is considered property of The Sindome Corporation. If at any time a coder has decided to leave, his code stays with Sindome. He may use his own code elsewhere, but Sindome is free to do what they will with what was left. If at anytime an administrator is asked to leave/@toaded, they may ask that any plots/creations that they have made to be removed from the game. The admin will make an effort to accommodate them, but have no requirement to do so.
Any $justice may @newt a player or administrator for a period of up to 21 days with proper documentation. @newt is limited to 48 hours without documentation. Any other revocation of login rights, to include @newt over 21 days, @toad and any 'listing' requires the consent of 2 or more senior staff, one of which must be arch-justice, Johnny. If the arch-justice is unavailable for a period of 2 weeks, Fengshui shall be the supernumerary.
Players will be automatically reaped after 90 days of inactivity. If a player is going to be absent longer, then they should use the IC cryostasis explained in 4.B.
Any code that is intended to subvert the permissions assigned to you, monitor another administrator of equal or higher level, or harm the game by means of excessive lag, server panics, database bloating or any other malicious nature is grounds for permanent blacklisting by 2 $justices without consent of an arch-justice. This does not include accidental runaway verbs or crashes, unless the verb was designed to subvert security or permissions assigned to the administrators.