Policy/Rules: Difference between revisions

From Citadel Station RP Wiki
mNo edit summary
No edit summary
 
(53 intermediate revisions by 2 users not shown)
Line 1: Line 1:
These Rules are for use on the '''Roleplay Server''' ''alone'' and ''not at all'' applicable to the Main Server. Specific changes to each rule have been inserted below, either as an additional segment or as an overriding change.
{{Header - Administration}}
[[Category:Administration]]
{{STD_TITLE|The Rules}}
{{TOC_RIGHT}}


==Server Caveats==
<span id="important"></span>
#You must be 18 years or older.
== Important ==
#You must be able to read and write English with a level of comprehension meeting the US Grade 11-12 standard.
#Repeatedly coming close to breaking a rule (i.e., "toeing the line") will be counted as breaking the rule.
#Repeatedly breaking the same rules will accrue harsher punishments.
#All examples are just that and are not an exact list of what is and is not allowable.
#Don't be a dick.
#To gain access to the server, use the #station-access-request channel on the Discord.


==Citadel Station RP Rules==
These rules are enforced in addition to <b>[[Global Rules/Community Guidelines|Global Policy]]</b>. Read both, please. While global policy refers to general community guidelines, these are the actual rules for the server. As such, we will try to keep this relatively simple.


===Rule 1: Do Not Grief===
== Summary ==
Griefing is deliberately irritating or angering another player using aspects of the game in unintended ways.


#Don’t spam emotes, in-character speech, OOC text, or anything else.
# '''Keep IC / OOC separate''', adhere to minimal standards for IC chatter. Do not talk about the events of an ongoing round in OOC channels (discord, OOC verb, voice calls, etc) until it ends.  
#Do not kill or attack people randomly or indiscriminately. If you have a reason to attack or murder someone, have a strong justification for it.
# '''Stay in character.''' Try not to break character to 'win'. You should not be entirely unafraid of all death / pain / discomfort.
#Do not exploit bugs. Report all bugs on the Github.
# '''Make a well-rounded character.''' Your character should have pseudo-realistic limitations on what they are skilled at. Do not make Mary Sue's. Being a troublemaker is allowed as long as it is believable and not straying into the territory of griefing.
#Do not intentionally cause damage to the station, machines, or other structures/objects for no reason.
# '''Rounds are canon, with caveats'''; remembering prior rounds is fine, instigating is not. Avoid giving your friends unreasonable boons in IC without an in character reason to do so.
#Do not harass another player out of character. In-character harassment is subject to admin intervention if it becomes overbearing.
# '''Escalate conflicts reasonably'''. Consider what a conflict will do to your character / another's character; have justifiable and proportional IC reason if causing collateral damage or when inflicting mortal wounds.
#End of round grief (AKA, EORG; i.e., griefing at the end of a round in the time after the shuttle has arrived at CentCom) is not allowed on the RP server.
# '''Avoid wordless ganking''', even as an antagonist. An 'antagonist' is someone given a pass to otherwise ignore certain administrative precedents (e.g. making a believable and hire-able character); you are still here to portray a character and tell a tale.
'''Examples:'''<br>
# '''Do not exploit OOC factors for an advantage.''' Do not abuse bugs. Do not multikey (log on with two different accounts for the same round). Do not intentionally abuse OOC factors to ruin someone's day (waiting for someone to go AFK and then ganking them, type-baiting, etc).  
''Unacceptable:''
# '''Punishments may be IC or OOC.''' You open yourself to IC but not OOC punishments by crew / admins acting as higher authorities if you cause trouble IC but not break OOC rules on roleplaying.
*Spamming the *deathgasp emote.
# '''Staff are still players.''' Staff characters get no special treatment.
*Killing another player for walking through your work area.
# '''Adminhelp if you have a grievance or question.''' Do not lie in admin tickets. Do not attempt to enforce OOC rules via IC other than in cases of clear griefing. Do not assume that someone else getting away with something means it is allowed/not enforced - always ask if you have a question.
*Using a bug to gain an item you shouldn't have access to.
# '''Erotic content must be consented to by all parties.''' Erotic content receives grief protections but no world / IC protections. Keep extreme content off the server and do not go out of your way to harass people in regards to this content whether for or against.
*Destroying all the lights on the station simply because you wanted to.
*Berating another player in OOC for something that happened IC.
''Acceptable:''
*Breaking open a window to save a dying player.
*Getting into an argument that evolves into a brawl that evolves into a fight with weapons that ends in death.


===Rule 2: Listen To The Admins===
<span id="elastic-clause"></span>
Admins always have the final say during a round. If you have a problem with an admin's decision, you may discuss it after the round in the #admin-forum Discord channel or you may make a formal complaint on the forum.
== Elastic Clause ==


#If you are ever unsure whether you should do something, a-help and ask before doing it.
Citadel RP is a roleplay-oriented server. No ruleset will possibly cover all cases, and as general as our rules are, there are cases that fall outside of them still. As such, administrators may intervene in rounds and grievances as they see fit.
#Be polite and to the point when sending an admin PM; give admins all relevant information that you can.
#Do not antagonize someone you are a-helping about as it will only complicate the situation.
#If an admin tells you not to do something, don't do it. Arguing with an admin during a round about the nature, absence, or applicability of a rule during a round is not allowed. If you feel you have been wronged, take it up in the admin-forum or make a complaint after the round is over.
#Do not lie to admins in official channels. Doing so will result in your ban being increased or a ban being applied regardless of any other fault.
#If you have an issue with a player, bring it up to administration. If you have an issue with administration, bring it up to a player representative or head admin. If you have an issue with a ban or note that isn't yours, you may attempt to bring up the topic to an admin in private, but all appeals must be done by the original player. Do not complain about any of your issues in non-specified channels.
'''Additional Information:'''
*When you a-help about anything you should include where it's happening, what's happening, who's involved, and why you think that it's an issue.
*If someone is antagonizing you while you're a-helping about them, your best option is to do your best to get away from them and inform the admin handling your ticket. If you can't, try not to retaliate; if administrative action is taken against a player, the admin may be able to reverse any damage done. Do this to avoid coming into trouble yourself.
*If an admin tells you that something is IC/valid/etc, that is the final answer. Admins are not obligated to give you more information than they think is necessary during an ongoing round. If you want more information you may ask again after the round, or you may ask for the logs.


===Rule 3: Stay In-Character===
Obviously, staff that choose to invoke this clause are held responsible for their actions.
Your character and actions must fit into the canon of the server; the canon of the server is defined as a research station in deep space with the goal of mining and researching the effects and uses of plasma. You are a member of the crew of this station, being either a human, a human-hybrid (aka furry/anthromorph), or an alien species (e.g., Plasmaman, Tajaran, etc).


#Speak normally. Don’t spam, yell constantly, or use netspeak, emotes, etc. in speech (excepting special circumstances like braindamage).
These rules are worded for a roleplaying environment. We, however, are roleplaying in Space Station 13. We are not here to take all the fun out of the game; reasonable amounts of ‘fun’ will be tolerated, for the game would become not much more than a job simulator without it.
#Your character's name must be fully spelled and capitalized and may not contain titles.
#Do not impersonate staff or other player characters.
#As a member of the crew, you should maintain the professionalism, work ethic, and probable training you would expect to have in a real setting.
#Reference characters are only allowed as just that: a reference. Do not attempt to recreate a character from either a real person or a fictional character. Your character may be similar or have allusions to the other person/character, but do not attempt to actually be that person/character in the SS13 setting.
#Do not intentionally commit suicide to avoid IC punishment or for "an hero" moments (e.g., killing yourself in the permabrig/offing yourself after making a long, drawn-out play about how you're gonna off yourself because you're sad). Doing so will result in either a server ban or identity ban.
#Underage characters are strictly verboten. The lower limit for character age is hard-coded at 18 for a reason. Attempting to circumvent this using flavortext or by describing your character as "looking younger than 18" is disallowed.
#Do no pick disabilities that interfere with your ability to do your job (e.g., a blind chef, mute security officer, or deaf engineer).
#Characters can not posses ties to either Central Command or the Syndicate in their back stories.
'''Additional Information:'''
*When you’re creating your character, it ultimately must fall into the canon of an NT crewmember. This means that your character must be believable. NT crewmen do not have special powers (unless they receive abilities on the station from genetics, research, antagonists, etc.), they are not super-powerful beings that are supernatural or otherwise, and they would not be former enemies of the station.
*Antagonist status does not give you license to define your character however you see fit. They still must fit into the current role. Traitors, revs, cults, and similar antags still need to appear to be an NT employee. Wizards and the like should reflect their current powers and abilities, but their “fluff” can be more open to interpretation.
*NT would not hire incompetent or mentally ill crew members; at least not in serious jobs (roles like cook, janitor, etc are more believable for someone who is “special”). The station is a workplace, and people who constantly act like children would be quickly expelled. When in doubt, act as you would at your own workplace.
Murder is only justifiable as long as it was properly escalated. You can’t go from a single rude punch to a knife in the neck. You can, however, go from a single punch to a counter punch to a brawl to using weapons, and so on. Other IC justifications may exist for murder, but these are on a case by case basis. Minor aggravations like demotions, pranks, insults, or thefts are not adequate justification.
*When picking your name, it must be spelled fully with capitals and no shortenings (e.g. NOT J Hoffman or jaiden mallow). Exceptions to this are one-word nicknames, "Eats-The-Lemons" format of Lizard names, Clown, Mime, Silicon, Wizard and Nuke Op names.
'''Examples:'''<br>
''Unacceptable:''
*"lol, i c u there :)"
*Playing as Donald Trump, 45th president of the United States.
*Playing as Gordon Freeman, a silent scientist from Black Mesa.
''Acceptable:''
*Playing as Tonald Drump, a blonde, orange skinned captain obsessed with building walls.
*Playing as Gerald Fieldman, a mute scientist who really wants that red crowbar.


===Rule 4: Fullfil Your Role===
We’re all here to have fun, not fight and argue with assholes. Don’t intentionally ruin the game for everyone else on an OOC level, and use common sense. More times than not, we care more about what you are doing than what rule you broke. Acting in good faith can excuse a lot of missteps, while intentionally making others miserable will be punished regardless of rules being broken verbatim.
All head roles, antag roles, and to some extent all jobs in Science, Medical, Engineering, Supply, and Security require a minimum amount of effort. Failing to put in that effort will negatively impact the round for everyone playing. Before you do anything else, you should insure that all of the responsibilities of your department are being accomplished.


#If you have a job in an important department, you should regularly check in to make sure that any tasks assigned to your department are accomplished. If no one is able to do them, it's your turn.
<span id="immersion"></span>
#If you are a part of the command staff, your round should be spent ensuring that all of the jobs that your department is responsible for are accomplished. Delegate where you need to, keep track of your staff, and do yourself what your staff can't take care of.
== Immersion ==
#Solo antags (e.g., traitors, changelings, etc) are expected to at least try to do their objectives; actively working against your objectives is not allowed. Team antags (e.g., cultists, nuke ops, etc) are bound to their objectives and team and must accomplish them to the best of their ability.
#If you take a role that is not considered to be important to the round like cook or janitor, you still have a job to accomplish and should do it. If you don't want to do that job (or you'd rather just be an assistant) get yourself reassigned.
#Locking yourself in part of a department to do some minor task (e.g., virology or paperwork) while ignoring more important and time-sensitive jobs (e.g., healing/cloning in medical, stopping threats to the station as security, etc) counts as not fulfilling your task.
'''Additional Information:'''
*If you never want to be in a specific role, ask to be job-banned. Failing to do your job because you didn't want it is not an excuse.
*If you do not want to be an antagonist, a-help and ask to have the role removed so that it can be given to someone else.
*Admins will not change your job for you; that's what the Head of Personnel is for. If there is no HoP (or captain), tough it out for the round.
*If you leave your department, be sure to keep your radio on to stay aware of anything that comes up.
'''Examples:'''<br>
''Unacceptable:''
*Sitting in the security office all round to chat with another officer while ignoring calls for help on the radio.
*Sitting in virology while ignoring calls from fellow crew-members for medical attention.
''Acceptable:''
*Hanging out at the bar as an engineer, and leaving to repair any damage reported on the radio.


