Admin Rulings: Difference between revisions

From VORE Station Wiki
Jump to navigation Jump to search
 
(24 intermediate revisions by 6 users not shown)
Line 1: Line 1:
This is a list of admin decisions in chats or the forums about issues that have come up in gameplay, divided up by department. They are not necessarily rules, however complying with them will, at the very least, avoid long discussions about whether you should have done something or not.
This is a list of admin decisions in chats or the forums about issues that have come up in gameplay, divided up by department. They are not necessarily rules, however complying with them will, at the very least, avoid long discussions about whether you should have done something or not.


== General ==
==General==
* You are not required to ignore public non-consensual scenes due to scene protection rules.
==='Mentally' Underage Characters===
* 'Mentally' underage characters are still considered underage characters and are against the server rules. The opposite is also true ("young body, old mind").
*'Mentally' underage characters are still considered underage characters and are against the server rules. The opposite is also true ("young body, old mind").
* You void dorm scene protection if you commit the crime outside the dorm, or '''communicate''' about the crime in the dorm to the outside (radio,pda,etc).
===Soul Stuff===
* Soul stuff: [[Souls|See This Article]]
*Soul stuff: [[Souls|See This Article]]
* Prey's responsibility to notify pred in LOOC before calling for help, unless pred preference notes specify that it is fine, or prey preference notes specify that they always do.
===Prey's Responsibility During a Scene===
* CentCom characters are not "walking admins". Don't metagame and treat them weird or assume that everything they say is now a rule.
*Prey's responsibility to notify pred in LOOC before calling for help, unless pred preference notes specify that it is fine, or prey preference notes specify that they always do.
* You don't HAVE to have different characters for different departments, but it's somewhat preferred. It starts to push realism otherwise.
===CentCom Characters===
* Is someone who has previous training in a job (Job A) but is working another job (Job B) in the same department obligated to fulfill the duties of Job A? No. There is no obligation to do a job you are familiar with but are not currently working in unless that particular job lacks the appropriate people to fulfill that role. Note: this does not mean a person is obligated to learn another job. This is strictly covering a person who has worked the job before.
*CentCom characters are not "walking admins". Don't metagame and treat them weird or assume that everything they say is now a rule. Unlike admins, CentCom characters are ''characters'', and sometimes have biases, grudges, and other things that are the result of in-character incidents.
===Characters in Multiple Departments===
*You don't HAVE to have different characters for different departments, but it's preferred even if they only stick to one job per shift.
**It is generally recommended that your character stick to one Department Head role (Research Director, Head of Security, Chief Engineer, Chief Medical Officer) - moonlighting as regular department staff is permitted, as are more generic command roles.
**If you play your character as any on-station command role, it is generally not recommended to also play them as Talon crew.
*If you wish to have your character undergo a change in career, it is recommended to play them as general department staff for a while instead of leaping directly to head of staff.
**If you are ICly involved in a major incident, it is advised not to immediately switch sides (eg. a Talon crewmember involved in a dispute joining as a station head of staff the following shift)
**While there are no strict rules about how long you must wait between switching your character's job, admins may take action if you change so frequently as to break immersion.
**"My character worked as this job before" will not be accepted as an excuse for job-stealing.
**It is highly recommended that you create different characters to make it easier on yourself.


== Command ==
===Job Obligations When Working Another Job===
*Is someone who has previous training in a job (Job A) but is working another job (Job B) in the same department obligated to fulfill the duties of Job A? No. There is no '''obligation''' to do a job you are familiar with but are not currently working in. You can volunteer. If you're a Psychiatrist, but a surgeon is needed, you are not required to suddenly become a surgeon unless you are literally the only person there who can currently do the job, in which case you might want to try to help them for the sake of their gameplay time and not leaving them crippled. At that point it is more an OOC favor to that player to allow them to continue playing.


== Engineering ==
==Command==
The following are related to each other:


* Is someone that works in engineering in a job that isn't specifically engineering/engine tech and has no engine training required to set the engine? The answer is no without supervision/on-site training due to lack of ability to troubleshoot. A person should use this as an opportunity to RP with an engineer.  
==Engineering==
* Should someone who DOES have previous training but is in a different job be able to touch the engine? This falls under the general ruling on doing someone else's job, meaning you are not obligated to touch the engine unless there is a pressing need to do so, or there is nobody else in the department with a more appropriate role. The general rule of thumb is to try and stay in your lane unless you are either ordered to help, someone asks for it, or they accept your help and training.
===Job Obligations as it Relates to Engineering Skill===
* Should a person who is in another job be obligated to run the engine despite lack of training? The answer goes back to number 1 and 2 which is no, there is no obligation and it is a liability due to lack of troubleshooting ability. Wait for a trained individual to supervise and teach you.
*The following two are related to each other:
**Is someone that works in engineering in a job that isn't specifically engineering/engine tech and has no engine training required to set the engine? The answer is 'no' without supervision/on-site training, due to lack of ability to troubleshoot. A person should use this as an opportunity to RP with an engineer.
**Should someone who DOES have previous training but is in a different job be able to touch the engine? This falls under the general ruling on doing someone else's job, meaning you are not obligated to touch the engine unless there is a pressing need to do so, or there is nobody else in the department with a more appropriate role.
===Engine Experimentation With an Actively Working Engine===
*Please do not fuck with the engine if it has already been set up and is running smoothly. Unless you are prepared to sit there and monitor it because you're experimenting with it, don't do it.


