Server Rules
For more in-depth explanations of rules and FAQ, please read the Rule precedents document
Core Rules 0). Take these rules as they are to be intended and not as they are written literally. 0.1. Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly.
1). Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This means it is important to do what is expected out of your department and not what would be expected out of other departments.
1.1. If you want to build mechs, play roboticists. If you want to hunt for antags and uphold space law, play security. This is to ensure all players can have a fun shift and have a role to fill. This is not intended to limit what is possible on the server but to provide structure for everyone. 1.2. Opt-in for roles you intend to play or seek an IC way to change your job. Failure to attempt to do the most basic of duties for your role may result in a job ban. [A list of basic duties can be found here]. While transferring to another department and doing another job is acceptable, being a know it all for multiple departments is not. 1.3. If you do not wish to be a role or antag, ensure you set it to never in your occupation preferences and/or request a ban from said role or antag. Changing your job preference settings to “return to lobby if preferences unavailable” will prevent you from being assigned a random position. 1.4. Players' knowledge of the game is not limited by their job. However, using knowledge of antags and round types without IC justification is considered metagaming. For example, it is acceptable for a clown to know how to build a conveyor belt for a prank. It is not acceptable for a clown to know that xenomorphs are weak to fire and rush to make a flamethrower.
2). Malicious acts like griefing, metagaming, killbaiting, banbaiting, powergaming, self-antagging, greytiding, validhunting (along with calling people and silicons valid without proper cause), and exploiting can become bannable offenses if occurring regularly or if the infraction is serious enough.[See the glossary here].
2.1. Multi keying, ban evasion, cheating, blatant intent to grief, and RDMing are all permanent ban offenses. 2.2. If playing with someone that is at the same location as you, alert us so we may take note of it. Otherwise, we may assume they are you. 2.3. Antag rolling, or round-start suicides that appear to be antag rolling, may result in an antag ban if occurring frequently enough 3). Sexual content is strictly prohibited. This includes content like photos/websites/Erotic Role Play (ERP) and applies to the server, Discord, and forums. Sending unsolicited sexual content to another player via direct messages will also result in a ban.
4). Hate speech is strictly forbidden. Using the Discord, the SS13 server, or the forums to threaten a group of people or to propagate racial and otherwise prejudiced slurs or stereotypes is a bannable offense. We take this seriously and want to create a server that is welcoming to all people. This includes variations or misspellings of slurs. SS13 is your character’s workplace; if you would get fired for saying it in a modern-day office setting, you shouldn’t be saying it on the server.
5). Discrimination towards in-game sub-species and silicons is acceptable in moderation, but attacking them or otherwise preventing them from playing the round is not. Additionally, terms that are based on real-life slurs are not allowed.
6). Do not spam, advertise, or paste lengthy and/or inappropriate copypastas.
7). Keep IC content in IC, and OOC content in OOC. This means no IC in OOC (ick ock) and vice versa.
8). Revealing information about the current round in OOC, Discord, or the forums (metacomming) is strictly prohibited. Wait until after the Round End screen to discuss the round or file a report.
9). Avoid antagonizing players and staff via the Discord, Forums, or through OOC/deadchat. While expressing frustration about in-round events is acceptable, ganging up on fellow players is not.
9.1 - IC insults are fine within reason, but harassing other players repeatedly throughout the round or using OOC insults IC is not. 10). Each round exists independently of all other rounds. While friendships persisting through rounds is okay, using experiences from other rounds to give an advantage or disadvantage to other players is not permitted.
Returning From The Afterlife 1). Do not use information obtained while dead or from a previous life upon returning to the land of the living.
2). Cyborgs and other creatures that are created with a character’s organic brain (i.e. not a positronic brain) retain all knowledge of events that happened before the procedure while they were living. Rule 1 still applies to information obtained while dead.
2.1. Antagonists who undergo forced cyborgization retain their antag status and objectives but must prioritize their law set. This prevents borgs from attempting to be unborged in most circumstances. SSD/AFK Player Interactions Note: SSD characters are players who are disconnected or AFK. It is possible for players to return to SSD bodies. Players become catatonic when they take a ghost spawner role or commit suicide. Players are NOT able to return to these bodies without admin intervention.
1). Do your best not to interact negatively with SSD/AFK players. Moving them to safety is acceptable, but killing, looting, or otherwise griefing them while they are away is not.
1.1. If the player in question is an antag’s target or they are being secured by security, interactions to finish what is required of your duties/objectives are always acceptable. 1.2. Ahelping about an SSD/AFK player may grant an exception to this rule. 2). Rule 1 does not apply to players that are catatonic. Although needlessly killing or harming catatonic players is discouraged (and will probably get you hunted by security), harvesting their organs to save another player is acceptable.
Escalation Clause 1). Escalation resulting in murder is only acceptable within reason. If your life is in danger, you can always fight back lethally, or if a conflict with the other player has lasted throughout the round with multiple fights. In most cases, fights end when one party enters critical condition or is otherwise incapacitated. Theft, break-ins, demotions, destruction of property, getting pranked and other inconveniences are not reasons to murder another player or put them into a life or death situation. Ask what a rational person would do and act accordingly.
1.1. Expect to receive the same kind of treatment and escalation that you give out. 1.2. If the other party during an altercation dies or is seriously injured, work to get them healed or revived. 2). If you act like an antagonist, expect to be treated like one and be held liable for your actions both IC and by admins.
3). Over-escalation of fights is also unacceptable. Over-escalation is, in short, doing more damage to someone than is required to resolve an issue or using violence instead of words to solve an issue.
Examples being:
Killing someone during a dangerous fight when they could be placed into crit and healed or ignoring the opportunity to use non-lethal force when available. Placing someone someplace they will surely die, like disposals when crit, space, in shuttle landing zones, or other gibbers. Delimbing someone for doing minimal damage to you. Breaking into a department and attacking someone when they try to remove you from the department instead of asking for what is needed. 3.1). While using lethal force is allowed in some cases of self-defense, actions that jeopardize the lives of other players or could cause massive damage to the station (e.g. max caps) is considered over escalation, and you will be held accountable for deaths that occur due to negligent behavior. This rule applies when committing acts that will likely cause mass casualties to eliminate antagonists.
Command/Security/Silicon Responsibilities 1). The following jobs: Captain, HOP, HOS, CE, RD, CMO, QM, and AI should ahelp when they need to leave. This is to ensure a replacement can be installed (Your body will be offered to ghosts or your character will be deleted and the job slot reopened) for continuity of the round. Your intent to leave should also be made known to other command staff if possible. If no staff are available to offer your body to ghosts, you should designate another player as your replacement after ahelping.
1.1. These roles must exhibit some competency. Lack of this can result in a job ban. Command roles are designed to lead and manage departments first and do second. They are not intended to become do-it-all members of their departments. 1.2. Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the chain of command when the new player arrives. 2). In the absence of a captain and CentCom appointed acting captain, the Head of Personnel or Head of Security must serve as acting captain or split the duties of the captain between themselves. In the absence of a captain and CentCom appointed acting captain, HoP, and HoS, the other command staff have equal standing in determining a new acting captain among themselves.
2.1. Only command staff may serve as acting captain. Acting departmental heads and regular crew may not serve as acting captain. 2.2. The only item acting heads may take from the head’s office is the command headset. Unless there is a dire emergency, no other items should be removed by non-antags. 2.3. An acting captain may fill in for decisions that require the captain’s authorization, but may not run the station and its departments, nor are they privy to the captain's equipment or access outside of the command headset and nuke disk. The captain’s spare ID can be used to run the HoP line in the case of a non-HoP acting captain but should not leave the bridge. 3). Heads of staff, acting heads of staff, and security should not abandon the station without permission from CentCom. This includes going to Lavaland, space exploration, bitrunning, and entering the gateway.
4). We adhere to our own version of [space law].
4.1. While the majority of this is a guideline, we expect things to be applied reasonably. Giving someone a ten-minute brig timer for slipping the captain is an example of things not being applied reasonably. 4.2. Abusing crew as security is never acceptable. 4.3. Authorization for permanent punishments (including executions) should only be followed if the authorization was given by the correct authority. For example, a sec officer should not comply with execution orders given by an HoS when a captain is abroad the station. 4.4. Security must use nonlethal force unless there is reasonable suspicion that the other party is armed (e.g. breaking into the armory), lethal force is used upon them, or the use of nonlethal force is impossible (e.g. Hulks). See “Use of Deadly Force” under Space Law for more information. 4.5 Ensuring prisoners receive timely revival and proper medical care is the responsibility of everyone in the security team. Unless an execution was authorized by the captain, this applies to any player killed by security. Detaining players who are dead or will likely die from injuries without attempting to provide medical care (e.g. throwing a prisoner in critical condition in a cell) is a violation of 4.2. See “Prisoner Medical Care” in Space law for more information. Repeated negligent deaths may result in a role ban. 5). We adhere to our own version of [silicon and drone] policy.
5.1 Those that upload laws to silicons are responsible for what said law causes. 5.2 Ordering silicons to commit suicide or any actions that would be considered grief as a non-antag is strictly prohibited. Silicons who are given such orders should ahelp before carrying them out; however, the person giving the command will still be held responsible. 6). We now adhere to our own [standard operating procedure] policy.
6.1 Calling the shuttle on red alert to end the round faster despite there being no significant threats to the station will likely result in it being recalled. Antagonist/Lavaland/Ghost Policy 1). Antagonists exist to move the round forward and make things interesting and fun for everyone involved. Excessively recalling the shuttle to prevent the natural end of the round in order to do your objectives should be avoided and may result in moderator intervention. If you complete your objectives, you may pray to be given additional objectives.
1.1. Do not needlessly kill those you do not need to outside of your objectives and simply because you can. This includes destroying silicons. Things like covering up evidence, dealing with pursuing security officers, ‘Good Samaritans’ on your tail, and removing a witness, are always acceptable examples. Ahelping ideas for gimmicks may grant an exception to this. 1.2. Killing players outside of rule 1.1 must directly further your goal, and you cannot permanently remove these players from the round. For example, killing an engineer to gain departmental access with the objective to steal the CE’s blueprints is acceptable. Killing an engineer for her insulated gloves or access to the prolathe without an objective in that department is not. 1.3. Do not spawn camp or prevent others from entering the round safely. 1.4. Do what is needed for your goals. Destroying half the station when you only need to steal research is an example of going extremely overboard. Causing chaos in a department with a bomb is okay but destroying half the station is not 1.5 Team antag objectives take precedent over solo antag objectives. 2). If you become an antagonist and do not wish to be one, ahelp so that we may set you up with another role and/or give your antagonist status to another player.
3). Creatures and those turned into creatures maintain their antag status from their previous form. See the “Returning from the Afterlife” section for more information.
4). Ghost spawner roles must follow their flavor text upon taking said role. These roles are meant to allow players to return to the game, and their slots are usually limited. Intentionally wasting spawner slots (e.g. repeatedly suiciding as spawner roles during one round) may result in a ghost role ban.
5). Sentient animals, critters, and creatures are not valid to be killed by the crew simply for existing -- they are players too. However, if they are causing trouble, this protection is waived.
6). Lavaland spawner roles (such as Ashwalkers and Free Golems) are meant to allow players to return to the game and are only considered valid if aggressive toward crewmembers. See the “Guide on acceptable killing” section at the end of this document.
6.1. Lavaland spawners who enter the station must be peaceful and are held to stricter standards for escalation and roleplay than when on Lavaland. Spawners may not use meta knowledge to seek out the Lavaland mining base and may only enter if invited by crew members. Spawners who are hostile/ willingly impede the station are subject to a ghost role ban. 6.2 Spawner roles must follow their flavor text and treat their spawn location (e.g. Charlie station) with the same regard as the main station. Intentionally destroying your spawn location without sufficient IC reason prevents players from rejoining the game and will result in a ghost role ban. 7). Rules 6 and 6.1 do NOT apply to any Syndicate spawners. These roles are permitted to kill Nanotrasen crew members on sight and similarly may be killed by NT crew.
7.1 Spawners at the Syndicate base in Lavaland are never permitted to leave their base. 7.2 Spawners at the Syndicate ship are allowed to leave their base but must not seek out the Nanotrasen station. These spawners are never permitted to intentionally approach or board the NT station. If you accidentally find the NT station you are expected to leave immediately. 8). If you disconnect as an antagonist, we will be forced to offer your body to ghosted players after ten minutes without reconnecting. Members of team antagonists (e.g. nuclear/clown operatives, blood brothers, head revolutionaries) must notify admins that they are leaving through ahelps.
Admin Interactions 0). Our staff is composed entirely of volunteers who work to make Fulp a welcoming community to all players. While it’s okay to express frustration with admin interactions, doing so in a way that is aggressive or harassing will result in a mute or a ban. If you harass staff, expect consequences to come as a result of your actions or your issue to be discarded.
0.1). Do not send unsolicited Direct Messages to staff via Byond. If you need to contact staff, verify on Discord and use the #ask-mods channel or the forums. Sending unsolicited DMs via Byond may result in a permaban.
1). Ahelp as soon as possible. Waiting can make things harder or even impossible to look into. We do not know what we do not see. The moderation team exists to help. Ahelping can bring things to our attention we may miss.
2). Provide as many details as possible. Generally, your ahelp should include the name of the offending character and a brief description of what happened. This makes it easier for us to figure out an issue. Bad ahelp: Sec arrested me for no reason Good ahelp: Sec officer John Smith put me in a cell with no timer for trespassing into science, and I’ve been here for 5 minutes already.
3). While players are encouraged to ahelp problems they have in-round, misusing ahelps (e.g. complaining about round or asking to be an antag) is not acceptable. If your ticket is rejected or marked IC and you wish to have it reviewed, file a staff report on the forums as additional tickets regarding the same issue will be ignored. Misusing ahelps clutters tickets, and repeatedly doing so may result in notes or a ban.
4). Do not lie in ahelps as we can verify any claims made via player logs. If you are unsure of how an event transpired, you are encouraged to look through your logs for verification. Lying in ahelps will result in a ban.
5). Respond to Admin PMs as soon as possible so we know you aren’t ignoring the ticket. Even a ‘one moment’ will suffice.
6). In-character communication with admins should be done through the prayer option under the IC tab. Prayer can be used to obtain in-game items at the admin’s discretion. This includes TC trades. Ahelps should not be used in place of prayers for IC issues. Praying does not guarantee a response and may result in being smited. Spamming prayers may result in a mute/smiting. Do not ahelp if your prayer is not answered.
| Admin interaction | Event |
|---|---|
| Ahelp | Other players breaking the rules (e.g. suspected self-antag, IC in OOC, hate speech, theft of dept equipment, etc.), reporting a bug/ glitches, leaving as a dept head, asking for antag status to be removed, confirming rules about large-scale antag actions |
| Mhelp | Asking about game mechanics |
| Prayer | TC trades, requesting items, asking for antag status when not already an antag, asking for additional objectives |
| Forum Post | Reporting other players when no admins are online, ban appeals |