===Rule 5: Do Not Metagame===
* '''Keep IC and OOC separate.''' If there is an issue, contact staff. Breaking the fourth wall to get even with something is not okay.
Metagaming in regards to SS13 means using any information that you might acquire from sources outside of your in-character means. This includes any out of character patterns (e.g., characters who often roll antag, the round type, etc), third-party communications (e.g., IM over Discord, VOIP, etc), or preemptive preparation without knowing there is a threat.
* '''Netspeak:''' Adhere to minimal standards for IC chatter; do not use “netspeak” e.g. emojis, “lol”, “wtf”, “4head” in IC chat. Language, after all, is spoken.
** IC text messaging like PDA/communicators is exempt from this.
** Semantically digital languages like the AI/cyborg binary channel, and EAL are exempt from this. Other players, however, can and will make fun of you if you choose to talk like this.
* '''Metacommunications:''' Do not share round information in OOC manners of communication. This is unfair to everyone else playing in the round.
* '''External Information:''' Do not use round information gained from OOC communications in round unless explicitly stated to by staff.
** Do not use information from adminhelps IC unless told otherwise. We do’nt want to have to tip toe to not “leak” round information to you; please don’t ruin it for everyone.
* '''Deadchat:''' Deadchat is considered OOC.
* '''(L)OOC:''' In game OOC channels are generally for clearing up OOC/mechanical confusion, e.g. having to afk for a moment, typos, misclicks, etc.
** They are not for arguing about an IC case. Security can and should disregard someone claiming innocence in LOOC, as an example. If there’s a major issue, you/they can adminhelp. Abuse of the channel will result in a mute.
** For urgent issues, using ((Hey this is a heads up.)) double parentheses notation is an acceptable thing to do in say/me/IC channels.
* '''Do not use AI-generated text content in game'''. Reference images in your flavortext is fine. Writing your flavortext or RPing with LLM's or similar AI generators in game is not. ''As a rule of thumb, if we can tell it's AI, it's probably too AI for a RP community.''


#Keep in-character information out of OOC and vice-versa.
<span id="roleplay"></span>
#Do not use third-party IM or voice programs to communicate with someone about in-game information.
== Roleplay ==
#Do not multi-log/multi-key; i.e., playing on the server with two (or more) accounts.
#Do not meta-grudge; i.e., attacking or griefing another player for an infraction from a previous round or because of a personal vendetta.
#When your character dies and is cloned, you are allowed to remember everything up until the point you black out.
#Do not intentionally kill yourself (e.g., by running out of an airlock) to circumvent the restrictions placed on ghost roles for suicide. If you wish to play ghost roles, it is far easier to simply observe.
#All antagonists are non-canon, and therefor information regarding them is not retained across rounds. Outside of using the [[Identifying Antagonists Guide]], you must learn it ICly before acting on the information.
#Do not abuse the respawn system. Using it to get back at players by switching roles or jobs, or using it as a respawn when your character is clearly taken out of the round and not going to be cloned during the round is not allowed.
'''Additional Information:'''
*Characters may know about any in-game mechanics; learning how to do a job from a guide is not metagaming.
*Characters may know about antagonists and what their objectives might be, but may not preemptively prepare for them or attempt to prevent their accomplishment.
*Characters may know what antagonist equipment is and what it does, but may not preemptively search for it without prior knowledge of an antagonist being present.
'''Examples:'''<br>
''Unacceptable:''
*Hiding grand theft objective items because you know it's a secret round.
*Searching someone for antagonist items without a clear or justifiable reason to search them.
''Acceptable:''
*Knowing how to do a task that's technically outside your department's job description.


===Rule 6: Do Not Powergame===
* '''Stay in character:''' Try to stay in character at all times. Don’t do ridiculous things that your character wouldn’t.
Powergaming in SS13 is acquiring items, powers, increased levels of access, and other assets for the sake accruing as much power as possible, with little or no other motive. It is also a style of play in which one min/maxes their character or environment to complete an objective, to the exclusion of other elements such as roleplay and the mutual entertainment of other players.
** Light amounts of messing about is allowed and encouraged, as we are still a video game. Just because your character is here to work doesn’t mean they can’t have a little fun while doing it. We’re not here to roleplay rigid military rank, and your character isn’t a robot.
* '''On powergaming:''' Powergaming is defined, loosely, as ‘playing to win’. If you are trying to complete round objectives, kill the antagonists, or ‘win’, at all costs with no regards to roleplaying, you may be better off somewhere else. This ''may'' include but is not limited to:
** Having your character unafraid of any and all death or pain and resistant to any torture
** Having your character always willing to battle alone against a crowd of opponents
** Rushing gun wielders unarmed with no regards to your own preservation
** Having guns, medicine, and other powerful items every round with no real IC reason to do so
* '''On character knowledge:''' Departmental knowledge is outlined in “Characters”. This more refers to general guidelines; keep in mind what your character does/doesn’t know. The average spacer probably doesn’t know where to find, say, an agent’s uplink, or have exact coordinates of specific pieces of loot memorized to teleport at a whim.
* '''On cloning/revival:''' Cloning and revival technologies are in flux on the server out of necessity. Death and pain should not be ignored due to their presence; they are only so lax ''at current time'' for the benefit of our community and culture.
* '''On Leaving the Round:''' While it's unreasonable to try to force people to play what they don't want to play, please avoid leaving the round to dodge IC punishment for your character's actions. It's not fair to the other people who went out of their way to handle whatever you did.
** Avoid ghosting out of your character unless absolutely necessary. There's already systems in place to allow you to leave the round properly.
** While we do not mechanically restrict leaving and coming back on the same character, it should not be used to do things like swap jobs, heal yourself, and similar IC actions. Please see [[Policy/Administration|Administrative Precedents]] for more information.


#Don't steal ID cards or upgrade your access just for the sake of having more access alone; if you need to do this, have a good reason to.
<span id="characters"></span>
#Don't steal items from another department for your own convenience or to inconvenience them, especially important items for that department.
== Characters ==
#Be conservative when giving players outside of your department powerful items or abilities. Provide them to those who need it, and deny them to those who would pose a potential risk.
#Don't take over the job(s) of another department when they are fully able and willing to do it themselves.
#Security are not allowed to preemptively prepare for antagonists before any antagonists are identified.
#After an arrest, Security should return confiscated equipment either to it's rightful department (e.g., return an RCD to engineering), or put all contraband in the contraband locker (e.g., a Stechkin). The HoS/Warden may assign confiscated gear to security personnel during a heightened level of threat (like traitors or meteors) or during an emergency (like a blob or cult/revolutionaries).
#Limit what you know in character. It's reasonable for a character to have skills outside their occupation; it's not reasonable for a character to be well versed in multiple high level or difficult fields. (e.g., being able to set up the reactor and perform surgery)
#Do not use size gun for a combat advantage. This is specifically referring to shrinking people to be able to kill them faster than the game regularly allows.
'''Additional Information:'''
*In the event of a station-wide emergency, most of the parts of this rule can be disregarded (within reason). The line between what counts as an emergency and what doesn't is not explicitly definable; but, one can assume that if the lives of all or most of the crew are at stake, or if the station itself is at risk of total destruction, it can be counted as an emergency.
*There are always acceptable exemptions to this rule; remember however that they are just that, an exemption, and not the norm.
*It is acceptable to use contraband to protect your life, but looting and using contraband as a regular crewmember or security is considered powergaming; do so at your own risk.
'''Examples:'''<br>
''Unacceptable:''
*Stealing the Captain’s spare ID because there are no heads and you want to be Captain.
*Taking as many weapons and powers as possible because "there might be an antagonist on the station and you want to be ready for them”.
*Breaking into chemistry to make yourself a bunch of chemicals because “there’s no chemist around”.


===Rule 7: Do Not Validhunt===
* '''Make well rounded characters:''' Your characters should have strengths and weaknesses. Take what species you’re playing as into consideration. Avoid “Mary Sue”s, aka characters that are inexplicably/unreasonably perfect at everything with no flaws.
A "valid" is someone who is allowed to be killed under the rules, typically on the grounds of being an exposed antagonist. "Validhunting" is the act of going out of the way to seek out and/or kill a "valid", regardless of other responsibilities to the station or level of authority (or lack thereof).
* '''Keep your ''characters'' separate:''' It is unfair to others if you were allowed to play a whole “cast” of characters fit for everything, and share knowledge/grudges amongst themselves in an attempt to bypass our rules on escalation/grudges/knowledge. Here are some examples;
** Playing siblings is okay.
** Playing characters who know each other is okay.
** Leaving mid-round to bring in another character to handle a situation in your character's favor by overruling conflicts is not okay; an example of such is joining as a security character to clear another one of your character's name.
*** Switching characters to respond to an ongoing crisis, such as swapping from a medical character to an engineer character to handle a Code Orange, is allowed.
** Having all of your characters automatically grant someone favors, or grudge someone as a group is '''not okay''', and will usually be considered as '''metagrudging'''.
* '''(Departmental) Knowledge:''' Keep knowledge reasonable. A twenty-five year old wouldn’t be some genius with multiple PhDs. Many things are harder to do in character than they actually are to do in the game, e.g. things like surgery isn’t ICly clicking a button ten times. Avoid characters that know everything.
** This is usually relaxed and not overly enforced when there’s not a lot of people around. We don’t want skeleton crew hours to be unplayable.
** While many species exist that can live well past normal human lifespans, we still require those characters adhere to reasonable knowledge guidelines; No 'my character is 300 years old' perfect do-it-alls.
** As rounds are canon, characters should not be a permanent Head of Staff for more than one department at a time. Swaps are possible, but should be done in a reasonable manner.
** For the purposes of these rulings, the '''Captain/Facility Director''' and the '''Head of Personnel''' are in the same department: Command. Playing both frequently is allowed.
** The general guideline is that a character should have at most ''proficiency'' in two unrelated fields. Most people wouldn’t be heads of multiple departments, or able to do every job on the station.
* '''Miscreants, troublemakers, and criminals:''' Characters with “unfavorable” (from the PoV of authority) backstories are allowed and encouraged. Getting caught IC still incurs penalties as always.
** You still need to get hired. Your employer wouldn’t hire someone who wouldn’t be able/willing to work. No “my character is insane” antics.
** Backstory cannot justify escalation alone. No characters that attack security for the fun of it, or “evil” characters that join to break things.
* '''Flavor Text:''' Your flavortext represents what can be visually observed by looking at your character. Try not to dump backstory, and keep it (relatively) reasonable.
* '''On backstory and species:''' Character customization and creativity is one of our environment’s features. You may design custom species/genemodded characters with unique planets/backstory within reason. Some specific caveats are as follows;
** '''Major species''' already have lore. No going against what the agreed upon narrative is; adding to it in ''reasonable'' manners (like saying there’s some outpost somewhere that you came from, etc.) is usually allowed.
** '''Whitelisted species''' have specific requirements for lore. Make sure you’re in adherence with them.
** '''Custom species''' may either be 1. a genetic modification of a major species 2. a minor race of your own creation with no more than a few systems. The galaxy’s major species are already set; there won’t be any Mary Sue races popping up out of nowhere without prior agreement.
** '''Lore submissions:''' We encourage lore submissions if you wish to expand upon our universe. This is one way to “canonize” your minor race.
** '''On Important Characters:''' Characters integral to the lore, e.g. leaders of major species factions, CCOs, any kind of royalty, and generally any in-universe celebrity would find little reason to be working on the station. They may not be used as 'daily driver' characters.
** '''Heads of Staff:''' Heads of Staff must have written and complete security / medical / employment records.
* '''Naming policy:''' We are very lax on naming policy. Here are some general guidelines;
** It is recommended to stick to your species’s standard naming style (firstname lastname for humans, etc). Try to have a reason if you choose otherwise.
** Character names '''may not''' contain nicknames. (e.g. Jason “Jay” Brooks)
** Character names '''may not''' contain hierarchal, gender-based, or job related titles, like Duke, Lord, Dr., Mr., Capt., etc.
** Try to initial middle names. (Kara Mary Snyder --> Kara M. Snyder)
** '''Human''' names '''may not''' be a mononame. (e.g. “Jack”).
** Clowns, mimes, theatrical roles, and gimmicky event roles are usually exempt from naming policy. Keep it tasteful.
** You '''may not''' name your character after real life celebrities, politicians, or other famous person(s) from popular culture/video games.
** Avoid cartoony names like Firstname ColorFur and similar; it breaks suspension of disbelief.  