== Security ==
==Security==
* You should not patrol maintenance regularly, for the sake of actually allowing the other side of the game (people trying to get away with things) a chance.
===Maintenance Patrols===
* The Head of Security (or whoever is the securityboss) can issue a blanket license to carry e-guns for sec officers if they wish, if people are being particularly problematic with guncargo or R&D guns or something. Or if they want to. It's their prerogative.
*You should not patrol maintenance regularly, for the sake of actually allowing the other side of the game (people trying to get away with things) a chance.
===HoS (Round Limited) Weapons Permits===
*The Head of Security (or whoever is the securityboss) can issue a blanket license to carry e-guns for sec officers if they wish. However, the HoS issuing the permit assumes the responsibility of whatever happens as a result of handing out a weapons permit.
**In the event something does go wrong, it will be handled ICly first. If it becomes seen as a habitual problem, it will be handled OOCly.
===Victim Dropping Charges ICly or OOCly===
*A victim can drop charges directly relating to them ''except for Murder.''
**However if both pred and prey, IC and OOC want to drop charges over their scene, then it should be dropped.


*A victim can drop charges directly relating to them ''except for Murder.''  
==Medical==
**From an OOC perspective, being cloned/resleeved comes with Clone Memory Disorder attached, and for Resleeving the idea that the backup implant is not CONSTANT means there could be a gap at the end of your memory. Those are IC reasons for a more important OOC thing: Coming back from the dead to influence criminal proceedings is shitty gameplay, so don't do that. When you're cloned, you either forget the crimes against you, are considered an unreliable witness, or something. Be reasonable here. Try to make the game fun for everyone. That's the whole point of games. Like all games. Don't be an ass.
===Asking to be Resleeved via OOC===
***A resleeved person can drop charges if they can prove they are of same mind, different body. This also means a criminal can be charged for a crime if it is proven they are of same mind, different body.
*People needing resleeving may OOCly '''ask''' for one but may not OOCly '''demand''' it because they have alternative respawing abilities to use in the event asking fails. Demand in this case means to aggressively ask for something with no regard to the other player's own activities and being obscenely unreasonable in the process. At the same time, doctors should at least make the effort to resleeve that specific person at least '''once'''. After that one time for that specific person, the doctor may prioritize other activities for a reasonable period of time.
**'''Charges directly relating to the victim''' means that the crime happened to the ''victim and the victim alone.'' Security can still charge for crimes that happened AROUND the specific victim. For example, vandalism of property belonging to NT during the crime, disturbing the peace, or even assault of another person or persons. ''The victim cannot speak for other entities, only for themselves.''
**'''What does this mean for OOC Vore-Crimes considerations?''' Refer to the previous ruling on public scenes from January 12, 2017. Other than that, not much, you dingus. If the victim of a vore crime lives and opts not to press charges specific to them, drop em. Else, ooc vore-crime considerations to a sentence still attach. (Just use your better judgement, please.)


== Medical ==
==Cargo==
* Psych position is not required to perform medical tasks outside their job function, but may if they have that job experience for setting up cryo or chemistry. They may want to consider cloning, if possible, and assuming cryo is set up, simply for the sake of letting someone rejoin the game normally using the IC mechanics rather than respawning.


== Cargo ==
==Science==
===Soloing Group-Oriented Content===
*Don't try to do group-oriented content by yourself. People later in the shift, or even your coworkers may have wanted to participate in the mission. If you complete it by yourself, then you're depriving other people of the enjoyment of it.


== Science ==
==Silicon==
===Ordering a Cyborg to Pick or Switch to a Specific Module===
*Cyborgs are not required to follow orders to pick or switch to a particular module any more than a regular crewmember can be ordered to go on duty or join as a particular job. If pressed to do so, borgs are completely at liberty to advise crew that they don't have the firmware loaded for a particular module, then do a terrible job or "shut down to prevent harm". Alternatively, the order should be ahelped then disregarded.
===Spam-Demanding a Borg to State Laws===
*Don't spam the borg with repeated obnoxious "state law" requests. The borg may prioritize who they answer that request to.
**For example, the borg can choose completely ignore this request from low-level crew members/visitors and only acknowledge the request from Heads of Staff.
**Note: Even if they don't have the standard lawset, if the lawset isn't harmful then getting your valids on it or reverting them immediately is considered [[no fun allowed]].

Latest revision as of 15:17, 23 May 2023

This is a list of admin decisions in chats or the forums about issues that have come up in gameplay, divided up by department. They are not necessarily rules, however complying with them will, at the very least, avoid long discussions about whether you should have done something or not.

General

'Mentally' Underage Characters

  • 'Mentally' underage characters are still considered underage characters and are against the server rules. The opposite is also true ("young body, old mind").

Soul Stuff

Prey's Responsibility During a Scene

  • Prey's responsibility to notify pred in LOOC before calling for help, unless pred preference notes specify that it is fine, or prey preference notes specify that they always do.

CentCom Characters

  • CentCom characters are not "walking admins". Don't metagame and treat them weird or assume that everything they say is now a rule. Unlike admins, CentCom characters are characters, and sometimes have biases, grudges, and other things that are the result of in-character incidents.

Characters in Multiple Departments

  • You don't HAVE to have different characters for different departments, but it's preferred even if they only stick to one job per shift.
    • It is generally recommended that your character stick to one Department Head role (Research Director, Head of Security, Chief Engineer, Chief Medical Officer) - moonlighting as regular department staff is permitted, as are more generic command roles.
    • If you play your character as any on-station command role, it is generally not recommended to also play them as Talon crew.
  • If you wish to have your character undergo a change in career, it is recommended to play them as general department staff for a while instead of leaping directly to head of staff.
    • If you are ICly involved in a major incident, it is advised not to immediately switch sides (eg. a Talon crewmember involved in a dispute joining as a station head of staff the following shift)
    • While there are no strict rules about how long you must wait between switching your character's job, admins may take action if you change so frequently as to break immersion.
    • "My character worked as this job before" will not be accepted as an excuse for job-stealing.
    • It is highly recommended that you create different characters to make it easier on yourself.

Job Obligations When Working Another Job

  • Is someone who has previous training in a job (Job A) but is working another job (Job B) in the same department obligated to fulfill the duties of Job A? No. There is no obligation to do a job you are familiar with but are not currently working in. You can volunteer. If you're a Psychiatrist, but a surgeon is needed, you are not required to suddenly become a surgeon unless you are literally the only person there who can currently do the job, in which case you might want to try to help them for the sake of their gameplay time and not leaving them crippled. At that point it is more an OOC favor to that player to allow them to continue playing.

Command

Engineering

Job Obligations as it Relates to Engineering Skill

  • The following two are related to each other:
    • Is someone that works in engineering in a job that isn't specifically engineering/engine tech and has no engine training required to set the engine? The answer is 'no' without supervision/on-site training, due to lack of ability to troubleshoot. A person should use this as an opportunity to RP with an engineer.
    • Should someone who DOES have previous training but is in a different job be able to touch the engine? This falls under the general ruling on doing someone else's job, meaning you are not obligated to touch the engine unless there is a pressing need to do so, or there is nobody else in the department with a more appropriate role.

Engine Experimentation With an Actively Working Engine

  • Please do not fuck with the engine if it has already been set up and is running smoothly. Unless you are prepared to sit there and monitor it because you're experimenting with it, don't do it.

Security

Maintenance Patrols

  • You should not patrol maintenance regularly, for the sake of actually allowing the other side of the game (people trying to get away with things) a chance.

HoS (Round Limited) Weapons Permits

  • The Head of Security (or whoever is the securityboss) can issue a blanket license to carry e-guns for sec officers if they wish. However, the HoS issuing the permit assumes the responsibility of whatever happens as a result of handing out a weapons permit.
    • In the event something does go wrong, it will be handled ICly first. If it becomes seen as a habitual problem, it will be handled OOCly.

Victim Dropping Charges ICly or OOCly

  • A victim can drop charges directly relating to them except for Murder.
    • However if both pred and prey, IC and OOC want to drop charges over their scene, then it should be dropped.

Medical

Asking to be Resleeved via OOC

  • People needing resleeving may OOCly ask for one but may not OOCly demand it because they have alternative respawing abilities to use in the event asking fails. Demand in this case means to aggressively ask for something with no regard to the other player's own activities and being obscenely unreasonable in the process. At the same time, doctors should at least make the effort to resleeve that specific person at least once. After that one time for that specific person, the doctor may prioritize other activities for a reasonable period of time.

Cargo

Science

Soloing Group-Oriented Content

  • Don't try to do group-oriented content by yourself. People later in the shift, or even your coworkers may have wanted to participate in the mission. If you complete it by yourself, then you're depriving other people of the enjoyment of it.

Silicon

Ordering a Cyborg to Pick or Switch to a Specific Module

  • Cyborgs are not required to follow orders to pick or switch to a particular module any more than a regular crewmember can be ordered to go on duty or join as a particular job. If pressed to do so, borgs are completely at liberty to advise crew that they don't have the firmware loaded for a particular module, then do a terrible job or "shut down to prevent harm". Alternatively, the order should be ahelped then disregarded.

Spam-Demanding a Borg to State Laws

  • Don't spam the borg with repeated obnoxious "state law" requests. The borg may prioritize who they answer that request to.
    • For example, the borg can choose completely ignore this request from low-level crew members/visitors and only acknowledge the request from Heads of Staff.
    • Note: Even if they don't have the standard lawset, if the lawset isn't harmful then getting your valids on it or reverting them immediately is considered no fun allowed.