More actions
Schalkguy1 (talk | contribs) No edit summary |
Schalkguy1 (talk | contribs) |
||
(47 intermediate revisions by the same user not shown) | |||
Line 21: | Line 21: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" width=150|Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" width=150|Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 187: | Line 187: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 199: | Line 199: | ||
| | | | ||
*Collective managment | *Collective managment | ||
| | |- | ||
!<div align="center">Can the corrupted hive choose to be friendly to the USCM? And must other hives always be hostile?</div> | |||
| | |||
Alpha through Zeta hives = hostile | |||
Corrupted = can choose | |||
Total leeway during major events if it is signposted beforehand. Some during minor depending on how signposted and how much | |||
| | |||
*12/16/2022 | |||
| | |||
*Moonshanks | |||
|- | |||
!<div align="center">If someone who shouldn't normally be frontlining such as shipside personnel deploy to escape arrest and stay near the frontline that's not okay, right? </div> | |||
| | |||
*Unauthorised deployment becomes OOC if either of two conditions are met | |||
*1. They’re frontline fighting as non combat role | |||
*2. They’re not performing the required duties of their role, IE an MT isn’t building defences or repairing the APC, or a Doctor is not providing medical aid whatsoever | |||
*If neither are true but they’re still near frontline and MPs can’t reach them, that’s just tough luck for MPs. Though generally speaking it’s not often they’re on front without one or both of those conditions occurring. | |||
| | |||
*11/13/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Is it acceptable for a researcher, after spending entire round not doing any work in research whatsoever, to waste all the accumulated credits on buying clearance and random recipes, without asking the CMO or anybody else in research?</div> | |||
| | |||
*I would check to make sure the player wasn't new or confused on what they were doing, but assuming they were not, yes, in my opinion that does sound like griefing. | |||
* If the person was just spending everything earned without reason, it would be grief- if they were looking for something specific, but didn't contribute to the round by playing their role, I would just talk to them about RP and limited roles- depending on severity of them not playing the role/newness of the player possible note for LRP or cnote if you have concerns they might continue. | |||
| | |||
*11/03/2022 | |||
| | |||
*Scarlet | |||
|- | |||
!<div align="center">Are there any rules for the Corporate Liaison in handing out their items such as drugs and implants?</div> | |||
| | |||
*There needs to be roleplay between the Corporate Liaison and the other party. The Corporate Liaison should not be on the front line or at briefing handing out items like Ultrazine and saying LRP stuff such as "Free candy!" The items should be in exchange for the party working on behalf of W-Y interests, not just "Marine be my bodyguard, heres free ultra" | |||
| | |||
*08/25/2022 | |||
| | |||
*TheSoldier | |||
|- | |||
!<div align="center">Can I use the gibber to make meals out of dead marines as a chef or any other role?</div> | |||
| | |||
*No. While there is nothing stopping you from doing that mechanically, grinding the bodies of recently deceased marines or random survivors to serve them as meals does not fit our established setting and would be considered a heinous/insane act. As such, it is considered to fall below the expected RP standard for all roles outside of events and is not allowed per our server rules. | |||
| | |||
*07/13/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center">What, if any, images are acceptable in CIC and Queen Broadcasts?</div> | |||
| | |||
* Players in command roles on both sides are allowed to post direct links to images containing current map (from sources like the webmaps or wiki images of the map) or images of the tacmap, with drawn on overlays giving directions/other information as long as they are kept reasonably IC. | |||
| | |||
*06/27/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center">Where does the Vehicle Crewman job fall as far as RP standards/expectations go?</div> | |||
| | |||
* Vehicle Crewmen fall into the same bracket of IC and OOC expectations as SL's, RTOs, Specs and Smartgunners - this means that their character concept is meant to be somewhat grounded in our setting and perhaps more importantly they are bound by OOC rules to follow orders from the officer in command of the operation to the best of their ability unless doing so would put their life and/or the APC under direct threat. | |||
| | |||
*05/24/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center"> Can Xenos refer to humans by name, and Humans refer to Xenos by prefix?</div> | |||
| | |||
* No, the Xenos have no idea a human is so and so, and humans have no idea a Xeno has a “Nick name” Terms should be generic such as caste, tall host, specialist type etc… the developers eventually and some hopefully plan on making it that each side will only be able to see the other side as generic terms (Host, Caste, etc…) but it’s not set in stone | |||
| | |||
*04/17/2022 | |||
| | |||
*TheSoldier | |||
|- | |||
!<div align="center"> Can I use larva as recon to find survivors?</div> | |||
| | |||
* Absolutely not. Larva are not recon castes, and using them to find survivors goes against the principle they should stay in the hive, and puts them in danger. | |||
| | |||
*04/08/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center"> Can I as CLF dress up as a marine to trick and kill them, or as a marine dress up as CLF/another hostile faction?</div> | |||
| | |||
* No. No pretending to be friendly then backstabbing, outside of events with specific permission. | |||
* This does not include pretending to comply with an arrest and running. | |||
| | |||
*04/05/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center"> Are APC's considered "Secure Areas" for the purposes of Marine Law?</div> | |||
| | |||
*Yes. Support roles may stay within the APC as they would any other secure area. MP's may make use of the APC to travel from one secure area to another, but cannot use the APC as a way of heading to or arresting people on the frontlines. | |||
| | |||
*02/02/2022 | |||
| | |||
*Somenerd | |||
|- | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Line 252: | Line 348: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 294: | Line 390: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 352: | Line 448: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="width:164px; background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 364: | Line 460: | ||
| | | | ||
*Collective managment | *Collective managment | ||
| | |- | ||
!<div align="center">Is damaging corpses (HvH) after death is still a no-no (Both for ERTs and marines)</div> | |||
| | |||
*Deliberately rendering someone unable to be revived is a no go yes. This includes hostile humans. The difference is you can move them to somewhere difficult, you just can’t hide them away/over damage them. It has to be semi realistic to what can be done rather than meta to stop revives | |||
| | |||
*12/12/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Thoughts on morgue trays not being able to be attacked?</div> | |||
| | |||
*Can be climbed over and the morgue itself melted will remove the tray | |||
| | |||
*12/06/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Is a xeno using a barrel as cover (the easily destructible kind with a crowbar or explosives) metagaming?</div> | |||
| | |||
*it's fine unless they move them for cover / use them as moveable cover as that is tool use and xenos cannot use tools | |||
| | |||
*12/04/2022 | |||
| | |||
*Stan_Albatross | |||
|- | |||
!<div align="center">Is it considered an exploit to use a sleeper in a combat manner? Someone was using a sleeper to pop out and instantly double fire a custom shotgun without any delay.</div> | |||
| | |||
*Gonna say it's unintended to use it for that mechanic yes, gotta add a delay for it | |||
| | |||
*11/28/2022 | |||
| | |||
*Nanu | |||
|- | |||
!<div align="center">Is placing a custom C4 on a girder allowed or not?</div> | |||
| | |||
*Stationary yes mobile no | |||
| | |||
*11/22/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Is walling off NORMAL APCs allowed? For instance the power APC in colony engineering (https://cdn.discordapp.com/attachments/799438026140287016/1042136861528834128/image.png)</div> | |||
| | |||
*Yes | |||
| | |||
*11/15/2022 | |||
| | |||
*Stan_Allbatross | |||
|- | |||
!<div align="center">C4 planted on xeno corpses then moved around. Is this okay?</div> | |||
| | |||
*Sounds fine to me, if c4 was visible plus it being dragged around manually | |||
| | |||
*01/03/2023 | |||
| | |||
*Nanu | |||
|- | |||
!<div align="center">Can I use tailstab through doors/windows/blast doors?</div> | |||
| | |||
*No, this is a bug and doing so will get you in trouble. | |||
| | |||
*10/12/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Push ups, or any other mechanic, has made my character permanently horizontal, allowing me to move/shoot at regular speed and while holding my gun. Can I use this mechanic because I find it entertaining or for any other reason?</div> | |||
| | |||
*No. Making your character permanently horizontal is jarring from an IC standpoint and skirts our memery/ooc behavior rules and is clear bug abuse as well. Moving forward, purposefully abusing this mechanic will be treated as blatant bug abuse. | |||
*The only allowed way of movement via remaining horizontal on the screen is using the crawling mechanic, done by moving while laying down. | |||
| | |||
*08/30/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center">What about OT grenades? Can I set them on a high timer, prime them, put them in my pack, then get capped on purpose?</div> | |||
| | |||
*No. Blowing up the hive and caps with any explosive hidden in your backpack is not an intended mechanic. | |||
| | |||
*08/21/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center">Can I plant a custom C4 on a mouse, then put it into my backpack so it can be detonated via remote trigger if I am capped?</div> | |||
| | |||
*No. That is a bug that will be soon patched up. As a general rule, C4 is not supposed to be mobile after planting and is supposed to be clearly visible once it is planted. Anything that bypasses those two conditions is most likely a bug in which case you should report it and stop using it. | |||
| | |||
*08/20/2022 | |||
| | |||
*Silencer | |||
|- | |||
!<div align="center">Can I use third party tools such as auto hot key or autoclickers?</div> | |||
| | |||
*Using third party tools to gain an advantage past what a person could do normally is not allowed, this means that using auto-clickers is strictly forbidden as an example. | |||
*Using macros made outside of Byond's in-game macro editor that chain multiple button presses together or a combination of them is also not allowed. | |||
*Re-binding a single button press to another is allowed, with the exception of Mouse-Wheel macros. | |||
| | |||
*07/16/2022 | |||
| | |||
*Nanu | |||
|- | |||
!<div align="center">Can I spam the give item dialogue to mechanically disrupt players in game?</div> | |||
| | |||
*No. This is considered an exploit and will be met with an immediate 7 day ban. | |||
| | |||
*05/27/2022 | |||
| | |||
*Ben11567 | |||
|- | |||
!<div align="center">Can I drag the queen to a flank so she doesn't make any sound?</div> | |||
| | |||
*No. This is bypassing a mechanic intended to pre-announce the Queen's presence. | |||
*Dragging her while AFK, injured or otherwise is fine, but moving the Queen via dragging to avoid footstep sounds is bypassing this feature. | |||
| | |||
*05/23/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center"> Can I build cameras on the colony and link them to the Almayer?</div> | |||
| | |||
*No, this is a bug exploit and is not intended to be possible. | |||
| | |||
*05/23/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Line 414: | Line 635: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 426: | Line 647: | ||
| | | | ||
*Collective managment | *Collective managment | ||
| | |- | ||
!<div align="center">Are MPs allowed to accept OOC gameplay recordings as evidence? Since helmets do have cameras and the guy would've been stuck in brig until his appeal otherwise. | |||
</div> | |||
| | |||
*Yes because of your logic, but it should be ruled on a case by case basis. The majority of the time OOC evidence should go through staff. (or be handed out by staff) | |||
| | |||
*11/28/2022 | |||
| | |||
*Moonshanks | |||
|- | |||
!<div align="center">Can I kill marines gearing up in cryo or prep before hijack, because on red alert they are equipped with mod 88s?</div> | |||
| | |||
*No, Xenomorphs cannot attack marines gearing up in cryo or prep outside of hijack | |||
* Hijack can mean mechanical hijack or if the ship is completely overrun by xenos but no mechanical hijack has happened. | |||
* If a marine is baiting a xeno by shooting them and then running back into prep, it is probably fine for the xeno to kill them | |||
* If in doubt use common sense | |||
| | |||
*11/14/2022 | |||
| | |||
*Moonshanks | |||
|- | |||
!<div align="center">Can I fire an OB on the LZ as soon as the dropship takes off from the Almayer, before the Queen can lock it?</div> | |||
| | |||
No, this would be meta without IC justification. For all you know there could be technical malfunction. In most cases you have no reason to suspect it has anything to do with the LZ or xenos. If you have IC justification you can do so, but this is subject to review at the time. In cases where you think you're justified to fire OB on the LZ after dropship takes off from the Almayer, ahelp your reasoning at same time as firing or before if possible. | |||
| | |||
*11/03/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">When can defenses and major preparation on the Almayer be made after an evacuation?</div> | |||
| | |||
*When the shuttle hijack message is announced. | |||
| | |||
*08/16/2022 | |||
| | |||
*TheSoldier | |||
|- | |||
!<div align="center">Can I as a xeno board the dropship on first drop to cause havoc on the Almayer?</div> | |||
| | |||
* No, this should not be done until at least second drop, when general attacks around/at the FOB are accepted. | |||
| | |||
*05/17/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">As a ship side xeno pre hijack, can I target critical equipment such as powerloaders or tcomms?</div> | |||
| | |||
* General damage is fine, but specifically targeting irreplaceable equipment is not allowed. You can attack communications but exclusively going there is meta due to not knowing the importance of that one place/not knowing the layout of the ship. | |||
This is the same for exclusively going to CIC in an attempt to decapitate the marine capabilities. | |||
| | |||
*03/21/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Line 455: | Line 730: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 527: | Line 802: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 592: | Line 867: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 604: | Line 879: | ||
| | | | ||
*Collective managment | *Collective managment | ||
| | |- | ||
!<div align="center">is bateman a valid last name? as in like paul bateman and etc </div> | |||
| | |||
*Yes, I would just make sure the player isn't using a celebrity of pop culture reference with the first name they choose. | |||
| | |||
*11/17/2022 | |||
| | |||
*Scarlet | |||
|- | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Line 637: | Line 920: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date | ||
Line 649: | Line 932: | ||
| | | | ||
*Collective managment | *Collective managment | ||
| | |- | ||
!<div align="center">So if someone loots a dead guy, and that dead guy wakes up, he has to use normal escalation to get his stuff back right?</div> | |||
| | |||
Yes. And they shouldn’t immediately know who stole it either. | |||
| | |||
*12/12/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center">Should OD injection should be considered lethal and standard forced injection considered "dangerous melee"? (aside one doesn't escalate to the other)</div> | |||
| | |||
*All OD injection is considered lethal because it would be kinda videogamy to select what injections are considered more lethal then others | |||
* it's breaking the RP of the server. In this case, escalation of force | |||
| | |||
*11/12/2022 | |||
| | |||
*Moonshanks | |||
|- | |||
!<div align="center">Can I shoot marines that are being captured, or order marines to do so?</div> | |||
| | |||
*No, this is explicitly something requiring IC or OOC (LOOC) consent from the person being capture to shoot them if they get captured. If consent is given in LOOC, it supersedes anything said, or not said, IC. | |||
| | |||
*05/23/2022 | |||
| | |||
*Forest2001 | |||
|- | |||
!<div align="center"> If person 1 repeatedly disarms and punches person 2, person 2 gives person 1 a warning in IC speech that they will shoot them if they continue and person 1 continues with their shenanigans and is shot by person 2 is this still IE?</div> | |||
| | |||
*IE unless person 2 is punched most of the way to death. Escalation requires appropriate force, not just a “I’ll shoot you” | |||
| | |||
*01/15/2023 | |||
| | |||
*Forest2001 | |||
|- | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Line 742: | Line 1,058: | ||
<tab name="Rule Clarifications"> | <tab name="Rule Clarifications"> | ||
{| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | {| border="1" cellspacing="0" cellpadding="2" width="80%" style="background-color:#EEEEFF;" class="wikitable sortable" | ||
! scope="col" style="background-color:#EEEEFF;" |Case | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Case | ||
! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ! scope="col" class="unsortable" style="background-color:#EEEEFF;" |Clarification | ||
! scope="col" style="background-color:#EEEEFF;" |Date | ! scope="col" style="background-color:#EEEEFF;" |Date |
Latest revision as of 00:51, 17 January 2023
Staff Powers
|
Rule 1. No Erotic Role Play (ERP), erotic content, or 18+ sexual content
Roleplay intended to elicit a sexual response from the receiver(s), including but not limited to writing stories (WGW) or posting links to adult content. Doing so will almost always result in an instant permaban from our server. However, these actions could still be susceptible to Marine Law. A good rule of thumb for whether an interaction crosses this line would be to consider if the action would be allowed in a PG-13 rated movie in the USA.
Staff reserve the right to make judgement calls on situations to determine if they constitute a breach of 18+ or erotic conduct. If something is overly disgusting or crosses a line in a way that becomes an 18+ situation, it may be punished for regardless of nature.
The above are guidelines for reference, and it is highly recommended not to straddle the line along what is and is not allowed when dealing with erotic/18+ content.
|
Rule 2. Roleplay
CM-SS13 is intended to be a Medium Roleplay server. Play a reasonably realistic character. Treat your character as a separate entity from you, the player. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences and not your own as the player. Low roleplay actions that have no regard for your character or the setting (Memes, silly copypaste spam IC) are not acceptable. Character development can occur over rounds but each round is a soft-reset, meaning you can have previous mission experience but your character will never have died or fled the ship in the past. Follow the Roleplay Standards.
- Major shenanigans that may disrupt the normal flow of the round at roundstart, (This includes but is not limited to; big or lethal fights, briefing brawls, riots, massive equipment restrictions and tackling players trying to reach their prep room.), are not tolerated.
|
Rule 3. Community Expectations
The general behavioural expectations for members of the community. Unless explicitly stated these rules apply to all areas of the community.
- Don't be a dick.
- This is not a complete list and only includes the most important elements.
|
Rule 4. No griefing
Griefing is the intent of one player wanting to cause grief or annoyance to other players or the server without a valid roleplay reason. If Staff believes that the player’s intent is to grief, then action will be taken whether or not it was the player’s intent. Any damage to the station or players caused by griefing can be repaired at an Admin's discretion. If you are being griefed, don’t retaliate - Adminhelp it and you’ll get healed. Shooting a griefer can cause you to get in trouble as well, and the combat logs you’re generating make it harder for Staff to prove who the real griefer is.
|
Rule 5. Mechanical Exploits
Do not abuse bugs or unintended features to gain an unfair advantage for yourself or your team.
|
Rule 6. No Metagaming or Metacommunication
Acting upon knowledge your character would not have or providing unknowable information to another player. Should you be in a voice call with other players, you are still expected to relay information through IC channels (talking, radio, etc) to preserve in-game roleplay. IC information should not be posted to any public location where other parties can be given an advantage. Any form of cheating via metacomms will result in a permaban. All public chat on the CM Discord should refrain from talking about any ongoing round information until the round ends.
|
Rule 7. No Ban Evading / Multi-Keying
Logging in with different accounts at different times, logging in with another account because you died (or were banned), or logging into two separate accounts at the same time. If you have multiple accounts tied to CM-SS13, please ahelp regarding them. Players caught breaking this rule may receive permabans from the server.
|
Rule 8. Suicide, Rage-Quitting, and Logging off
If you are a marine and need to leave the game, go to Cryo on the ship and put yourself in a cryotube. This will release your job slot and allow another player to join with your job. If you are unable to get to cryo, send an Adminhelp to staff. If you are the Queen, Adminhelp to let staff know. If you leave without cryo-ing yourself or informing staff, you risk a job ban, especially if your job is an important one. Suicide is permitted if you have a reasonable roleplay reason why, such as you are infected with a xenomorph and there is no hope of rescue, or you are the last xenomorph alive and there is no queen. Committing suicide without a valid reason will result in a ban and/or jobban.
Some roles carry the risk of punishment for logging out or ghosting without notice.
|
Rule 9. Character names
Use a reasonable, unique, lore-friendly character name that has a first name and surname. Short reasonable nicknames are allowed inside the name (e.g. Derek 'Double-D' Donahue, Jane 'Crusher' Sanchez). Other character names should not be used, this includes ckeys. Nicknames should not be considered a meme. Nicknames should also not be slurs, 18+ content, etc... You may be a sibling or cousin of another player's character, however you cannot play another player's character unless it's part of a staff event. References can be made to characters in the Official CM-SS13 lore. Xenomorph prefixs should not be 18+ or slurs as well. Staff retain rights to make the final judgement if a name or Xenomorph prefix is acceptable or unacceptable.
|
Rule 10. Lethal Force
Do not attack another player without a legitimate, explainable roleplay reason that could be applied in a similar, real-life scenario. A fist fight does not suddenly escalate into a gun fight. Should one defend themselves from grief or improper escalation, the staff handling the matter decides if a punishment is given out and to who. Staff may also decide to leave things in character. Even if you are justified, you are still susceptible to Marine Law.
|
Rule 11. Marine Law
Mutinies must be Adminhelped by a chosen leader stating the reasoning and the players directly involved. There must be at least 5 members. with MPs not eligible to mutiny.
|
Rules Clarification
In most cases, the management team releases rulings on borderline/questionable rule breaks and releases them as rule clarification. These are generally not meant to be read all in one go but should be relied upon to check what isn't or is allowed if you are about to do it.
The wiki & main Colonial Marines discord both contain a repository for these rule clarifications, that allow a player to understand if something borderline (in terms of rules) is allowed or not. So it's recommended:
- If the main colonial marine discord is easily accessible to you, you frequently check the #rule-clarification channel for new & singular historic rulings.
- You use the wiki page - Rules Clarification - for viewing long-standing rulings with quality of life improvements over the standard discord formatting.