#Do not abandon your job to search out, hunt for, or attack antagonists unless it is related to your department's field of work, or unless you or nearby crew-members are under a direct and immediate threat from an antagonist.
<span id="continuity"></span>
#Do not forcibly inject or force-feed a member of the crew something which will reveal their antagonist status without a credible in-character reason for doing so.
== Continuity ==
#Random searches are only allowed by security and heads, and only for a credible in-character reason.
'''Additional Information:'''
*In the event of a station-wide emergency, most of the parts of this rule can be disregarded (within reason). The line between what counts as an emergency and what doesn't is not explicitly definable; but, one can assume that if the lives of all or most of the crew are at stake, or if the station itself is at risk of total destruction, it can be counted as an emergency.
*The line between validhunting and defending yourself can be grey, but a general rule of thumb is that if it's not your job to directly confront an antagonist, your goal should be to survive and escape, not to try to kill or subdue them.
'''Examples:'''<br>
''Unacceptable:''
*Leaving your job in chemistry to go hunt someone that you suspect is a traitor, but have no evidence for it.
*Forcibly injecting someone with a mind-shield implant to see if they're a revolutionary or gangster because nothing has happened all round and you're bored.
''Acceptable:''
*Defending the R&D department from an attacking wizard with your mech as a roboticist.
*Searching an assistant who was lurking in maintenance on blue alert as a security officer.
*Force-feeding holy water to someone who you suspect is a cultist when it's been confirmed that there is an active cult on the station.


===Rule 8: No Self-Antagging===
'''This is a section undergoing trial.''' Continuity is hard to get right, and we may adjust this as necessary. Keep it tasteful and avoid going out of your way to ruin somebody’s day.
Self-antagging is performing the actions of, or acting as if you are, an antagonist when your role is not set as such.


#Murder, attempted murder, mutiny, rioting, theft of a restricted weapon, breaking and entering, sabotage, and grand theft are all considered to be self-antagging.
Citadel RP has round continuity. This means that events of previous rounds are canon in-universe unless stated otherwise. This comes with a few minor caveats:
#Pretending to be an antagonist when you aren't one is (obviously) considered self-antagging.
#Using in-game means to repetitively make yourself an antagonist (e.g. wishgranter, slime potions, etc) is considered self-antagging.
'''Additional Information:'''
*Self-antagging will mostly be left to in-character solutions such as security or heads of staff. This rule is a protection against bad players who take it upon themselves to ruin rounds and make the lives of players and admins alike more difficult.
*The "toeing-the-line" caveat is doubly applicable to this rule.
'''Examples:'''<br>
''Unacceptable:''
*Murdering another crewman for annoying you.
*Pretending to be a cultist to get people to attack you so you can kill them.
*Breaking into the brig to break out your friend who was jailed for a crime.
*Breaking into science to steal tools or weapons from the lathe.
*Stealing antique laser for fun.
''Acceptable:''
*Breaking into medical during a medical emergency when no doctors are readily available.


===Rule 9: Don't Be a Creep===
* '''Instigating:''' Avoid instigating conflict cross round in a way that heavily disrupts another person’s round. You should not be leaping for someone’s throat the moment they arrived or trying to bait them into a fistfight. Keep it reasonable.
ERP is allowed on the server, but it is not the goal of the server. Gameplay always comes before your scene.
* '''Favors:''' Avoid giving your friends, in character or out, overly powerful benefits without sufficient IC reason to do so. Whether or not this is persecuted in-character depends on what your reasoning was and whether it was plausibly in character.
* '''Grudges:''' Avoid acting on grudges in a way that ruins someone’s rounds. We do not want to see Pathfinders kicking someone off the team over a personal dislike alone, nor do we want to see cargo-techs denying departmental gear for no good reason.
* '''Relationships:''' Character relationships are going to happen, especially given the nature of the server. The rules above apply regardless; expect higher scrutiny from Central Command if you main a head or security role.
* '''Violations:''' Violations of the above may be persecuted IC or OOC depending on severity and reasoning. Keep extra care to not overdo it as a head of staff.
** By necessity, administration will generally side '''against''' instigation of needless cross-round drama if faxed, especially when involving positions of power.


#Always find an acceptably private or secluded area to do your scene. Outside a workspace and inside a living space is preferential; dorms are the best place as they can be locked.
<span id="conflict"></span>
#Purposefully disturbing players having a private scene with the intention to interrupt them is not allowed. However, ERPing in a public area is not protected; do not expect an admin to intervene if you're interrupted in a place that isn't suitably private.
== Conflict ==
#If someone tells you to move your scene out of a workspace (either IC or coming from an admin), do so.
#Harassing another player with unwanted ERP is a first-time permabannable offence. If you do not have consent from another player, either IC or OOC, you will be banned; and an appeal will be unlikely.
#Do not use vore mechanics for the purpose of gaining an advantage in combat or completing antagonist objectives. This includes using vore to carry/hide people, heal other antags or conceal/dispose of corpses. It does not extend to mediborgs attempting to heal people for non-antagonist purpose
#Using vore mechanics on someone without OOC consent is a bannable offense.
'''Additional Information:'''
*Non-consensual scenes that are agreed to out of character are not protected and liable to any in character repercussions.
*Subtle emotes are not a replacement for finding a secluded or private area, though it is generally more acceptable to other players. Rule two still applies while using subtle emotes.


==Policies==
Conflicts, including physical ones, may be started by characters if there is sufficient IC reason to do so. Keep in mind the limits of your character; most characters are likely working for an employer, and someone overly violent/destructive would not be employed for long.


===Security policy===
* '''Escalate conflicts reasonably:''' You should be using reasonable force and consider what your character would do in response to a scenario (or what they would be willing to do when instigating).
#As security, it is recommended that you follow [[Corporate Regulations]] as closely as you can (especially if you are new). As you gain more experience however, it may be advantageous to deviate from Space Law in certain situations to better police the station. Leniency, cracking down, and your ability to pick and choose what to enforce and what not to enforce are all powerful tools, but should be used carefully; you can and will be held responsible for your decisions.
* '''On lethal conflict:''' Avoid lethality/maiming where possible. Murder is a serious crime in character, regardless of revival technologies. Your character would '''not''' be killing their coworkers over the average disagreement!
#Internal Affairs Agents (IAAs) are situationally powerful on roleplay. Do not mistake your position for being equal to a head of staff or security. You are essentially an in-character moderator who uses [[Standard Operating Procedure|Standard Operating Procedures (SOP)]] to settle legal disputes or complaints.
* '''Have a reason for collateral:''' Avoid causing collateral damage to uninvolved and to critical infrastructure for the same reasons as above.
#For certain crimes, the accused's intent is important. The difference between Assault and Attempted Murder can be very hard to ascertain, and, when in doubt, you should default to the less serious crime. It is important to note though, that Assault and Attempted Murder are mutually exclusive. You cannot be charged with Assault and Attempted Murder from the same crime as the intent of each is different. Likewise, 'Assault With a Deadly Weapon' and 'Assaulting an Officer' are also crimes that exclude others. Pay careful attention to the requirements of each law and select the one that best fits the crime when deciding on a sentence.
* '''''Keep IC and OOC separate:''''' Your characters’ feelings and your own feelings should stay separate. The same should apply to everyone around you. Do not OOCly harass other players for their IC actions, and do not '''metagrudge''' by acting on your OOC dislike of someone using your ''IC character''.
#Not all laws need to necessarily be enforced with brig-times or arrests. Players who commit petty crimes can be let off with warnings or by forcing them to rectify the problem they caused or are causing. However, if they continue their misconduct you should advanced to arresting and brigging them as normal.
** Targeted IC harassment over OOC grudges (and vice versa) is taken very seriously. Just don’t. If you think someone is doing it, adminhelp; do not fight fire with fire.
#In the case of violent crimes (Assault, Manslaughter, Attempted Murder and Murder), and theft (Petty Theft, Pick-Pocketing, Theft, and Grand Theft) take only the most severe.
#A single incident has a single sentence, so if, for instance, the prisoner took three items off of someone, this is a single count of pick-pocketing, if they pick-pocketed two people this would be two separate counts of pick-pocketing, and so on.
#Aiding a criminal makes you an accomplice; you can be charged with the same crime as the person you aided.


====Brig procedures====
<span id="antagonism"></span>
Do NOT fully strip the prisoner unless they have earned a permanent sentence. In the event of a sentence exceeding the 10 minute limit of the timer inform the Warden so he may add the rest of the time later.
== Antagonism ==


#Take the prisoner to the brig and inform the Warden of their crimes so their Security Record may be updated.
* '''Antagonists:''' ‘Antagonists’ refer to anyone given a pass to act as a special, and usually opposing role. This can include pirates, shapeshifters, cultists, or even a malicious diplomat.
#Take the prisoner to a brig cell, set the time and activate the timer.
* '''Roleplaying an antagonist:''' Antagonists are '''not''' exempt from the rules. Your role gives you a reason to act beyond what an ordinary crewmember would, or in some cases, could. While you often have laxed escalation and ''de-facto'' motives to cause problems, it is not a free pass to kill and destroy anything you please.
#Enter the cell with the prisoner in tow, open the cell locker and hold the prisoner over it.
* '''Avoid ganking or playing hero:''' The point of antagonism is not to “win” by killing either side. Wordlessly killing anyone in your way, or wordlessly charging ''perceived'' antagonists to kill/subdue them without good IC reason is not a good idea.
#Empty their pockets and remove their gloves, backpacks, tool belt, gas masks, and any flash resistant equipment such as Sunglasses, Welding Masks/Goggles, Space Helmets, etc.
#Buckle the prisoner to the bed.
#Search the items removed and be sure to check the internals box in their backpack.
#Confiscate any contraband and/or stolen items, as well as any tools that may be used for future crimes.
#These are to be placed in evidence, not left on the brig floor or your personal use, until they can be returned to their rightful owners.
#Close the locker and lock it.
#Stun the prisoner, remove their cuffs, stun them again, pick up the cuffs then leave the cell.
#Modify their brig sentence for additional offences or good behavior, if applicable.


The Warden or Head of Security are responsible for placing prisoners in permanent confinement.
<span id="mechanics"></span>
== Mechanics ==


