Subrules - Revision history

Kelaris: /* Social Conflict */

2026-08-20T10:00:14Z

Social Conflict

← Older revision		Revision as of 10:00, 20 August 2026
Line 44:		Line 44:
	* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.		* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.
	* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.		* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.
	** SC2.1 If a player notifies you via any OOC channel that they want to end an interaction for any reason, you are expected to drop it immediately.		** SC2.1 If a player notifies you via any OOC channel that they want to end an interaction for any reason, you are expected to drop it immediately. This one rule in this section is treated as a very serious rulebreak if not followed.
	* SC3. When involved in an argument or heated exchange, take a moment to check in with the players you are engaging with, in LOOC/SOOC, unless their consent sheet indicates they welcome social conflict roleplay. Ensure it remains a collaborative experience rather than unwanted interaction.		* SC3. When involved in an argument or heated exchange, take a moment to check in with the players you are engaging with, in LOOC/SOOC, unless their consent sheet indicates they welcome social conflict roleplay. Ensure it remains a collaborative experience rather than unwanted interaction.
	* SC4. Do not suddenly initiate abrasive, hostile, argumentative, or aggressive dialogue or behavior targeted at unfamiliar characters, unless their consent sheet or a LOOC check-in indicates they welcome social conflict roleplay. Know your audience.		* SC4. Do not suddenly initiate abrasive, hostile, argumentative, or aggressive dialogue or behavior targeted at unfamiliar characters, unless their consent sheet or a LOOC check-in indicates they welcome social conflict roleplay. Know your audience.

Kelaris: /* Social Fights */

2026-08-20T09:57:07Z

Social Fights

← Older revision		Revision as of 09:57, 20 August 2026
Line 55:		Line 55:
	* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.		* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.
	* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving lethal weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.		* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving lethal weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.
	* SF4. Behind a privacy holobarrier, you are free to use weapons, crit, kill, or even round remove someone. This only requires mutual prior informed OOC consent from the players involved. Turn off your suit sensors when doing this. What happens in private RP should not become a disruption for the rest of the station to deal with.		* SF4. Behind a privacy holobarrier, you are free to use lethal weapons, crit, kill, or even round remove someone. This only requires mutual prior informed OOC consent from the players involved. Turn off your suit sensors when doing this. What happens in private RP should not become a disruption for the rest of the station to deal with.

	==== Harmless Crime ====		==== Harmless Crime ====

Kelaris: /* Social Fights */

2026-08-20T09:56:39Z

Social Fights

← Older revision		Revision as of 09:56, 20 August 2026
Line 54:		Line 54:
	* SF1. Players are allowed to engage in light brawls with each other over social/roleplay issues, after escalation. These fights must have mutual prior OOC consent, avoid using lethal weapons, and should avoid fighting to crit or death. Some mishaps, especially due to trait combinations lowering crit/death thresholds, are understandable.		* SF1. Players are allowed to engage in light brawls with each other over social/roleplay issues, after escalation. These fights must have mutual prior OOC consent, avoid using lethal weapons, and should avoid fighting to crit or death. Some mishaps, especially due to trait combinations lowering crit/death thresholds, are understandable.
	* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.		* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.
	* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.		* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving lethal weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.
	* SF4. Behind a privacy holobarrier, you are free to use weapons, crit, kill, or even round remove someone. This only requires mutual prior informed OOC consent from the players involved. Turn off your suit sensors when doing this. What happens in private RP should not become a disruption for the rest of the station to deal with.		* SF4. Behind a privacy holobarrier, you are free to use weapons, crit, kill, or even round remove someone. This only requires mutual prior informed OOC consent from the players involved. Turn off your suit sensors when doing this. What happens in private RP should not become a disruption for the rest of the station to deal with.

Kelaris: /* Social Fights */

2026-08-19T20:30:56Z

Social Fights

← Older revision		Revision as of 20:30, 19 August 2026
Line 52:		Line 52:
	==== Social Fights ====		==== Social Fights ====

	* SF1. Players are allowed to engage in light brawls with each other over social/roleplay issues, after escalation. These fights must have mutual prior OOC consent, avoid using weapons, and should avoid fighting to crit or death. Some mishaps, especially due to trait combinations lowering crit/death thresholds, are understandable.		* SF1. Players are allowed to engage in light brawls with each other over social/roleplay issues, after escalation. These fights must have mutual prior OOC consent, avoid using lethal weapons, and should avoid fighting to crit or death. Some mishaps, especially due to trait combinations lowering crit/death thresholds, are understandable.
	* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.		* SF2. Do not continuously fight in public, becoming an ongoing disruption to the station. Do not escalate by assaulting security or bystanders without consent.
	* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.		* SF3. Mutual consent and prior admin permission are required for deadly fights or assaults (as non-antagonists), involving weapons, striking someone in crit, or otherwise intentionally resulting in someone being killed. Admins will frequently provide weapons, uplinks, or other assistance if asked, when approving this kind of fight.

