Note: This document is meant to supplement the Core Rules. If there is any question about an inconsistency between the Roleplay Standards and the Core Rules, the Core Rules take priority. Although roleplay standards may be cited in player notes or bans, this document should not be used as justification of otherwise rule breaking behavior and should not be cited in ban appeals.
0). Fulp is a Medium Role Play (MRP) server, but we also pride ourselves on being beginner-friendly. This means that while we uphold these standards for roleplay, exceptions may be made when it is necessary to explain mechanics to beginners.
1). Out of character (OOC) content in the in character chat (ICC) is prohibited (see Core Rule 7). This includes using OOC terminology when IC alternatives exist. Examples of OOC terminology include, but aren’t limited to, antag, ahelp, powergaming, and admins.
2). Say: should be used for things your character is saying, and me: should be used for actions your character takes.
2.1). Use of emotes also falls here, like saying ‘ :) ’ in the chat. Occasional use of things like ‘lol’ and ‘brb’ are more acceptable however unless used too often. This does not apply to PDA messages. Players are instead encouraged to use me: to emote in character
2.2). Intentionally speaking in me: to get around deafness or language barriers between characters is not allowed.
Unacceptable: me: wait a second/signs wait a second
Encouraged: me: nods, holds up 1 finger
3). Players are encouraged to use unique and creative names, but names should not be sexual or have racist connotations. With the exception of clowns, names that break immersion by being overly silly, real-life celebrities, or historical figures should be avoided. Characters with overly inappropriate names are subject to change at the admin’s discretion.
3.1 Names should allow crew and admins to easily identify players. Mononyms should be sufficiently unique to avoid confusion with similarly-named characters.
1). Job changes should be done by the Head of Personnel and be reflected on the ID. Any job-specific equipment and uniforms should be returned to the appropriate department.
1.1). Crew members are expected to attempt the basics of their department. If you do not know how to complete your job’s essential tasks, you should ask other players and your department head for assistance or request a job change from the Head of Personnel. Ahelping or using the #Mentor-help Discord channel is also appropriate so long as metaknowledge is not revealed.
2). Crew members are expected to listen to their department head when given reasonable orders. While it’s okay to question your department head, ignoring their requests or insulting them may result in a demotion at the department head’s discretion. Crew members should accept demotions gracefully and are not allowed to forcefully resist a demotion.
Acceptable: Asking the Chief Medical Officer why they are requiring doctors to perform surgeries on operating tables, bringing up organ decay.
Unacceptable, possible demotion: Refusing to comply after the CMO addresses these concerns
2.1). Alterations to department areas (e.g. building additional stasis beds, removing walls) or actions that will affect the entire station (e.g. adding non-standard gasses to the distro) should be approved by the applicable department head BEFORE they are completed. If your department does not have a head, seek approval from the captain or another knowledgeable member of command.
3). IC complaints about department heads should be brought up to the captain when possible. It is never acceptable to lethally attack a department head over disagreements or demotions (see Escalation Clause 1).
4). Crew members are expected to communicate requests and exhaust all other options (e.g. PDAing department heads, contacting the AI, and using departmental request consoles) before breaking into any department. See Core Rule 1.6
5). Crew members should be considerate of their co-workers and avoid intentionally making projects more difficult for them in shared space. This includes things like making significant changes to the piping in atmospherics without consulting other atmos techs, stealing other roboticists’ mechs, or interrupting players who are using the autholathe.
5.1). This also applies to public areas such as the hallways. Intentionally dirtying public space (especially with blood as it spreads disease) should be avoided without an IC reason to do so. This includes oxygen tank suicides.
6). Departments are allowed to protest and conduct work stoppages, but must do so peacefully and in a way that won’t ruin the round for other players. For example, miners refusing to mine until advanced mining is researched is acceptable, but destroying the shuttle console to prevent others from doing so is not.
6.1). Free Cargonia is acceptable on revolution rounds ONLY. Participating in self-antagonistic behavior (such as ordering munitions or attacking security) in other round types OR when not converted to the revolution will result in a ban.
7). Access to a department does not mean authorization to be there or use their equipment. Unless they are overruled by the captain, the department heads have the final say in who is allowed in their department. Crew are expected to leave restricted areas peacefully when asked to do so.
8). The Gateway is a restricted area, and the captain (or acting captain) has a final say on when/if access is granted. Obtaining unauthorized access is considered powergaming and self-antagging (See Core Rule 2).
9). Antagonists deserve a fair chance at winning, and security officers need to be able to do their job. While helping a player who is being attacked is allowed, intentionally seeking out antags as a non-sec role is not. Generally speaking, you shouldn’t leave your department to help as a non-sec role.
9.1). Captain and other department heads (besides HoS) are non-sec roles and should not validhunt under most circumstances.
9.2). Possession of weapons without sufficient IC reason is not allowed. The presence of antags on the station is not sufficient IC reason.
10). Griefing or targeting security because your character believes all cops are bastards is not acceptable as a non-antag. Security is a stressful role, and if you’re acting like an antag, expect to be treated like one (and bwoinked for it).
11). Taking advantage of logged-in consoles (especially those in the bridge) is not allowed. This includes using ID consoles to grant yourself extended access, purchasing shuttles, opening maintenance access, clearing security records, and calling or recalling the shuttle.
11.1). Using logged-in consoles to make prank announcements is acceptable so long as the announcement is in line with other core rules.
12). Miners and other players who are inviting lavaland spawners to the station should make an effort to inform the Head of Personnel or Captain before doing so.
0). We follow our own version of space law and standard operating procedures. Security members are expected to follow these rules to the best of their ability at all times.
1). Except in emergencies, wardens should stay in or near the brig at all times. A warden should not leave the department unattended unless absolutely necessary.
1.1). Ensuring the safety and proper sentencing of prisoners is primarily the warden’s responsibility. This includes moving prisoners to safety during explosions, radiation storms, and evacuation.
2). Antagonists are an essential part of the game. Unless it is unsafe to do so, players are encouraged to use methods of punishment that do not remove antagonists from the round such as gulag, perma, or forced cyborgization. Calling for the execution of a non-violent and cooperative antag may be marked as failrp. However, this is entirely up to the Captain, acting captain, or HoS, and their ruling (in order of the CoC) is final.
Note: Forced cyborgization is not possible for Bloodsuckers or Changelings.
2.1). HoS cannot authorize executions under space law if they are not serving as an acting captain.
1). Department heads should be knowledgeable in the basics of the sub-departments that they manage at minimum (see Command/Security/Silicon Responsibilities 1.1); however, they should avoid performing the functions of their departments if doing so displaces their subordinates.
For example, a Research Director doing toxins when no scientists are willing or able to do so is acceptable while an RD doing xenobiology while there are scientists interested in doing it is not.
1.1). Department heads should prioritize effective communication both within their departments and with other department heads. Coordinating inter-department projects and providing status updates to command staff are essential functions of department heads. Failing to effectively communicate leaves heads subject to demotion at the captain’s discretion.
1.2). Players interested in playing command roles are encouraged to use the #mentorhelp channel in discord to learn more about their department.
3). Command staff should respect the chain of command unless there is sufficient reason to not do so. A CE ignoring a captain’s meeting request when the supermatter is delaminating is acceptable. The HoS ignoring a captain’s meeting request during non-emergencies is not.
3.1). Captains should delegate tasks but avoid micromanaging departments that are staffed with department heads. Overruling the access decisions of department heads (e.g. insisting a botanist be given chem access after the CMO denied the request) or directly ordering crew members in a department is generally considered micromanaging.
4). Crew members can be demoted by department heads without captain approval for insubordination, negligence, and dereliction of duty. Because we’re a beginner-friendly server, command should avoid demoting staff for honest mistakes when the crew member is open to feedback.
4.1). Department heads can be demoted by the captain for incompetence, poor communication, and insubordination. Department heads are held to the same standards when facing demotion as regular crew. When in doubt, ahelp.
4.2). Mutiny against the captain is only acceptable AFTER you have ahelped the issue and gotten approval from admins as this often causes a lot of chaos in the round. If no admins are online, command staff may mutiny only if the captain is committing dereliction of duty or egregious infractions (i.e. capital offenses) of space law.
5). In the event that there is no captain on the station, the Head of Personnel or Head of Security must take the duties of acting captain. If there are neither a captain, HoS, nor HoP, an acting captain must be chosen from the following roles: RD, CMO, and CE. Acting department heads, silicons, and other crew members cannot be acting captain.
5.1). Acting captains are expected to perform the essential duties of the captain (secure the nuclear disk, read Command Reports, authorize executions, and run the HoP line in the case of a non-HoP acting captain) without jeopardizing the functionality of their department. If managing their own department becomes difficult, they can assign an acting head.
5.2). Acting department heads must be approved by the captain (or acting captain) and should be a player assigned to that department. Assigning a botanist to be acting CE, even when the player has previously played CE, is acting on metaknowledge and not appropriate roleplay.
5.3). Players who obtain a job change into a department (e.g. an assistant who joins engineering) should not be chosen as an acting head if there are other staff within that department.
6). Unless overruled by the captain, department heads have the final say in who has access to their department. HoPs must seek approval from department heads when granting access to a department. When the station isn’t staffed with a department head or the head doesn’t respond, the HoP should use their best judgement when granting access. For example, a janitor has IC reason to be granted medbay access but a clown does not.
6.1). Crew members' requests for extended access within their own department (e.g. an engineer asking for access to atmospherics) should be handled by the department head when one exists.
6.2). Granting all-access as a non-antag HoP (even with restricted areas removed) without a direct order to do so is never acceptable and may result in a role ban.
6.3). The Gateway is a restricted area, and the captain (or acting captain) has a final say on when/if access is granted. Granting access without authorization or an AI bolting Gateway doors open without sufficient IC reason can lead to a job ban.
7). Only the captain (or acting captain) should call the shuttle when there is one who is capable of doing so. The captain should take the requests of department heads into consideration when determining to call/ recall the shuttle. The shuttle should be called an appropriate alert level (e.g. ending a round without an immediate threat can only be called on green alert).
1). Being an antagonist is not sufficient cause for random murder. Arguing that syndicate agents want to make Nanotrasen look bad (or similar)is not an acceptable excuse.
2). Although teamwork isn’t required for non-team antags, antags should act in the best interest of the organization they represent and avoid working against each other without sufficient IC reason.
3). When converted to an antagonist role (e.g. vassal, revolutionary, brainwash victim), you are REQUIRED to follow the flavor text associated with the conversion even if the conversion was involuntary. Attempting to be deconverted, informing on, or acting against your co-conspirators’ goals is against the rules and can result in a ban. If you do not wish to participate in this type of antag, contact admins and request a role ban.
4). Leaders of group antags (i.e. nuclear/clown operatives, cult, and revolutionaries) should be obeyed much like a regular department head.