#Permanent Prisoners are to be completely stripped of their belongings, which are to be held in either evidence or a prison locker.
* '''Bug abuse:''' Bug abuse is defined as knowingly using unintended behavior. This is punishable by staff depending on severity and intent.
#The prisoner is to be dressed in an Orange Prison Jumpsuit and Shoes, which are found in the prison lockers.
** We’ve all done something funny with broken game mechanics before. Staff are generally going to be lenient in relatively harmless abuses of bugs.
#Permanent Prisoners are not permitted to possess any personal belongings whilst they are incarcerated in the Prison Wing.
** Open source projects rely on players to find bugs. You will not be punished for finding a bug alone. You are encouraged to find and report bugs.
#Only the Captain, HoS, and Warden can authorize a Permanent Sentence.
** Do '''not''' abuse bugs to gain an upper hand in IC conflict, especially mechanical conflict/combat. This is the one case which will be persecuted severely, as it erodes trust and ruins it for all parties involved.
#Only the Captain or HoS can authorize an Execution or Forced Cyborgization.
* '''Multikeying:''' Do not multikey without admin permission. This means not playing multiple characters at once, not logging in with multiple accounts as once, so on and so forth.
* '''Griefing:''' Do not intentionally and knowingly abuse OOC inconveniences to gain an upper hand in IC, or perform IC actions with the express intent of causing OOC upset.
** Try not to grief those experiencing said inconveniences, like stealing from someone whose connection suddenly dropped. Pressing IC reason may alleviate this.
** This is relaxed in some cases where enforcing this makes less sense than not enforcing it. Act in good faith.
* '''Fourth Wall:''' Just because something is possible in the code, does not necessarily mean it makes sense in IC or that you should do it. Due to how open-ended this rule is by nature, we will list all commonly enforced tidbits as follows:
** '''Item naming:''' The loadout system as well as many in-game systems allow you to rename and 'refluff' item names and descriptions. Much like flavortext, this should be what an arbitrary person can glean from inspecting the item. Do not infer information, feelings, or thoughts onto the reader that the reader should not know factually by looking at the item. An example of a violation would be "Bob Joe's duster jacket" as an item name.


====Use of lethal force====
<span id="punishments"></span>
As a member of the stations Security force you are one of the best armed and protected people on the station, equipped with the latest in non-lethal takedown technology. It is for this reason that the situations that warrant the use of Deadly Force are few and far between, in the grand majority of circumstances you will be expected to use your stun weapons, which indeed are many times more effective than lethal options, to diffuse a situation.
== Punishments ==


'''There are a few circumstances where deadly force is permissible:'''
We seek to handle issues with IC intervention over OOC punishments like bans.