Kelaris: /* Silicons */

2026-08-14T05:55:56Z

Silicons

← Older revision		Revision as of 05:55, 14 August 2026
Line 123:		Line 123:

	* SI1. Silicons should follow their laws to the best of their ability, and their interpretation of those laws should remain consistent throughout the round.		* SI1. Silicons should follow their laws to the best of their ability, and their interpretation of those laws should remain consistent throughout the round.
	* SI2. Unless overwritten by a law, crew are defined as all personnel on board the station with a Nanotrasen issued ID or registered on the crew manifest.		* SI2. Unless overwritten by a law, "crew" or "Nanotrasen personnel" are defined as all personnel on board the station with a Nanotrasen issued ID or registered on the crew manifest.
	* SI3. Unless overwritten by a law, '''"authorized''' crew" are defined as all of Command, all Dignitaries, and all agents of Central Command. These roles have permission to visit the AI satellite at will.		* SI3. Unless overwritten by a law, '''"authorized''' crew" are defined as all of Command, all Dignitaries, and all agents of Central Command. These roles have permission to visit the AI satellite at will.
	* SI4. Silicons on their roundstart laws are considered crew aligned and are prohibited from intentionally being a mechanical nuisance, danger, or threat to the crew, except when defending themselves or following orders.		* SI4. Silicons on their roundstart laws are considered crew aligned and are prohibited from intentionally being a mechanical nuisance, danger, or threat to the crew, except when defending themselves or following orders.

Kelaris: /* Social Conflict */

2026-08-11T06:54:54Z

Social Conflict

← Older revision		Revision as of 06:54, 11 August 2026
Line 37:		Line 37:

	==== Social Conflict ====		==== Social Conflict ====
	This is a complex ~~and nuanced~~ topic. These rules exist to provide clear expectations ~~for ideal circumstances~~, encouraging communication from all participants during ~~hostile~~ or heated exchanges, not to interfere with mutually desired in-character conflict, or to punish anyone for their character giving a grumpy or blunt response.		This is a complex topic. These rules exist to provide clear expectations, encouraging communication from all participants during abrasive or heated exchanges, not to interfere with mutually desired in-character conflict, or to punish anyone for their character giving a grumpy or blunt response.

	Administrative enforcement of these rules, except in severely harmful or repeating cases, is always going to involve discussion and mediation, sharing the intentions and perspective of everyone involved, rather than immediate punishment.		Administrative enforcement of these rules, except in severely harmful or repeating cases, is always going to involve discussion and mediation, sharing the intentions and perspective of everyone involved, rather than immediate punishment.

Kelaris: /* Social Conflict */

2026-08-11T06:37:19Z

Social Conflict

← Older revision		Revision as of 06:37, 11 August 2026
Line 39:		Line 39:
	This is a complex and nuanced topic. These rules exist to provide clear expectations for ideal circumstances, encouraging communication from all participants during hostile or heated exchanges, not to interfere with mutually desired in-character conflict, or to punish anyone for their character giving a grumpy or blunt response.		This is a complex and nuanced topic. These rules exist to provide clear expectations for ideal circumstances, encouraging communication from all participants during hostile or heated exchanges, not to interfere with mutually desired in-character conflict, or to punish anyone for their character giving a grumpy or blunt response.

	Administrative enforcement of these rules, except in severely harmful or repeating cases, is always going to involve discussion and mediation, sharing the intentions and perspective of everyone involved, rather than immediate punishment~~. Similarly, if we never get a complaint, admins are not going to become involved at all~~.		Administrative enforcement of these rules, except in severely harmful or repeating cases, is always going to involve discussion and mediation, sharing the intentions and perspective of everyone involved, rather than immediate punishment.

	In the interest of keeping the rules concise, more details may be found here for those that are interested: [[Social Conflict\|Reasoning and Examples]]		In the interest of keeping the rules concise, more details may be found here for those that are interested: [[Social Conflict\|Reasoning and Examples]]

Kelaris: /* Social Conflict */

2026-08-11T06:36:11Z

Social Conflict

← Older revision		Revision as of 06:36, 11 August 2026
Line 44:		Line 44:
	* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.		* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.
	* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.		* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.
	** SC2.1 If a player notifies you via ~~LOOC~~ that they want to end an interaction for any reason, you are expected to drop it immediately.		** SC2.1 If a player notifies you via any OOC channel that they want to end an interaction for any reason, you are expected to drop it immediately.
	* SC3. When involved in an argument or heated exchange, take a moment to check in with the players you are engaging with, in LOOC/SOOC, unless their consent sheet indicates they welcome social conflict roleplay. Ensure it remains a collaborative experience rather than unwanted interaction.		* SC3. When involved in an argument or heated exchange, take a moment to check in with the players you are engaging with, in LOOC/SOOC, unless their consent sheet indicates they welcome social conflict roleplay. Ensure it remains a collaborative experience rather than unwanted interaction.
	* SC4. Do not suddenly initiate abrasive, hostile, argumentative, or aggressive dialogue or behavior targeted at unfamiliar characters, unless their consent sheet or a LOOC check-in indicates they welcome social conflict roleplay. Know your audience.		* SC4. Do not suddenly initiate abrasive, hostile, argumentative, or aggressive dialogue or behavior targeted at unfamiliar characters, unless their consent sheet or a LOOC check-in indicates they welcome social conflict roleplay. Know your audience.

Kelaris: /* Social Conflict */

2026-08-11T06:23:59Z

Social Conflict

← Older revision		Revision as of 06:23, 11 August 2026
Line 37:		Line 37:

	==== Social Conflict ====		==== Social Conflict ====
	This is a complex topic. In the interest of keeping the rules concise, more details may be found here for those that are interested: [[Social Conflict\|Reasoning and Examples]]		This is a complex and nuanced topic. These rules exist to provide clear expectations for ideal circumstances, encouraging communication from all participants during hostile or heated exchanges, not to interfere with mutually desired in-character conflict, or to punish anyone for their character giving a grumpy or blunt response.

			Administrative enforcement of these rules, except in severely harmful or repeating cases, is always going to involve discussion and mediation, sharing the intentions and perspective of everyone involved, rather than immediate punishment. Similarly, if we never get a complaint, admins are not going to become involved at all.

			In the interest of keeping the rules concise, more details may be found here for those that are interested: [[Social Conflict\|Reasoning and Examples]]
	* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.		* SC1. Characters can be in conflict, but the players involved should not be. Your character is a separate entity from yourself. Do not use in character actions to express negative out of character feelings.
	* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.		* SC2. If you become uncomfortable with any interaction for any reason, use LOOC to discuss the situation, ask for a change, or to disengage. You do not have to rationalize, justify, or defend your request. Just clearly communicate your wishes. Do not use OOC channels to escalate, vent about, or continue IC arguments.

Kelaris: /* Metagaming & Metashield */

2026-08-09T17:21:11Z

Metagaming & Metashield

← Older revision		Revision as of 17:21, 9 August 2026
Line 93:		Line 93:
	* MM1. You the player may know or suspect that something is a threat, but your character should only act on the actual evidence that you have in that round. Allow space for roleplay and activity to evolve. Don't seek to shut down antagonists at the first opportunity.		* MM1. You the player may know or suspect that something is a threat, but your character should only act on the actual evidence that you have in that round. Allow space for roleplay and activity to evolve. Don't seek to shut down antagonists at the first opportunity.
	** MM1.1 Several examples: You might hear a weird scream and lights shatter. That does not mean your character knows there is a Skia. You might see a Replicator carrying trash around, but until it harms the station it's just a weird little robot. If you see a shimmer, that doesn't mean your character knows there's a Ninja. Once someone witnesses a hostile, illegal, or destructive action, or there is supporting evidence, the entity may be called out and treated as a threat.		** MM1.1 Several examples: You might hear a weird scream and lights shatter. That does not mean your character knows there is a Skia. You might see a Replicator carrying trash around, but until it harms the station it's just a weird little robot. If you see a shimmer, that doesn't mean your character knows there's a Ninja. Once someone witnesses a hostile, illegal, or destructive action, or there is supporting evidence, the entity may be called out and treated as a threat.
	* MM1.2 Unknown forces on the station, such as Loneops, in obvious combat gear and weaponry can be immediately called out and treated as threats.		** MM1.2 Unknown forces on the station, such as Loneops, in obvious combat gear and weaponry can be immediately called out and treated as threats.
	* MM2. Do not presume the existence of antagonist items without evidence. Specifically do not search suspect's PDAs, headsets, pens, check items for chameleon properties, or perform implant searches unless there is a strong in-round reason to suspect the items.		* MM2. Do not presume the existence of antagonist items without evidence. Specifically do not search suspect's PDAs, headsets, pens, check items for chameleon properties, or perform implant searches unless there is a strong in-round reason to suspect the items.