Search the Community
Showing results for tags 'mrp'.
-
All crew on MRP are expected to stay within their job and not do other people's jobs for them, however there are no restrictions on crew knowledge in regards to hacking doors. This applies whether or not the situation is an emergency.
-
For example, if I'm an antag and I kill someone for an objective, but then get attacked by a bunch of people, can I kill them all?
-
Diona are actually 3 woodlice in a bark suit, therefore the following clarifications of various rules have been made: Diona Nymphs are to be treated as station pets akin to Ian, Renault, or Smile by the crew or its inhabitants, whether they are sentient or not. When a Diona splits into nymphs, its Brain Nymph remembers its past life before falling crit/unconscious, but is aware that it has died. On MRP the new life rule remains in effect for the diona through all life stages. Other non-brain Nymphs do not remember anything from their prior Diona state should they become somehow sentient. A Diona is only an antagonist in any stage of its life cycle if the game tells you that you are.
-
Recently I've been playing a character that resembles (is not named) Doomguy. I will accurately roleplay and act as the Doomguy from the Doom games, while abiding by escalation and power-gaming laws, or course. One time playing sec as this character, HoS (Of whom which I will not name, for I value privacy) had just been a buzzkill the whole shift, completely shutting down any attempt to roleplay my character or act as a unique being. In LOOC, I had a minor dispute with HoS. HoS claimed that my character was, and I loosely quote, "LRP silliness," and something sad along the lines of "I play for the job not the fun" or something depressing like that. I don't think that a franchise crossover is LRP silliness at all. In fact, it leads to greater roleplay and possibly even to HRP. My Doomguy arc was even advocated by admeme in a previous round. Would a franchise crossover such as Doomguy be considered LRP?
-
I'm gonna consider that hacking is not taught by nanotrashen to all crew other then engineering... or i could be wrong. Should a passanger know how to hack? A doctor? Of course breaking into a department is an IC offence thats not the question. But what about in emergency situations? Can i expect a doctor character to start hacking an access restricted door to get to a safer place if they never seen someone who "knows" like an engi? Could the CMO start hacking captains door if there is a report that captain is dead in their office? Or should they wait for CE or an engineer? tldr: Is hacking something crew can know about if they choose to round start? Or only engineering
-
So I was a rat king on MRP Detroit I was doing normal freindly rat king gimmick I was going to coexist I had not attacked anyone and the captain hunted me and I told other crew and other heads I was friendly and a head said on command coms that I was friendly but the cap said nothing during this whole thing I was trying to rp it out and stuff you know "nyeh what are you doing" the cap said nothing while he was hunting me yet again we were on mrp I understand hunting a antagonist but it is mrp for a reason I typed this out cause the admin at the time said it was a packed question and should take it here.
-
When/Is clothing considered contraband/restricted gear?
OverwatchVoice posted a question in Questions
Hello, I had this question in my mind and I have asked a few people but my answers were different. In the SOP under "Contraband Lists", most items are defined however clothing is not on the list. Would clothing such as Security, ERT, and Central Command be considered contraband/restricted gear? Shouldn't it be specified in the SOP if they are to be considered contraband/restricted gear? If they are not considered to be contraband/restricted gear, why aren't they? Also, this isn't related but, shouldn't everything like this be defined in SOP or are there specific exceptions where something isn't written there but is also illegal?
-
Picture this scenario: Someone claims they found a bloodpile with the remains of Ian's body. They claim they only just grabbed the corgi hide. However cargo confirmed they never ordered a corgi thus there's is a good reason to suspect they are lying Could you reasonably start checking for storage implants? Yes if someone uses an implant like an emp that's obvious. But what about hidden ones like storage?
-
Crew can learn of implants by seeing them used. For example, a freedom implant can be presumed if someone is seen spontaneously breaking out of cuffs, but not if there are other plausible explanations. If someone is cuffed, but out of view for some time and escapes, you cannot presume that they have an implant because they could have escaped the cuffs normally. Crew can also learn of implants if any other explanation is extremely unlikely. For example, an item is known to exist in an area, and a storage implant is the only plausible option for where it could exist. This can also be used in the opposite situation, an item is known to not exist in an area, but then appears, and the only plausible option was an implant. In a scenario where someone is in a cell with something, they are not out of view for so long that it is possible that the item could have left through some other means, like someone else taking it, the item is not there anymore, and the cell has been searched to ensure the item was not hidden, a storage implant can be presumed. It's important to remember that, even if a cell appears to be undamaged, someone could have broken in then repaired the damage, someone could have hacked in, or someone could have entered with access. A probable explanation for a prisoner no longer having an item can often be a security officer taking it from them. Finding an unlocked uplink allows crew to have full knowledge of all implants. Limitations This clarification is intended for MRP.
-
While some players indirectly references rules in an IC friendly way, saying things like "Central Command wouldn't like that" or "the gods don't like it when people randomly kill people", direct references to the rules "rdm is against the rules" in IC channels is itself against the rules and should be ahelped. Players are encouraged, but not required, to respond to things like this IC, which typically means acting like the person talking about rules is delusional. Players are not admins. Even admins who are playing in the round should be treated like any other player. If a player uses an OOC channel, like LOOC, to say you broke a rule, you're not required to listen to them. There are many options for how you can deal with this, including suggesting the player ahelp if they think you're breaking a rule, ahelping yourself, ignoring the OOC messages, or attempting to verify that you haven't broken a rule by re-reading the relevant section. You can also choose to try to explain why you believe you're not breaking a rule, but are encouraged to avoid getting into an argument about it with the player, especially during a round. A player having told you that something is against the rules isn't sufficient to expect you to believe that it is against the rules. This means that even if you're unsure, it's appropriate to do something like continue to brig someone who is telling you in LOOC that you're breaking a rule. If you are unsure if you're violating a rule, you should attempt to check, and can choose to tell the player in LOOC that you're going to check. Admins will generally only take actions beyond a warning in the most extreme cases if another player has threatened to get you banned. If you're ever contacted by an admin after a player threatened admin action, you shouldn't expect no admin action, but you're encouraged to bring it to the attention of the admin.
-
Antagonists are not entirely exempt from the restrictions of any active rolebans. Antagonists may not continuously or significantly act in the role they are banned from, but may do things to attempt to maintain a cover such as: Dressing (disguising) as the role they're banned from Getting promoted to the role they're banned from (I think?), which is something we've game banned people for in the past Performing some job tasks to blend into the role
-
Team antagonists are required to work with members of their team, but not any other antagonists. No other antagonists are required to work with any other antagonists. As long as it does not conflict with their specific rules, team antagonists are free to choose to cooperate with antagonists not in their team, and other antagonists are free to choose to cooperate with other antagonists. The requirement that this cooperation not violate the antagonist's specific rules means that, for example, team antagonists cannot cooperate with an antagonist to the detriment of their team.
-
Security shouldn't be searching every single item on a player without a proportional level of suspicion to justify that level of search. A truly random search should be relatively quick, with the amount of time that a search can take while still being reasonable increasing the more evidence there is casting suspicion on the searched player. PDAs There are no special restrictions on PDA searches. Even during a random search, security may check PDA notes or settings, look for unlocked uplinks, and try to unlock uplinks. Headsets If security has a reasonable IC suspicion that people are using channels they aren't authorized to, for example, because headset keys have been stolen, headsets can be checked as part of a search. Security is free to search headsets more thoroughly if someone is arrested, but should not delay their release or extend their brig time to enable excessive searching.
-
The goal of zombies is to infect as many others as possible. Power disruption generally interferes with this goal because zombies have to break through doors while crew can crowbar them open, but it may be appropriate in some cases. Zombies may break windows, break barricades, space areas, and break into departments, but should almost always prioritize infecting players that they're aware of. A zombie should generally not be attempting to break through a barricade while an uninfected player is within reach. Zombies are generally free to know the purpose of consoles and destroy them, but should keep in mind the rules about delaying rounds. For this reason, zombies should not destroy communication consoles. With anything zombies do that results in player deaths, including spacing, zombies should keep in mind the "Don't be a dick" rule and their goals. Zombies may space areas, but should avoid actions that result in prolonged periods between a player dying and being infected or revived.
-
You can use the game's built in ability to bind commands to keys, including for chat commands. Limitations Certain uses of these commands may still be problematic, such as using them to spam.
-
You can recognize any voice that the game allows you to recognize. If the game tells your character that Joe Genero said something, your character can act as as if they heard Joe Genero say it. This also applies to hearing holoparasites, nuclear operatives, and zombies say things. Limitations This should not be interpreted to allow you to bypass any new life rule or memory restrictions. This is onlly relevant for IC channels, your character is not aware of OOC or LOOC chat.
-
Supervisors have wide latitude for demotions. Someone can demote anyone under their supervision if they are able to articulate why they believe it is best for the station. IC conflicts can be used as justification for demotions if they are severe enough. On MRP, space law and standard operating procedure cover demotions.
-
Giving a player an advantage based on interactions in past round or any other knowledge of who they are is considered metafriending. Metafriending players is a form of metagaming and is against the rules. In some cases, being metafriended may also be against the rules, but only when there is evidence that the player being metafriended was complicit.
-
Validhunting is the hunting of players without a reasonable IC reason to do so. Players do not have to be attempting to kill another player to be considered to be validhunting. Validhunting is covered by the powergaming rules. Non-Security Non-security should generally not be focusing on seeking out, killing, or arresting threats. They can if threats present themselves, or if they are particularly relevant to the crewmember. For example, crew may attack a syndicate they see attacking another crewmember, and salvage techs may respond to a callout of carp in cargo. Certain severe emergencies may make it reasonable for normal crew to defend the station against it, like nukies or particularly destructive traitors. Security It is the job of security to deal with most sentient threats to the station. It is not validhunting for security to attempt to appropriately deal with these threats. Security being overzealous in attempting to deal with threats often falls under metagaming or inappropriate escalation, not validhunting.
-
Hey hey hey it's me the berry here with the most important question this channel will ever receive When is it appropriate to escalate a non-violent conflict into a violent one? Examples: Assistant broke into cap's office, stole an item, refuses to drop it and leave. An atmos technician walks into atmos to find someone in a gas mask with no ID in atmos. A security officer is attempting to unjustifiably arrest a bartender for creating moonshine. A clown hops into botany and uses a spade to remove every single plant. Assume that the killing party makes an attempt to get the killed party to medical. Both parties have no way of knowing if the other is an antag or not, and assume that in all cases there are no non-lethal alternatives. Assume as well that none of these people have violated any other rules (besides perhaps "don't be a dick", fuck you clown who removed my corn!) All of these are situations that I have personally encountered in my time playing in the last two weeks and for each one I've seen people who believe that the case was either completely against the rules or was completely safe under the current rules. The hope is that we can find some kind of generalized rule qualifying when it is appropriate to escalate conflict IC.
-
If someone is intentionally creating kudzu, or a similarly dangerous situation, they can be attacked to stop them, however the attacker will be held responsible for poor assumptions. Normal escalation rules apply if the person is not actively worsening the situation, or if it is accidental. For example if the creation of kudzu is not happening in the moment. Accidental creation of dangers can be treated as a low-level start of escalation. Verbal instructions from normal crew to stop do not have to be obeyed, but those instructions being ignored can further justify physical escalation. Department heads and the captain are typically free to demote people for the benefit or safety of the department or station. Additionally, security can choose to arrest people who create a dangerous environment or problems for the station. -
Kzudu is dangerous and extremely invasive, so intentionally making something that dangerous would typically be considered self-antagging.
-
When a player refuses to play the game, or puts little to no effort into playing the game when they don't get an antag role, they are said to be antag rolling. This typically happens when a player has little to no interest in playing the game when they are not an antag. All players are expected to play through every round they join as a role in until the "natural end" of that role. Players are not expected or required to accept cloning. It is unreasonable to expect every player to play fully through every round they join so, often, there will be no admin action unless a pattern or high frequency is seen. Important roles, like command, are expected to ahelp before leaving, but even here there are situations where this may not be possible so no admin action is typically taken on a first offense. Players should never ghost, suicide, disconnect, or not put effort into playing their role based on them getting a certain role, or not getting antag status. While the goals of these rules can be described with little grey area for what is considered a violation, the fact that intent is a factor and the fact that there are multiple valid reasons that may cause behaviors that look like antag rolling means that the grey area is relatively large in practice and enforcement can be subjective. Players who believe an admin made a mistake in enforcement should appeal and do their best to describe the situation. Common examples of things that may be considered antag rolling: Suiciding or disconnecting near round join, specifically if it becomes a pattern AFKing for long periods of time, specifically if it becomes a pattern As a staff role, building or leaving on a shuttle near round start, or when any important work needs to be done by your department As a staff role, building unnecessary rooms in maintenance, like a maint bar, near round start, or when any important work needs to be done by your department
-
Unsalvaged salvage debris is not owned by the cargo department, but salvaging debris as other roles just because you have a hardsuit may be considered powergaming depending on circumstances. IC conflicts can arise from others interfering with the savage techs by salvaging debris for personal use or for other departments. Items within the cargo department, including any salvage wings, can be treated as other items in other departments are. Stealing a crate that cargo intends to sell from inside cargo can generally be treated similarly to someone stealing a crate of materials from engineering. Items which salvagers have left outside of the station are not the same as items within the department. It is much more reasonable for someone to consider an item that is in space outside of salvage as "abandoned", even if that is rarely the case. Taking these items can still result in IC conflicts. Unlike taking items directly from the salvage debris, taking these items can be treated as stealing from a person or from the department, but not to the same degree as stealing directly from a person or items within the department.
-
Admins are able to make anyone an antag and there are multiple other ways that antags can get a role that can't typically be a round start antag. Regardless of if a role can naturally be an antag, players who act as antags can and should be treated as antags IC.