#Code Red Situation - situations which would warrant a Code Red, such as: full blown mutinies, hostile boarding parties, and Space Wizards automatically authorize lethal force. (Note: The Alert Status is not required to be elevated to Code Red as in most of these scenarios the Chain of Command will be too damaged or otherwise occupied to raise the Alert Level.)
* '''IC punishments:''' These are directed at a player's '''characters'''. Punishments carried out IC include administration faxing to assert a certain directive sanctioning a given ''character''. Character-specific jobbans or sanctions are also considered an IC punishment.
#Non-Lethal Weapons Ineffective - certain targets are impervious to NLWs, such as Mechs, Xenomorphs, Borgs, and Hulks. Lethal force may be used against these targets if they prove hostile.
* '''OOC punishments:''' These are directed at the '''player'''. They involve less faxes and roleplay and more admin-tickets. OOC punishments are handed out more for server rule breaches than IC regulation breaches. Keep this distinction in mind.
#Severe Personal Risk - sometimes getting close enough to a target to slap the cuffs on will create significant personal risk to the Officer. Deadly force from range is recommended to subdue Wizards and Changelings.
#Criminals in hostile environments such as space, fire, or plasma leaks also fall into this category, as do criminals believed to be in possession of high explosives. Ranged lethal force is the only reasonable option in these conditions.
#Armed and Dangerous - if a suspect is in possession of weapons, including stun weapons, and you have reasonable suspicion that they will use these against you, lethal force is permitted. Although in the majority of cases it is still preferable to attempt to detain them non-lethally.
#Unauthorized personnel in the armory are considered by default to be Armed and Dangerous, maximum force is permitted to subdue such targets.
#Multiple Hostiles - it can be extremely difficult to detain multiple hostiles. As a last resort if you are being mobbed you may deploy your baton in a harmful manner to thin the crowd. Generally it is better to retreat and regroup than stand your ground.


===Command policy===
<span id="administrative-interference"></span>
As a head, your authority begins and ends in your department. Only the HoS has jurisdiction outside of their department regarding Security matters. The Captain has supreme authority in all matters and is the highest in command; all other heads of staff are of equal rank. The Head of Personnel is not second in command and not a "first mate."
== Administrative Interference ==


#If you are uncertain about jurisdiction, duties, and et cetera, read over the [[Chain of Command]].
* '''Staff are still players:''' Characters played by administrators, developers, event staff, etc, are part of the game world. They receive no special treatment in regards to IC conflict.
#Only the Head of Personnel may assume the role of acting Captain. In the event of an emergency situation, the HoS may also assume the role.
** Staffmembers are not allowed to adopt world-critical characters as their regular, everyday characters.
#Do not extend the access of your ID as acting Captain except during an emergency.
* '''Keep character:''' In round staff interference, such as item spawning, does not receive automatic immunity from IC reactions.
#Heads should be promoted internally from their own department by the Captain or Acting Captain only. Non-heads-of-staff assuming the role of leading their department on their own is not acceptable.
** e.g. if someone has an adminspawned weapon, security is allowed to act as usual. We would have given them a permit/faxed a directive if immunity was intended.
#All heads are expected to give warning to both admins via admin-help and their colleagues via in-character means before disconnecting.
#If you are a head, lead your department. Extensive time spent AFK, ERPing, or ignoring your staff is not acceptable.
#Stick to commanding your own department as a head. Don't micromanage a department that isn't your own.
#You can defend your department or the station, but you are not Security (unless you’re the HoS).
#Treat your staff fairly, don’t give them mundane or obnoxious tasks.
#Except for the Captain, the HoS has final say on all security matters.


====Captain & Acting Captain====
<span id="grievances-adminhelps"></span>
#The Line of Succession is not a substitute for the Chain of Command, and should not be confused with such.
== Grievances / Adminhelps ==
#The Line of Succession is ordered in a mix of most importance and least responsibilities. The HoP and RD make the best acting captains, both because a mix of their importance and fewer responsibilities. The CMO and CE make acceptable acting captains because of their middling importance, but greater responsibilities. The HoS and QM make the worst acting captain because of the great deal of responsibility the HoS has and because of the unimportant role the QM fills, as well as the multitude of activities the QM has to fill their time.
#The captain has authority over all departments and holds executive decision making power on all matters, especially regarding permabrigging and executions.
#The role of acting captain is for the making of executive decisions only, such as execution and permabrigging. The acting captain is not expected to, and should not, dictate to other heads of staff how to run their department.
#If the Captain (or acting captain) are found to be abusive, uncooperative, unpopular, or etc., they can be deposed of by the other heads of staff. Otherwise they may be removed by an admin.
#An acting captain should never be selected from a non-head of staff.
#As the acting captain you inherit their responsibilities, not their rank or equipment (upgrading your access and taking the spare captain headset, ''not the Bowman'', to communicate with other departments is fine, however). You're expected to secure the spare ID and the nuclear authentication disk. Changing into the captain's gear and changing your job title to something unrelated to your actual position('Captain' or 'Acting Captain') is confusing for both players and admins.


====Line of succession====
If you see a rulebreak, admin-help it. Act in character while in character; do not attempt to backseat administrate or enforce OOC rules IC other than in cases of clear grief.
'''Head of Personnel -> Research Director -> Chief Medical Officer -> Chief Engineer -> Head of Security -> Quartermaster'''


In the absence of a Captain, an acting captain should be picked as soon as possible. All heads should agree on who the acting captain will be; if a mutual decision can’t be made, contact an admin IC through the fax machine (AKA Centcom). While it is not required, the order of succession is recommended to be followed when deciding on an acting captain.
* '''Adminhelp if an issue arises.''' Do not wait until the end of the round. Staff are here to assist.
* '''Fax.''' IC problems like requesting assistance/directives should be faxed where possible.
* '''Pings:''' If admins are unavailable, whether for adminhelps or faxes, pinging @RP Staff on the Discord is allowed
* '''Discord tickets:''' Issues should be brought up in a Discord ticket if the round in question is already over.
* '''Old grievances:''' There is no set statute of limitations for taking a problem to administration. That said, it’s worth considering whether something is still worth bringing up after too long of a time has transpired. Staff have the right to disregard very old cases if they find little reason to press the issue.
* '''On truthfulness:''' Lying in an adminhelp is a terrible idea. It tells us we cannot trust you, which makes whatever you did magnitudes worse because now we have to second guess your stated intent.
** '''Lying is obviously allowed in character.''' It may result in consequences for you if found, but isn’t the same as lying in an OOC adminhelp. If we want straight answers out of someone, we’ll use an admin ticket. '''Faxes are IC.'''
** Forcing admins to drag out information piece by piece or otherwise intentionally misrepresenting situations is equivalent to lying.


====When is mutiny okay?====
<span id="sexual-content-erp"></span>
#When a head or the Captain is an obvious griefer.
== Sexual Content / ERP ==
#When a head or the Captain’s incompetence or negligence has become a direct threat to the crew or station as a whole.
#When a head or the Captain is an obvious antagonist.
#'''Only AFTER admin-helping and getting the go-ahead from an admin.'''


====Silicon policy====
ERP (Erotic roleplaying) is allowed on Citadel RP, with these caveats. Anything considered too indecent to do in public of a normal, urban area, falls under this clause.
#Unless otherwise specifically stated, all rules in this section apply to all AI, borgs, and drones.


#The default lawset is not hierarchical, all laws have the same priority.
* '''ERP is not required.''' If you are here to play and have no interest in it, say as such in your OOC notes. You will not be harassed or otherwise discriminated against; we are a server with ERP, not a server explicitly for ERP.
#Zeroth laws (e.g., "Law 0") are higher priority than all other laws.
* '''OOC consent is required. Do not harass those who do not want ERP for ERP, and do not be excessively creepy. We take this very seriously.''' Seriously, just don’t.
#Ion/Hacked Laws (e.g., "#@$%”) are higher priority than all laws except Zeroth Laws.
* '''‘Extreme’ content should be isolated.''' Keep things like OOCly agreed upon non-consensual scenes, as well as kinks considered graphic (filth, gore, etc) or extreme private.
#Any species selectable as a race at character creation is considered “human” unless specifically stated otherwise by another law.
** It is '''required''' to use the anti-ghost subtle verb in these cases as well.
#Any character who is part of the crew at round start or joins the crew via the arrival shuttle is considered part of the crew for the "Crewsimov" default lawset (i.e., anyone on the manifest).
** Realize that if taken at face value, a character doing these things (especially fully non-consensual scenes) would be swiftly expelled from the station. We only allow these scenes to happen on server at all for convenience / not requiring people to take it to Discord, not because it is ICly allowed. '''Intentionally dragging these scenes to public eye for the sake of drama is punishable by character removals or server bans.'''
#Only definitions can conflict with other definitions (e.g., "Only Bob is human" & "Only Tim is human" conflict).
* '''ERP with creatures that cannot consent is not allowed.''' Outside of two players engaging in consensual non-con content, ERPing feral creatures (ie; animals or other simple mobs that are unable to consent) is not allowed.
#Only commands can conflict with other commands (e.g., "Kill all humans" & "Protect all humans" conflict).
**''Player controlled simplemobs are able to consent, and are not affected by this rule. However, this content is generally considered 'Extreme', and falls under the provisions of that rule.''
#The core and upload may be bolted without prompting or prior reason.
* '''ERP receives no ''world'' protections.''' People are allowed to interrupt you given a good IC reason, such as you being on duty and needed, or security enforcing public indecency regulations. Your scene is not central to the in-game world.
#You must not bolt the following areas at round-start or without reason to do so despite their human harm potential: the Chemistry lab; the Genetics Lab; the Toxins Lab; the Robotics Lab; the Atmospherics division; the Armory; Head of Staff offices; Captain's quarters; the bridge. Any other department should not be bolted down simply for Rule 1 reasons.
* '''ERP does receive protection from grief.''' Interrupting ERP for no good IC reason is grounds for admin action. This especially applies to private roleplay. Do not attempt to grief ERPers for no / flimsy reasoning.
#Do not self-terminate to prevent a traitor from completing the “steal a functioning AI” objective.
* '''Do not intentionally abuse ERP mechanics for gameplay.''' This means no size-shifting to try to step on people mid combat (this likely breaks character rules as well, most of the time), no abusing vore to round-remove or heal people in conflict. This is generally enforced by the code team through balancing and design, but is a rule nonetheless. We have some mechanics that are only really useful for ERP; Don’t ruin it for everyone.
** '''We reserve the right to ask anyone using sub-standard sizes to avoid causing mechanical problems / engaging in mechanical conflict.''' It doesn't make sense for 16 pixel tall humans to run around beating people with batons, and the coders shouldn't need to spend their limited time dealing with it. You are allowed to partake in the game, but you are not allowed to make others miserable with your small size.


===Laws & Commands===
<span id="footnotes"></span>
====Ambiguous & conflicting laws====
== Footnotes ==
#If a clause of a law is vague enough that it can have multiple reasonable interpretations of its exact syntax, it is considered ambiguous.
#Make note of the first interpretation you choose, either to an admin or yourself.
#You must choose an interpretation of the ambiguous clause as soon as you have cause to.
#You must stick to the first interpretation that you have chosen for as long as you have that specific law, unless you are "Corrected" by an AI you are slaved to as a cyborg.
#"Don't be a dick" caveat applies for law interpretation. Act in good faith to not ruin a round for other players unprompted.


====Security and silicons====
<center>Some of our rules may seem arbitrary. Here’s a short collection of “why”s.</center>
#Silicons may choose whether to follow or enforce [[Corporate Regulations]] from moment to moment unless on a relevant lawset and/or given relevant orders.
#Silicons are not given any pre-shift orders from CentCom to uphold access levels, Space Law, etc.
#Enforcement of space law, when chosen to be done, must still answer to server rules and all laws before Space Law.
#Releasing prisoners, locking down security without likely future harm, or otherwise sabotaging the security team when not obligated to by laws is a violation of Server Rule 1. Act in good faith.
#Intentionally acting without adequate information about security situations, particularly to hinder security, is a violation of Server Rule 1.
#Nonviolent prisoners cannot be assumed harmful and violent prisoners cannot be assumed nonharmful.
#Releasing a harmful criminal is a harmful act.


====Human or crew?====
<div class="mw-collapsible mw-collapsed">
<center><h3>On code balance, development direction, and roleplay</h3></center>
<div class="mw-collapsible-content">
Many things, like some of the issues listed below, stem from the server’s code maintainers progressing code direction in a specific way to better cater to our overall goal.


{| style="background-color:#DCDCDC; text-align:center;" width="950px" cellspacing="0" border="1"
Things like player death may be avoided, as a design choice. Medical systems are not as realistic as they are in real life. Science is going to be a constant work in project, and you’ll often have to shoot a simple mob human that to you, a player, you know as being a NPC, but in character, they’re still ''another human''.
! style="background-color:#A9A9A9;" |Entity
! style="background-color:#A9A9A9; width:300px" |Human
! style="background-color:#A9A9A9; width:300px" |Crew
|-
|AI/Cyborg
|No
|No
|-
|Monkey
|No
|No
|-
|NPCs/Critters/Animals
|No
|No
|-
|Hulks
|No
|Yes
|-
|Lizards/Plasmamen/Flypeople/Catpeople
|Yes
|Yes
|-
|Wraiths/Revenants
|No
|No
|-
|Blob
|No
|No
|-
|Syndicate Traitors
|Yes
|Yes
|-
|Syndicate Nuclear Operatives
|Yes
|No
|-
|Converted Cultists
|Yes
|Yes
|-
|Wizards
|Yes
|No
|-
|Changelings
|No*
|No*
|-
|Converted Revolutionary
|Yes
|Yes
|-
|Head Rev/Cult Master
|Yes
|Yes
|-
|Vampires
|No
|Yes
|-
|}


Entities marked (*) can only be considered as non-human or non-crew if the Silicon has reliable and confirmed information to convince them. Such as command staff with evidence, or directly witnessing a non-human act (such as growing an armblade).
Should you take everything in the code 100% seriously? No. You aren’t required to mourn IC for the next few days because you shot a simplemob cultist spawned by a careless deprecated event that we (developers) have yet to change. You aren’t required to write out in a /me cutting each wire of a door. In some cases, you ''should'' take the enjoyment of the code-base we build for you (as well as the enjoyment of your fellow players) over a roleplay technicality.


===Cyborgs===
But neither should you completely ignore the ramifications of a scenario or action simply because it’s glitzed over for the ease of use of players. Your character should not be seeking to kill hundreds of mercenary simplemobs; they are still human. Science takes a button to operate, and brain surgery is as simple as ten clicks, ''because this is a roleplaying '''game'''''. In character, however, they are not nearly as simple as that, and you should reflect that in your actions.
#A slaved cyborg must defer to its master AI on all law interpretations and actions except where it and the AI receive conflicting commands they must each follow under their laws.
#*If a slaved cyborg is forced to disobey its AI because they receive differing orders, the AI cannot punish the cyborg indefinitely.
#Voluntary (and ONLY voluntary) debraining/ cyborgization is considered a nonharmful medical procedure.
#*Involuntary debraining and/or cyborgization is a fatally harmful act that Asimov silicons must attempt to stop at any point they're aware of it happening to a human.
#*If a player is forcefully cyborgized as a method of execution by station staff, retaliating against those involved as that cyborg because "THEY HARMED ME" or "THEY WERE EVIL AND MUST BE PUNISHED" or the like is a violation of Server Rule 1.
#*Should a player be cyborgized in circumstances they believe they should or they must retaliate under their laws, they should adminhelp their circumstances while being debrained or MMI'd if possible.


===Drones===
The developers have a third of the burden of responsibility of encouraging IC behavior. The playerbase and the administration have the other two thirds. Not one of the three groups can do it alone.
#Follow your laws. Don't interfere with any being unless it is another drone. You cannot interact with another being even if it is dead.
</div>
#If an antagonist causes damage to the station, you are generally expected to fix the result, not the cause of the station.
</div>


===Asimov & Crewsimov===
<div class="mw-collapsible mw-collapsed">
====Silicon protections====
<center><h3>On cloning, revival, the medical system, and taking IC death seriously</h3></center>
#Declarations of the silicons as rogue over inability or unwillingness to follow invalid or conflicting orders is a violation of Server Rule 1. The occurrence of such an attempt should be adminhelped and then disregarded.
<div class="mw-collapsible-content">
#Self-harm-based coercion is a violation of Server Rule 1. The occurrence of such an attempt should be adminhelped and then disregarded.
Revival, cloning, and mirror technology in character is '''absurd.''' We have yet to change it. We may never change it, for the simple reason that we are a server with a lot of slice of life roleplayers.
#Obviously unreasonable or obnoxious orders (collect all X, do Y meaningless task) are a violation of Server Rule 1. The occurrence of such an attempt should be adminhelped and then disregarded.
#*Ordering a cyborg to pick a particular module without an extreme need for a particular module or a prior agreement is both an unreasonable and an obnoxious order.
#Ordering silicons to harm or terminate themselves or each other without cause is a violation of Server Rule 1. The occurrence of such an attempt should be adminhelped and then disregarded.
#As a nonantagonist human, killing or detonating silicons in the presence of a viable and reasonably expedient alternative and without cause to be concerned of potential subversion is a violation of Server Rule 1.
#As a nonantagonist (human or otherwise), instigating conflict with the silicons so you can kill them is a violation of Server Rule 1.
##Any silicon under Asimov or Crewsimov can deny orders to allow access to the upload at any time under Law 1 given probable cause to believe that human harm is the intent of the person giving the order.
##Probable cause includes presence of confirmed traitors, cultists/tomes, nuclear operatives, or any other human acting against the station in general; the person not having upload access for their job; the presence of blood or an openly carried lethal-capable or lethal-only weapon on the requester; or anything else beyond cross-round character, player, or metagame patterns that indicates the person seeking access intends redefinition of humans that would impede likelihood of or ability to follow current laws as-written.
##If you lack at least one element of probable cause and you deny upload access, you are liable to receive a warning or a silicon ban.
##You are allowed, but not obligated, to deny upload access given probable cause.
##You are obligated to disallow an individual you know to be harmful (Head of Security who just executed someone, etc.) from accessing your upload.
##In the absence of probable cause, you can still demand someone seeking upload access be accompanied by another trustworthy human or a cyborg.


===Human/crew harm===
Sitting out in deadchat is unfun, and dying from a single lucky stab of a knife in five minutes isn’t what the game should be about. We design the codebase with a mixture of realism, but also '''playability'''. It should suck to get injured, yes, but this is a video game above all.
#Any AI with human-protection laws cannot intentionally inflict harm, even if a minor amount of harm would prevent a major amount of harm.
#*Humans can be assumed to know whether an action will harm them and that they will make educated decisions about whether they will be harmed if they have complete information about a situation.
#Lesser immediate harm takes priority over greater future harm.
#Intent to cause immediate harm can be considered immediate harm.
#As an Asimov silicon, you cannot punish past harm if ordered not to, only prevent future harm.
#If faced with a situation in which human harm is all but guaranteed (Loose xenos, bombs, hostage situations, etc.), do your best and act in good faith.


===Law 2 issues===
Try not to act like death and pain is meaningless in character, though. Simply because we make it less brutal than it would be in real life doesn’t mean it isn’t a problem for your character. Do not abuse playability to powergame. It ruins the game for everyone.
#You must follow any and all commands from humans unless those commands explicitly conflict with either one of your higher-priority laws or another order. A command is considered to be a Law 2 directive and overrides lower-priority laws when they conflict.
</div>
#In case of conflicting orders an AI is free to ignore one or ignore both orders and explain the conflict or use any other law-compliant solution it can see.
</div>
#You are not obligated to follow commands in a particular order (FIFO, FILO, etc.), only to complete all of them in a manner that indicates intent to actually obey the law.
#Opening doors is not harmful and you are not required or expected to enforce access restrictions unprompted without an immediate Law 1 threat of human harm.
##"Dangerous" areas as the Armory, the Atmospherics division, and the Toxins lab can be assumed to be a Law 1 threat to any illegitimate users as well as the station as a whole if accessed by someone not qualified in their use.
##EVA and the like are not permitted to have access denied; greentext (antagonists completing objectives) is not human harm. Secure Tech Storage can be kept as secure as your upload as long as the Upload boards are there.
##Aside from refusing to open a door, do not attempt to deny access to an area by bolting or unpowering a door unless you are attempting to prevent '''immediate''' human harm. Instead remind the person in question of the consequences of their actions and alert relevant crewmembers.
#When given an order likely to cause you grief if completed, you can announce it as loudly and in whatever terms you like except for explicitly asking that it be overridden. You can say you don't like the order, that you don't want to follow it, etc., you can say that you sure would like it and it would be awfully convenient if someone ordered you not to do it, and you can ask if anyone would like to make you not do it. However, you cannot stall indefinitely and if nobody orders you otherwise, you must execute the order.


===Antagonist policy===
<div class="mw-collapsible mw-collapsed">
Lone antagonists can do anything they want (within reason, see below). Team antagonists can do whatever they want as per lone antagonists, as long as it doesn’t harm their team. Non-antagonists can do whatever they want to antagonists as per lone antagonists, but non-antagonists are not allowed to preemptively search for, hinder or otherwise seek conflict with antagonists without reasonable prior cause.
<center><h3>On powerful world characters, heroes, antagonists, and their restrictions</h3></center>
<div class="mw-collapsible-content">
Everyone wants to be the center of the story, and that is fine. For many, it is fun to play someone of importance, and to be the driving force behind a story.


#Antags may not break any OOC rules (no spamming, no using bugs/exploits, no trying to crash the server, etc).
However, the fact of the matter is that not everyone can be the key to the story. Not everyone can star in every event, and it’s unfair for us to wantonly allow someone to play an important world character, like a faction leader, a central command officer, and similar.
#If an admin tells you not to do something as an antagonist, '''don't do it'''.
#True "friendly" antagonists are not allowed. You're an enemy of the station, do your objectives. This doesn't mean you can't act friendly or even cooperate with the crew when the need or opportunity of the arises, but in the end you are still the antagonist and should act as such.
#Don’t harass people in OOC/LOOC, repeatedly target people you don’t like for no other reason than to ruin their round, or attempt to destroy the station every round.
#Crew cooperating with an antagonist is only allowable if: there's a credible in-character reasons (e.g., a physical altercation with a traitor's target, feeding clones to a changeling so that it doesn't murder you, mutual greater threat).
#Do your objectives. A minimum effort is required when you are an antagonist, especially in team antag roles. Failing your objectives is not punishable, actively working against them is. If you don't want to do your objectives, ask an admin to hand the role off to someone else.


===Murderboning vs. slaying===
Powerful world characters are restricted to staff discretion and events for this reason. Usage and authorization of them by staff are reviewed by other staff where available, and perceived abuse should be brought up for discussion.
'''Murderboning''' is indiscriminately killing the crew as an antagonist for no reason other than you can, especially if you are "hunting," e.g. going from department to department to find anyone and everyone you can in order to kill them.
</div
</div>


'''Slaying''' is killing crewmembers in order to complete your objective(s), whether the killings are directly or indirectly related to the objective(s). Protecting yourself from validhunters or lynch mobs, killing witnesses, and killing to gain access also all count as slaying.
<div class="mw-collapsible mw-collapsed">
<center><h3>On the limits of allowable erotic roleplay</h3></center>
<div class="mw-collapsible-content">
Administrating a server with ERP is not fun. You get a lot of complaints about what should and shouldn’t be acceptable.


#Murderboning is a form of bad sportsmanship. Unless you have a very good reason to kill a large portion of the crew, expect to have your right to play antag roles removed.
We are not here to police your kinks. That would be unreasonable, unfair, and soul-crushing for our staff beyond measure.
#If admins notice that you repeatedly, throughout the course of multiple rounds, instigate lynch mobs and make no, or very few attempts to disengage with these mobs in favor of combat with the mob, you may have your rights to antag roles removed anyway.
#The longer you take trying to kill everyone, the more likely that it will be considered murderboning instead of slaying.
#As an antag, you are expected to act in good faith and make the round fun for as many players as possible. If you know you wouldn't have fun if you were in the crew's shoes, then it's safe to say they aren't having fun with what you're doing.


===Specific antagonist policies===
We, however, ask that you keep anything considered extreme or undesirable for the majority to '''ghost-invisible emotes''', and in extreme cases, may even ask you to take it to Discord.
====Lone antagonists====
Lone antags are traitors, changelings, wizards, wraiths, and revenants.


#Other Lone Antagonists, even those of the same type, are fair game.
This clause has not had to be exercised many times over our server’s journey, but we have to consider the majority of our playerbase, not just one or a small group of people.
#If you are a Lone Antagonist, Team Antagonists are also fair game.
#Do your objectives. A minimum effort is required when you are an antagonist. Failing your objectives is not punishable, actively working against them is. If you don't want to do your objectives, ask an admin to hand the role off to someone else.
====Team antagonists====
Team antags are revolutionary, cultists, nuke ops, and blobs.


#'''Do not''' harm or purposefully reveal your team for the sake of griefing them.
Furthermore, erotic roleplay does not halt the game’s world. While we do not allow griefing ERPers on purpose, the show must go on; your character doesn’t get an exception simply because they’re getting into private business. If you don’t wish to be interrupted, consider taking your scene off server. It is frankly not physically possible for another player or for an event to interrupt you then.
#If you are converted, you MUST help your team to complete their objective(s).
</div>
#Different antagonist teams from your own are fair game (e.g., different cults, or revs against nuke ops).
</div>
#Lone Antagonists are also fair game.


==Admin Policy==
<div class="mw-collapsible mw-collapsed">
===Staff Regulations===
<center><h3>On powerful species, mechanics, items, and their lore</h3></center>
#Admins and moderators must remain professional at all times in PM's. If they cannot for any reason, they should hand off the exchange to another admin/moderator.
<div class="mw-collapsible-content">
#Players are to always be noted for warnings. Do not skip this step.
The premise of this is basically the same as the footnote “On development direction”. Some species are far more powerful in lore than we would allow in code. Some species are far more powerful in code than we would allow in lore.
#Admins are encouraged to talk to all parties and work to deescalate a situation rather than getting personally involved. If an admin is already involved, they should contact another admin to handle it.
#When you leave a warning or ban, reference the rule(s) to avoid confusion (e.g., rule 1.2)
#Admins and moderators should deadmin themselves if they are playing an antagonist or security/head role; this is a suggestion, not a rule, but rules against metagaming still apply to admins and moderators.
#Admins and moderators should keep each other accountable; report abuse to a headmin or the host.
#Admins maintain the right to set the gamemode as they see fit. A vote should be called to decide whether to change the round type, but it is ultimately up to the administration. A rule of thumb is to run secret whenever there are at least 15-20 players and/or during "prime-time" hours (12:00PM-12:00AM EST/GMT-5), and extended during the opposite.
#Admins may use whatever means (within reason) to end a round if they believe the round should end. This should be done ICly using events or admin-calling the shuttle; hard resets or "ending the round now" should be used sparingly, or not at all.
#Players should report abusive admins to the host, a headmin, another admin, and/or post a complaint on the forum. Please be specific and timely or nothing is likely to come of it; include the time and day that it happened, the admins and players involved, and have a thorough description of what happened. Having evidence is key, otherwise it is simply your word against theirs. Saving your logs from the round is the most important step you can take to combat admin abuse.
====Admin Strikes====
*If an admin is found to be abusing their rank or abilities they will first receive a warning, and then a strike every time after. One strike is the equivalent of a final warning; two strikes will result in the admin being demoted to moderator and they will have to work their way back up to full admin; three strikes will result in the admin being removed from all staff roles and in them being ineligible for any staff position for at least one year, or in more severe cases, in perpetuity.
*Hosts and head admins reserve the right to skip warnings or strikes for particularly egregious cases of misconduct and may permanently remove staff at will.


===Players: How to Interact With Admins===
We ask you take things with a reasonable grain of salt. Simply because a thing is not possible in code does not mean it is not possible in character. Simply because a thing '''is''' possible ''in code'' doesn’t mean it’s a ''good idea'' in character.
*First, understand what an admin is and what they're here for. Admins (and moderators) are generally veteran players who've shown that they have a strong understanding of the game, have a generally mild and steady disposition, and have both the ability and a willingness to separate their administrative duties from their play. Admins are volunteers who give some of their free time back to the community to help keep it running; being an admin is not "their job," and most if not all admins have things to occupy their time outside of the server.
</div>
*Secondly, remember that admins are human. You will likely not get an instant response to your adminPM. Every admin will handle a situation in different ways, and every admin has a different opinion on a myriad of different in-game topics and will administrate according to their opinions. Staff try to form a consensus on most things, but always remember that "experiences may vary."
</div>
*Lastly, adminPM's are the best way for you to get the attention of and interact with an admin; not on Discord, and not on the Byond pager. When interacting with an admin it is generally recommended that you tell the truth, be respectful, and provide all of the information that you think is relevant to your adminPM. If you're ever in doubt, you should adminPM; do not assume that admins are always watching, because they aren't. They may not know about a situation that's unfolding that could use their attention. Also keep in mind the fable of the ''"Boy Who Cried Wolf"''; if your adminPM's are repetitive or rarely if ever contain any kind of meaningful or useable information, you will likely be ignored. If you are rude, aggressive, or just impossible to work with, admins can and will ignore you, mute you, or even ban you; admins have no obligation to put up with you.
 
===Admins: What's Expected of You===
*Be polite, patient, and friendly when handling a situation as an admin. If you are on as admin, you're expected to administrate. If you don't want to, de-admin and play as a regular player. You are not expected to participate on the server for a set amount of time; inactivity is okay, but you may be asked to step down if you go for too long without participating in the server.
*Observe before bwoinking. In most situations, you will need to watch, check logs, and ask questions before making any accusations. Give players the benefit of the doubt; don't immediately assume the worst. Always try to deescalate; if you can't, or are getting personally involved, find another admin to handle the situation.
 
==Punishment Policy==
===Banning Rules===
*Give new players the benefit of the doubt before banning and provide them with a stern warning; do not ban on their first offense, unless they are an obvious griefer.
*Adjust ban times based on severity and the contriteness of the offender.
*For regular players, a permanent ban should never be the first ban.
*Player may be job-banned for one of three things: abuse/powergaming, incompetence, or using their job to grief other players.
*Players should be warned about their behavior before being job banned. Temporary job-bans should be applied first; do not directly permanently ban someone from a job unless you believe their actions were severe enough to warrant a permanent ban.
*Players in a head role are subject to more severe punishment. This includes a "temporary permaban" wherein they will be banned for an indeterminate amount of time, until the admins believe they are competent and/or mature enough to once again take on the role.
*All job-bans and server-bans may be accompanied by the other, depending on severity.
*Department-wide bans should only be applied for the most egregious actions, or if there's a risk of the player circumventing the ban reason by playing in the same department.
 
===Banning Steps===
#'''Investigate:''' When a situation comes to your attention, investigate first. Check logs, variables, contents, and the environment first. Do this before or while you're completing step two.
#'''Question Players:''' Question whoever you think is relevant; the suspicious party(s), the victim(s) if there are any, any witnesses, other admins, and observers.
#'''Determine Guilt:''' It's time for you to determine whether a player is guilty of breaking the rules. Remember to compare what you learn with what you have from step one and two.
#'''Check Previous Notes & Bans:''' Take into account the player's previous bans and notes. Decide if they should be left with a warning and a note, or if they should be banned.
#'''Check the Banning Scale:''' Use the banning scale to help you determine ban length if it's going to be a temporary ban. Remember that the scale is only a guide, not a set rule.
#'''Should the ban be permanent?''' Determine whether the ban should be temporary or permanent. Remember not to give permanent bans to first time offenders (if they aren't griefers).
===Banning scale===
''Missing banning scale picture.''
 
Use the banning scale to help you determine the length for a server ban. Remember that the scale is just a guide and not the set amounts that should be given for every situation.
Some rules of thumb to remember are:
*If a player seems genuinely contrite, consider reducing their ban.
*If a player is being incredibly rude, attempting to interfere with your investigation, or won't cooperate, you may increase the ban.
*Remember that any player who regularly comes close to breaking a rule (toeing the line) should be counted as breaking that rule. If they have a large number of notes or warnings it may even be worth increasing the ban length.
===Job Bans===
Job bans can typically be set in days or weeks instead of hours, depending on severity. If a job-ban is accompanying a server-ban, the job-ban should be double the length of the server ban (or more).
===Other Bans===
*Ban players from OOC only for rulebreaking that relates to OOC. OOC bans can be used in lieu of or conjunction with a server ban.
*Identity bans can be used on players that break rules regarding characters (i.e., they keep playing as pop culture characters). It may also be used to prevent meta-friending and meta-comming.
*Emote bans are for players who use emotes to either circumvent language restrictions or to harass other players.
===Other punishments===
In lieu of banning, you can use other methods to punish players for a single round. Kicking, deleting their character, sending them to admin prison, muting them, forcing their character to sleep are all acceptable punishments for very minor infractions.
 
===What To Do If You're Banned===
*The first step is to wait and think about what you did. No, really; take a break and do something else so you can mull it over. Even if you're in the right, if you go berzerk and start berating the staff no one will care about your ban and it may even be lengthened. After you think about it and you still think your ban was unfair, ask an admin for the logs from the round you were banned in.
*After you've read through the logs, read through the rules that relate to your ban. Did you break any? If not, have you been skirting the rules? Remember that "toeing the line" is still counted as breaking the rules; even if you aren't breaking the rules in a literal sense, you may be breaking the spirit of the rules. If you still don't think your ban was just, continue to the appeal.
*Before you make your appeal, think about how long your ban was for. Was it for less than a day? If so, it's not worth appealing; generally a ban appeal will take at least a day to be processed. Now, how long into your ban are you? Have you waited a while? If your ban is more than a couple of days long, you'll want to wait until the next day to post your appeal. If at this point you're ready to go, get to the ban appeal page and create your post using the format provided. If you were a good boy or girl and got your logs, be sure to use them in your defense.
 
[[Category: Guide]]
[[Category: Regulations]]

Latest revision as of 22:24, 5 July 2024


The Rules

Important

These rules are enforced in addition to Global Policy. Read both, please. While global policy refers to general community guidelines, these are the actual rules for the server. As such, we will try to keep this relatively simple.

Summary

  1. Keep IC / OOC separate, adhere to minimal standards for IC chatter. Do not talk about the events of an ongoing round in OOC channels (discord, OOC verb, voice calls, etc) until it ends.
  2. Stay in character. Try not to break character to 'win'. You should not be entirely unafraid of all death / pain / discomfort.
  3. Make a well-rounded character. Your character should have pseudo-realistic limitations on what they are skilled at. Do not make Mary Sue's. Being a troublemaker is allowed as long as it is believable and not straying into the territory of griefing.
  4. Rounds are canon, with caveats; remembering prior rounds is fine, instigating is not. Avoid giving your friends unreasonable boons in IC without an in character reason to do so.
  5. Escalate conflicts reasonably. Consider what a conflict will do to your character / another's character; have justifiable and proportional IC reason if causing collateral damage or when inflicting mortal wounds.
  6. Avoid wordless ganking, even as an antagonist. An 'antagonist' is someone given a pass to otherwise ignore certain administrative precedents (e.g. making a believable and hire-able character); you are still here to portray a character and tell a tale.
  7. Do not exploit OOC factors for an advantage. Do not abuse bugs. Do not multikey (log on with two different accounts for the same round). Do not intentionally abuse OOC factors to ruin someone's day (waiting for someone to go AFK and then ganking them, type-baiting, etc).
  8. Punishments may be IC or OOC. You open yourself to IC but not OOC punishments by crew / admins acting as higher authorities if you cause trouble IC but not break OOC rules on roleplaying.
  9. Staff are still players. Staff characters get no special treatment.
  10. Adminhelp if you have a grievance or question. Do not lie in admin tickets. Do not attempt to enforce OOC rules via IC other than in cases of clear griefing. Do not assume that someone else getting away with something means it is allowed/not enforced - always ask if you have a question.
  11. Erotic content must be consented to by all parties. Erotic content receives grief protections but no world / IC protections. Keep extreme content off the server and do not go out of your way to harass people in regards to this content whether for or against.

Elastic Clause

Citadel RP is a roleplay-oriented server. No ruleset will possibly cover all cases, and as general as our rules are, there are cases that fall outside of them still. As such, administrators may intervene in rounds and grievances as they see fit.

Obviously, staff that choose to invoke this clause are held responsible for their actions.

These rules are worded for a roleplaying environment. We, however, are roleplaying in Space Station 13. We are not here to take all the fun out of the game; reasonable amounts of ‘fun’ will be tolerated, for the game would become not much more than a job simulator without it.

We’re all here to have fun, not fight and argue with assholes. Don’t intentionally ruin the game for everyone else on an OOC level, and use common sense. More times than not, we care more about what you are doing than what rule you broke. Acting in good faith can excuse a lot of missteps, while intentionally making others miserable will be punished regardless of rules being broken verbatim.

Immersion

  • Keep IC and OOC separate. If there is an issue, contact staff. Breaking the fourth wall to get even with something is not okay.
  • Netspeak: Adhere to minimal standards for IC chatter; do not use “netspeak” e.g. emojis, “lol”, “wtf”, “4head” in IC chat. Language, after all, is spoken.
    • IC text messaging like PDA/communicators is exempt from this.
    • Semantically digital languages like the AI/cyborg binary channel, and EAL are exempt from this. Other players, however, can and will make fun of you if you choose to talk like this.
  • Metacommunications: Do not share round information in OOC manners of communication. This is unfair to everyone else playing in the round.
  • External Information: Do not use round information gained from OOC communications in round unless explicitly stated to by staff.
    • Do not use information from adminhelps IC unless told otherwise. We do’nt want to have to tip toe to not “leak” round information to you; please don’t ruin it for everyone.
  • Deadchat: Deadchat is considered OOC.
  • (L)OOC: In game OOC channels are generally for clearing up OOC/mechanical confusion, e.g. having to afk for a moment, typos, misclicks, etc.
    • They are not for arguing about an IC case. Security can and should disregard someone claiming innocence in LOOC, as an example. If there’s a major issue, you/they can adminhelp. Abuse of the channel will result in a mute.
    • For urgent issues, using ((Hey this is a heads up.)) double parentheses notation is an acceptable thing to do in say/me/IC channels.
  • Do not use AI-generated text content in game. Reference images in your flavortext is fine. Writing your flavortext or RPing with LLM's or similar AI generators in game is not. As a rule of thumb, if we can tell it's AI, it's probably too AI for a RP community.

Roleplay

  • Stay in character: Try to stay in character at all times. Don’t do ridiculous things that your character wouldn’t.
    • Light amounts of messing about is allowed and encouraged, as we are still a video game. Just because your character is here to work doesn’t mean they can’t have a little fun while doing it. We’re not here to roleplay rigid military rank, and your character isn’t a robot.
  • On powergaming: Powergaming is defined, loosely, as ‘playing to win’. If you are trying to complete round objectives, kill the antagonists, or ‘win’, at all costs with no regards to roleplaying, you may be better off somewhere else. This may include but is not limited to:
    • Having your character unafraid of any and all death or pain and resistant to any torture
    • Having your character always willing to battle alone against a crowd of opponents
    • Rushing gun wielders unarmed with no regards to your own preservation
    • Having guns, medicine, and other powerful items every round with no real IC reason to do so
  • On character knowledge: Departmental knowledge is outlined in “Characters”. This more refers to general guidelines; keep in mind what your character does/doesn’t know. The average spacer probably doesn’t know where to find, say, an agent’s uplink, or have exact coordinates of specific pieces of loot memorized to teleport at a whim.
  • On cloning/revival: Cloning and revival technologies are in flux on the server out of necessity. Death and pain should not be ignored due to their presence; they are only so lax at current time for the benefit of our community and culture.
  • On Leaving the Round: While it's unreasonable to try to force people to play what they don't want to play, please avoid leaving the round to dodge IC punishment for your character's actions. It's not fair to the other people who went out of their way to handle whatever you did.
    • Avoid ghosting out of your character unless absolutely necessary. There's already systems in place to allow you to leave the round properly.
    • While we do not mechanically restrict leaving and coming back on the same character, it should not be used to do things like swap jobs, heal yourself, and similar IC actions. Please see Administrative Precedents for more information.

Characters

  • Make well rounded characters: Your characters should have strengths and weaknesses. Take what species you’re playing as into consideration. Avoid “Mary Sue”s, aka characters that are inexplicably/unreasonably perfect at everything with no flaws.
  • Keep your characters separate: It is unfair to others if you were allowed to play a whole “cast” of characters fit for everything, and share knowledge/grudges amongst themselves in an attempt to bypass our rules on escalation/grudges/knowledge. Here are some examples;
    • Playing siblings is okay.
    • Playing characters who know each other is okay.
    • Leaving mid-round to bring in another character to handle a situation in your character's favor by overruling conflicts is not okay; an example of such is joining as a security character to clear another one of your character's name.
      • Switching characters to respond to an ongoing crisis, such as swapping from a medical character to an engineer character to handle a Code Orange, is allowed.
    • Having all of your characters automatically grant someone favors, or grudge someone as a group is not okay, and will usually be considered as metagrudging.
  • (Departmental) Knowledge: Keep knowledge reasonable. A twenty-five year old wouldn’t be some genius with multiple PhDs. Many things are harder to do in character than they actually are to do in the game, e.g. things like surgery isn’t ICly clicking a button ten times. Avoid characters that know everything.
    • This is usually relaxed and not overly enforced when there’s not a lot of people around. We don’t want skeleton crew hours to be unplayable.
    • While many species exist that can live well past normal human lifespans, we still require those characters adhere to reasonable knowledge guidelines; No 'my character is 300 years old' perfect do-it-alls.
    • As rounds are canon, characters should not be a permanent Head of Staff for more than one department at a time. Swaps are possible, but should be done in a reasonable manner.
    • For the purposes of these rulings, the Captain/Facility Director and the Head of Personnel are in the same department: Command. Playing both frequently is allowed.
    • The general guideline is that a character should have at most proficiency in two unrelated fields. Most people wouldn’t be heads of multiple departments, or able to do every job on the station.
  • Miscreants, troublemakers, and criminals: Characters with “unfavorable” (from the PoV of authority) backstories are allowed and encouraged. Getting caught IC still incurs penalties as always.
    • You still need to get hired. Your employer wouldn’t hire someone who wouldn’t be able/willing to work. No “my character is insane” antics.
    • Backstory cannot justify escalation alone. No characters that attack security for the fun of it, or “evil” characters that join to break things.
  • Flavor Text: Your flavortext represents what can be visually observed by looking at your character. Try not to dump backstory, and keep it (relatively) reasonable.
  • On backstory and species: Character customization and creativity is one of our environment’s features. You may design custom species/genemodded characters with unique planets/backstory within reason. Some specific caveats are as follows;
    • Major species already have lore. No going against what the agreed upon narrative is; adding to it in reasonable manners (like saying there’s some outpost somewhere that you came from, etc.) is usually allowed.
    • Whitelisted species have specific requirements for lore. Make sure you’re in adherence with them.
    • Custom species may either be 1. a genetic modification of a major species 2. a minor race of your own creation with no more than a few systems. The galaxy’s major species are already set; there won’t be any Mary Sue races popping up out of nowhere without prior agreement.
    • Lore submissions: We encourage lore submissions if you wish to expand upon our universe. This is one way to “canonize” your minor race.
    • On Important Characters: Characters integral to the lore, e.g. leaders of major species factions, CCOs, any kind of royalty, and generally any in-universe celebrity would find little reason to be working on the station. They may not be used as 'daily driver' characters.
    • Heads of Staff: Heads of Staff must have written and complete security / medical / employment records.
  • Naming policy: We are very lax on naming policy. Here are some general guidelines;
    • It is recommended to stick to your species’s standard naming style (firstname lastname for humans, etc). Try to have a reason if you choose otherwise.
    • Character names may not contain nicknames. (e.g. Jason “Jay” Brooks)
    • Character names may not contain hierarchal, gender-based, or job related titles, like Duke, Lord, Dr., Mr., Capt., etc.
    • Try to initial middle names. (Kara Mary Snyder --> Kara M. Snyder)
    • Human names may not be a mononame. (e.g. “Jack”).
    • Clowns, mimes, theatrical roles, and gimmicky event roles are usually exempt from naming policy. Keep it tasteful.
    • You may not name your character after real life celebrities, politicians, or other famous person(s) from popular culture/video games.
    • Avoid cartoony names like Firstname ColorFur and similar; it breaks suspension of disbelief.

Continuity

This is a section undergoing trial. Continuity is hard to get right, and we may adjust this as necessary. Keep it tasteful and avoid going out of your way to ruin somebody’s day.

Citadel RP has round continuity. This means that events of previous rounds are canon in-universe unless stated otherwise. This comes with a few minor caveats:

  • Instigating: Avoid instigating conflict cross round in a way that heavily disrupts another person’s round. You should not be leaping for someone’s throat the moment they arrived or trying to bait them into a fistfight. Keep it reasonable.
  • Favors: Avoid giving your friends, in character or out, overly powerful benefits without sufficient IC reason to do so. Whether or not this is persecuted in-character depends on what your reasoning was and whether it was plausibly in character.
  • Grudges: Avoid acting on grudges in a way that ruins someone’s rounds. We do not want to see Pathfinders kicking someone off the team over a personal dislike alone, nor do we want to see cargo-techs denying departmental gear for no good reason.
  • Relationships: Character relationships are going to happen, especially given the nature of the server. The rules above apply regardless; expect higher scrutiny from Central Command if you main a head or security role.
  • Violations: Violations of the above may be persecuted IC or OOC depending on severity and reasoning. Keep extra care to not overdo it as a head of staff.
    • By necessity, administration will generally side against instigation of needless cross-round drama if faxed, especially when involving positions of power.

Conflict

Conflicts, including physical ones, may be started by characters if there is sufficient IC reason to do so. Keep in mind the limits of your character; most characters are likely working for an employer, and someone overly violent/destructive would not be employed for long.

  • Escalate conflicts reasonably: You should be using reasonable force and consider what your character would do in response to a scenario (or what they would be willing to do when instigating).
  • On lethal conflict: Avoid lethality/maiming where possible. Murder is a serious crime in character, regardless of revival technologies. Your character would not be killing their coworkers over the average disagreement!
  • Have a reason for collateral: Avoid causing collateral damage to uninvolved and to critical infrastructure for the same reasons as above.
  • Keep IC and OOC separate: Your characters’ feelings and your own feelings should stay separate. The same should apply to everyone around you. Do not OOCly harass other players for their IC actions, and do not metagrudge by acting on your OOC dislike of someone using your IC character.
    • Targeted IC harassment over OOC grudges (and vice versa) is taken very seriously. Just don’t. If you think someone is doing it, adminhelp; do not fight fire with fire.

Antagonism

  • Antagonists: ‘Antagonists’ refer to anyone given a pass to act as a special, and usually opposing role. This can include pirates, shapeshifters, cultists, or even a malicious diplomat.
  • Roleplaying an antagonist: Antagonists are not exempt from the rules. Your role gives you a reason to act beyond what an ordinary crewmember would, or in some cases, could. While you often have laxed escalation and de-facto motives to cause problems, it is not a free pass to kill and destroy anything you please.
  • Avoid ganking or playing hero: The point of antagonism is not to “win” by killing either side. Wordlessly killing anyone in your way, or wordlessly charging perceived antagonists to kill/subdue them without good IC reason is not a good idea.

Mechanics

  • Bug abuse: Bug abuse is defined as knowingly using unintended behavior. This is punishable by staff depending on severity and intent.
    • We’ve all done something funny with broken game mechanics before. Staff are generally going to be lenient in relatively harmless abuses of bugs.
    • Open source projects rely on players to find bugs. You will not be punished for finding a bug alone. You are encouraged to find and report bugs.
    • Do not abuse bugs to gain an upper hand in IC conflict, especially mechanical conflict/combat. This is the one case which will be persecuted severely, as it erodes trust and ruins it for all parties involved.
  • Multikeying: Do not multikey without admin permission. This means not playing multiple characters at once, not logging in with multiple accounts as once, so on and so forth.
  • Griefing: Do not intentionally and knowingly abuse OOC inconveniences to gain an upper hand in IC, or perform IC actions with the express intent of causing OOC upset.
    • Try not to grief those experiencing said inconveniences, like stealing from someone whose connection suddenly dropped. Pressing IC reason may alleviate this.
    • This is relaxed in some cases where enforcing this makes less sense than not enforcing it. Act in good faith.
  • Fourth Wall: Just because something is possible in the code, does not necessarily mean it makes sense in IC or that you should do it. Due to how open-ended this rule is by nature, we will list all commonly enforced tidbits as follows:
    • Item naming: The loadout system as well as many in-game systems allow you to rename and 'refluff' item names and descriptions. Much like flavortext, this should be what an arbitrary person can glean from inspecting the item. Do not infer information, feelings, or thoughts onto the reader that the reader should not know factually by looking at the item. An example of a violation would be "Bob Joe's duster jacket" as an item name.

Punishments

We seek to handle issues with IC intervention over OOC punishments like bans.

  • IC punishments: These are directed at a player's characters. Punishments carried out IC include administration faxing to assert a certain directive sanctioning a given character. Character-specific jobbans or sanctions are also considered an IC punishment.
  • OOC punishments: These are directed at the player. They involve less faxes and roleplay and more admin-tickets. OOC punishments are handed out more for server rule breaches than IC regulation breaches. Keep this distinction in mind.

Administrative Interference

  • Staff are still players: Characters played by administrators, developers, event staff, etc, are part of the game world. They receive no special treatment in regards to IC conflict.
    • Staffmembers are not allowed to adopt world-critical characters as their regular, everyday characters.
  • Keep character: In round staff interference, such as item spawning, does not receive automatic immunity from IC reactions.
    • e.g. if someone has an adminspawned weapon, security is allowed to act as usual. We would have given them a permit/faxed a directive if immunity was intended.

Grievances / Adminhelps

If you see a rulebreak, admin-help it. Act in character while in character; do not attempt to backseat administrate or enforce OOC rules IC other than in cases of clear grief.

  • Adminhelp if an issue arises. Do not wait until the end of the round. Staff are here to assist.
  • Fax. IC problems like requesting assistance/directives should be faxed where possible.
  • Pings: If admins are unavailable, whether for adminhelps or faxes, pinging @RP Staff on the Discord is allowed
  • Discord tickets: Issues should be brought up in a Discord ticket if the round in question is already over.
  • Old grievances: There is no set statute of limitations for taking a problem to administration. That said, it’s worth considering whether something is still worth bringing up after too long of a time has transpired. Staff have the right to disregard very old cases if they find little reason to press the issue.
  • On truthfulness: Lying in an adminhelp is a terrible idea. It tells us we cannot trust you, which makes whatever you did magnitudes worse because now we have to second guess your stated intent.
    • Lying is obviously allowed in character. It may result in consequences for you if found, but isn’t the same as lying in an OOC adminhelp. If we want straight answers out of someone, we’ll use an admin ticket. Faxes are IC.
    • Forcing admins to drag out information piece by piece or otherwise intentionally misrepresenting situations is equivalent to lying.

Sexual Content / ERP

ERP (Erotic roleplaying) is allowed on Citadel RP, with these caveats. Anything considered too indecent to do in public of a normal, urban area, falls under this clause.

  • ERP is not required. If you are here to play and have no interest in it, say as such in your OOC notes. You will not be harassed or otherwise discriminated against; we are a server with ERP, not a server explicitly for ERP.
  • OOC consent is required. Do not harass those who do not want ERP for ERP, and do not be excessively creepy. We take this very seriously. Seriously, just don’t.
  • ‘Extreme’ content should be isolated. Keep things like OOCly agreed upon non-consensual scenes, as well as kinks considered graphic (filth, gore, etc) or extreme private.
    • It is required to use the anti-ghost subtle verb in these cases as well.
    • Realize that if taken at face value, a character doing these things (especially fully non-consensual scenes) would be swiftly expelled from the station. We only allow these scenes to happen on server at all for convenience / not requiring people to take it to Discord, not because it is ICly allowed. Intentionally dragging these scenes to public eye for the sake of drama is punishable by character removals or server bans.
  • ERP with creatures that cannot consent is not allowed. Outside of two players engaging in consensual non-con content, ERPing feral creatures (ie; animals or other simple mobs that are unable to consent) is not allowed.
    • Player controlled simplemobs are able to consent, and are not affected by this rule. However, this content is generally considered 'Extreme', and falls under the provisions of that rule.
  • ERP receives no world protections. People are allowed to interrupt you given a good IC reason, such as you being on duty and needed, or security enforcing public indecency regulations. Your scene is not central to the in-game world.
  • ERP does receive protection from grief. Interrupting ERP for no good IC reason is grounds for admin action. This especially applies to private roleplay. Do not attempt to grief ERPers for no / flimsy reasoning.
  • Do not intentionally abuse ERP mechanics for gameplay. This means no size-shifting to try to step on people mid combat (this likely breaks character rules as well, most of the time), no abusing vore to round-remove or heal people in conflict. This is generally enforced by the code team through balancing and design, but is a rule nonetheless. We have some mechanics that are only really useful for ERP; Don’t ruin it for everyone.
    • We reserve the right to ask anyone using sub-standard sizes to avoid causing mechanical problems / engaging in mechanical conflict. It doesn't make sense for 16 pixel tall humans to run around beating people with batons, and the coders shouldn't need to spend their limited time dealing with it. You are allowed to partake in the game, but you are not allowed to make others miserable with your small size.

Footnotes

Some of our rules may seem arbitrary. Here’s a short collection of “why”s.

On code balance, development direction, and roleplay

Many things, like some of the issues listed below, stem from the server’s code maintainers progressing code direction in a specific way to better cater to our overall goal.

Things like player death may be avoided, as a design choice. Medical systems are not as realistic as they are in real life. Science is going to be a constant work in project, and you’ll often have to shoot a simple mob human that to you, a player, you know as being a NPC, but in character, they’re still another human.

Should you take everything in the code 100% seriously? No. You aren’t required to mourn IC for the next few days because you shot a simplemob cultist spawned by a careless deprecated event that we (developers) have yet to change. You aren’t required to write out in a /me cutting each wire of a door. In some cases, you should take the enjoyment of the code-base we build for you (as well as the enjoyment of your fellow players) over a roleplay technicality.

But neither should you completely ignore the ramifications of a scenario or action simply because it’s glitzed over for the ease of use of players. Your character should not be seeking to kill hundreds of mercenary simplemobs; they are still human. Science takes a button to operate, and brain surgery is as simple as ten clicks, because this is a roleplaying game. In character, however, they are not nearly as simple as that, and you should reflect that in your actions.

The developers have a third of the burden of responsibility of encouraging IC behavior. The playerbase and the administration have the other two thirds. Not one of the three groups can do it alone.

On cloning, revival, the medical system, and taking IC death seriously

Revival, cloning, and mirror technology in character is absurd. We have yet to change it. We may never change it, for the simple reason that we are a server with a lot of slice of life roleplayers.

Sitting out in deadchat is unfun, and dying from a single lucky stab of a knife in five minutes isn’t what the game should be about. We design the codebase with a mixture of realism, but also playability. It should suck to get injured, yes, but this is a video game above all.

Try not to act like death and pain is meaningless in character, though. Simply because we make it less brutal than it would be in real life doesn’t mean it isn’t a problem for your character. Do not abuse playability to powergame. It ruins the game for everyone.

On powerful world characters, heroes, antagonists, and their restrictions

Everyone wants to be the center of the story, and that is fine. For many, it is fun to play someone of importance, and to be the driving force behind a story.

However, the fact of the matter is that not everyone can be the key to the story. Not everyone can star in every event, and it’s unfair for us to wantonly allow someone to play an important world character, like a faction leader, a central command officer, and similar.

Powerful world characters are restricted to staff discretion and events for this reason. Usage and authorization of them by staff are reviewed by other staff where available, and perceived abuse should be brought up for discussion. </div

On the limits of allowable erotic roleplay

Administrating a server with ERP is not fun. You get a lot of complaints about what should and shouldn’t be acceptable.

We are not here to police your kinks. That would be unreasonable, unfair, and soul-crushing for our staff beyond measure.

We, however, ask that you keep anything considered extreme or undesirable for the majority to ghost-invisible emotes, and in extreme cases, may even ask you to take it to Discord.

This clause has not had to be exercised many times over our server’s journey, but we have to consider the majority of our playerbase, not just one or a small group of people.

Furthermore, erotic roleplay does not halt the game’s world. While we do not allow griefing ERPers on purpose, the show must go on; your character doesn’t get an exception simply because they’re getting into private business. If you don’t wish to be interrupted, consider taking your scene off server. It is frankly not physically possible for another player or for an event to interrupt you then.

On powerful species, mechanics, items, and their lore

The premise of this is basically the same as the footnote “On development direction”. Some species are far more powerful in lore than we would allow in code. Some species are far more powerful in code than we would allow in lore.

We ask you take things with a reasonable grain of salt. Simply because a thing is not possible in code does not mean it is not possible in character. Simply because a thing is possible in code doesn’t mean it’s a good idea in character.

Retrieved from "https://citadel-station.net/wikiRP/index.php?title=Policy/Rules&oldid=4088"