From f3308976e0a7b20c0997c5675cced3d7983a10e0 Mon Sep 17 00:00:00 2001 From: DDrakov Date: Mon, 15 Jun 2026 10:29:04 +0700 Subject: [PATCH 1/5] Update 0 to 6 rules --- .../Guidebook/Rules/CoreRules/RuleC0.xml | 218 +----------------- .../Guidebook/Rules/CoreRules/RuleC1.xml | 26 ++- .../Guidebook/Rules/CoreRules/RuleC2.xml | 8 +- .../Guidebook/Rules/CoreRules/RuleC3.xml | 13 +- .../Guidebook/Rules/CoreRules/RuleC4.xml | 10 +- .../Guidebook/Rules/CoreRules/RuleC5.xml | 6 +- .../Guidebook/Rules/CoreRules/RuleC6.xml | 24 +- 7 files changed, 62 insertions(+), 243 deletions(-) diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml index 9a635920b8c..a7cf0fbcd8c 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml @@ -1,14 +1,22 @@  -[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] +[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] [color=#99ff99]Triad is an english speaking 18+ medium roleplay server[/color] -[color=#a4885c][head=3]0 Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] +[color=#a4885c][head=3]Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] • Admins will instead be held accountable through use of the Admin code of conduct. [color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] +[color=#ffff00][head=3]Severity guidelines:[/head][/color] + + • ★ / Minor infraction + + •[color=#f1c232]★★[/color] / Major infraction + + •[color=#cc0000]★★★[/color] / Extreme infraction + # Core Rules These rules apply at all times, including between rounds. @@ -28,210 +36,4 @@ - [textlink="Section 12. Escalation Guidelines" link="TriadRuleC12"] - [textlink="Section 13: Ship saving" link="TriadRuleC13"] - - [color=#ffff00][head=3]Severity guidelines:[/head][/color] - - • *1 - - Minor infraction - - •[color=#f1c232]*2[/color] - - Major infraction - - •[color=#cc0000]*3[/color] - - Extreme infraction - -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] - -[color=#a4885c]1.1[/color] Be respectful to others OOC. *1 - -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. *1 - -[color=#a4885c]1.3[/color]Don't metagame.*1 - -[color=#a4885c]1.4[/color] Don't spam or advertise. *1 - -[color=#a4885c]1.5[/color] Do not intentionally take actions that would negatively impact or disrupt others enjoyment of the game. *1 - -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. *2 - -[color=#a4885c]1.7[/color]Don't evade bans.*2 - -[color=#a4885c]1.8[/color] Don't self antag. *2 - -[color=#a4885c]1.9[/color]Don't ragequit/disconnect to avoid consequences.*2 - -[color=#a4885c]1.10[/color]Cheating and exploits are forbidden.*3 - -[color=#a4885c]1.11[/color] Respect others OOC consent and preferences.*3 - - -[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - -[color=#a4885c]2.1[/color]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.*2 - -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). *2 - -[color=#a4885c]2.3[/color]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Triad sector without consent of all parties involved.*2 - -[color=#a4885c]2.4[/color] Ghosting with the sole intent of spying on others personal activities is not permitted. *2 - - -[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. *1 - -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. *1 - -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. *1 - -[color=#a4885c]3.3A[/color] Meta-Communication is permitted so long as its ONLY about PvE content any other content should NOT be said unless its though In-game chats - -[color=#a4885c]3.4[/color] Discussion about the current around is allowed on the Triad Discord server however acting on information gained though this method is considered metagaming regardless of the information - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out of character information to give unfair treatment or advantages to others.) *1 - -[color=#a4885c]3.6[/color] Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)*1 - - -[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] - -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. *1 - -[color=#a4885c]4.2[/color] If a player is brought back to life they cannot recall more than foggy concepts of how they died. *1 - - -[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] - -[color=#a4885c]5.1[/color] Don't make meta references. *1 - -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - - -[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - -[color=#a4885c]6.1[/color] Your character is 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 rather than your own as the player. *1 - -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. *1 - -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. *1 - -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. *1 - -[color=#a4885c]6.5[/color] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away.*2 - -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) *2 - -[color=#a4885c]6.7[/color]Roleplaying an underage character is strictly forbidden. So is talk of such activities.*3 - - -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] - -[color=#a4885c]7.1[/color] Do not hide Antag objective items. *1 - -[color=#a4885c]7.2[/color] Do not make active use of known bugs in the game. *1 - - -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] - -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. *1 - -[color=#a4885c]8.2[/color] Arrivals as well as the Evac shuttle (and evac hallway) are considered Safezones in which this rule takes effect. *1 - - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] - -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. *1 - -[color=#a4885c]9.2[/color] DO NOT use ERP as bait for kill objectives, unless done with OOC consent of all parties involved. After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. *1 - -[color=#a4885c]9.3[/color] Do not kinkshame. *1 - -[color=#a4885c]9.4[/color] You MUST use the (-) subtle command for any and all erotic roleplay material. *1 - -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. *1 - -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. *1 - -[color=#a4885c]9.7[/color] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in character.*2 - -[color=#a4885c]9.8[/color] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP.*2 - -[color=#a4885c]9.9[/color] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket.*3 - -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). *3 - -[color=#a4885c]9.11[/color] People are not permitted to engage in acts of ERP in high traffic zones shush as the CC Hallways and docking ports (Maints, Dorms, Offices and secure areas less travelled parts are fine) - - -[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] - -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. *1 - -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. *1 - -[color=#a4885c]10.3[/color] Don't abuse your position of power. *1 - -[color=#a4885c]10.4[/color] You are expected to roleplay with others, this includes antagonists. *1 - -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. *1 - - -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] - -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. *1 - -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. *1 - -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. *1 - -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. *1 - - -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] - -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. *1 - -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. *1 - -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. *1 - -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. *1 - - - -[color=#ffff00][head=3]Section 13: Ship saving[/head][/color] - -13.1[/color] Ships are to be no larger than 80x50 tiles. [color=#a4885c] *1 - -13.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. [color=#a4885c] *2 - -13.3[/color] Do not exploit the stash to duplicate items. This especially goes for contraband. [color=#a4885c] *3 - -13.4[/color] Do not use inventories to circumvent stash restrictions. [color=#a4885c] *2 - -13.5[/color] Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission. [color=#a4885c] *1 - -13.5A[/color] You may not load from backup if your ship was destroyed by hostile elements such as Automated defences/offences (Drones, LPB, ect) [color=#a4885c] - -13.6[/color] Do not under any circumstances modify a ship save file without admin permission (like with the engine update). [color=#a4885c] *2 - -13.7[/color] Do not go afk for extended periods on your ship (like logging off to sleep). The ship saving is provided to allow people to save progress without the need to do this. UNATTENDED SHIPS WILL BE REMOVED. [color=#a4885c] *1 - -13.8[/color] DO NOT ADD MORE THAN THE LISTED AMOUNTS PER RESPECTIVE STASH: [color=#a4885c] *3 - -Medical: 2 *3 - -Armory/Hardsuit: 1 *3 - -Default: 2 *3 - -Botany: 1 *3 - -13.9[/color] Thrusters regardless of size must be exposed to space at all times there should be no walls separating the thruster from space. (Grills may protect them) [color=#a4885c] *2 - diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml index efd4c3fd5a3..5b74513f262 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml @@ -1,25 +1,29 @@  [color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] -[color=#a4885c]1.1[/color] Be respectful to others OOC. *1 +[color=#a4885c]1.1[/color] Be respectful to others OOC. ★ -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. *1 +[color=#a4885c]1.2[/color] Do not use hate speech, racism, or other bigoted remarks. ★ -[color=#a4885c]1.3[/color]Don't metagame.*1 +[color=#a4885c]1.3[/color] Do not metagame. ★ -[color=#a4885c]1.4[/color] Don't spam or advertise. *1 +[color=#a4885c]1.4[/color] Do not spam or advertise. ★ -[color=#a4885c]1.5[/color] Do not intentionally take actions that would negatively impact or disrupt others enjoyment of the game. *1 +[color=#a4885c]1.5[/color] Do not intentionally take actions that negatively impact or disrupt others' enjoyment of the game. ★ -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. *2 +[color=#a4885c]1.6[/color] Avoid discussing controversial topics such as self-harm or rape in public. ★★ -[color=#a4885c]1.7[/color]Don't evade bans.*2 +[color=#a4885c]1.7[/color] Do not evade bans. ★★ -[color=#a4885c]1.8[/color] Don't self antag. *2 +[color=#a4885c]1.8[/color] Do not intentionally create unnecessary conflict or disruption without reasonable in-character justification. ★★ -[color=#a4885c]1.9[/color]Don't ragequit/disconnect to avoid consequences.*2 +[color=#a4885c]1.9[/color] Do not cryo or disconnect to avoid in-character consequences. ★ -[color=#a4885c]1.10[/color]Cheating and exploits are forbidden.*3 +[color=#a4885c]1.10[/color] Cheating and exploiting bugs are forbidden. ★★★ -[color=#a4885c]1.11[/color] Respect others OOC consent and preferences.*3 +[color=#a4885c]1.11[/color] Respect others' OOC consent and preferences. ★★★ + +[color=#a4885c]1.11[/color] Suicide RP is prohibited. Many players may be dealing with personal struggles, and the game should remain a comfortable environment for everyone. Therefore, portraying suicide is not allowed, regardless of roleplay context. ★★ + +[color=#a4885c]1.12[/color] Roleplaying an underage character is strictly forbidden. So is talk of such activities. ★★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml index e3229db4459..95641e9e3ea 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml @@ -1,11 +1,11 @@ [color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] -[color=#a4885c]2.1[/color]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.*2 +[color=#a4885c]2.1[/color] If you are banned from a role, you may not play that role. This includes seeking or accepting promotions into restricted roles, as well as taking ghost roles that occupy those positions. ★★ -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). *2 +[color=#a4885c]2.2[/color] Do not intentionally become a major problem, nuisance, or disruption to civilians while not being an antagonist (i.e. self-antagging). ★★ -[color=#a4885c]2.3[/color]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Triad Sector without consent of all parties involved.*2 +[color=#a4885c]2.3[/color] Livestreaming rounds to others or sharing recorded gameplay outside of the Triad Sector without the consent of all parties involved is strictly prohibited. ★★ -[color=#a4885c]2.4[/color] Ghosting with the sole intent of spying on others personal activities is not permitted. *2 +[color=#a4885c]2.4[/color] Ghosting with the sole purpose of spying on the private activities of others is not permitted. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml index 40dd81f4017..a041e455573 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml @@ -1,17 +1,16 @@  [color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. *1 +[color=#a4885c]3.1[/color] Use each chat channel for its intended purpose. ★ -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. *1 +[color=#a4885c]3.2[/color] Characters do not retain any knowledge of events that occurred while they were dead. ★ -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. *1 +[color=#a4885c]3.3[/color] Do not use information obtained through meta-communication to perform PvP or other hostile actions against players. ★ -[color=#a4885c]3.3A[/color] Meta-Communication is permitted so long as its ONLY about PvE content any other content should NOT be said unless its though In-game chats +[color=#a4885c]3.3A[/color] Meta-communication is permitted only for discussing PvE content. All other information must be communicated through in-game channels. ★ -[color=#a4885c]3.4[/color] Discussion about the current around is allowed on the Triad Discord server however acting on information gained though this method is considered metagaming regardless of the information +[color=#a4885c]3.4[/color] Discussion about the current round is permitted on the Triad Discord server. However, acting on any information obtained through these discussions is considered metagaming, regardless of the nature of the information. ★ -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out of character information to give unfair treatment or advantages to others.) *1 +[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. Using in-character or out-of-character information to unfairly target, favor, or grant advantages to others is prohibited. ★ -[color=#a4885c]3.6[/color] Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)*1 diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml index 56b1e6bcd29..252cfddbd75 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml @@ -1,7 +1,13 @@  [color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. *1 +[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. ★ -[color=#a4885c]4.2[/color] If a player is brought back to life they cannot recall more than foggy concepts of how they died. *1 +[color=#a4885c]4.2[/color] Characters who are revived retain only vague memories of the circumstances surrounding their death. They may remember broad details, but not specific events or individuals involved. For example, if you were shot, you may remember being shot but not who shot you. If you accidentally set yourself on fire with a welder, you may remember being burned but not how it occurred. ★ + +[color=#a4885c]4.3[/color] Players who respawn instead of being resurrected lose all memories of the current shift and may not return to the site of their previous death. ★ + +[color=#a4885c]4.3A[/color] Players who receive information about their death or previous circumstances from others may reclaim or repair any lost property, but should not use such information to regain memories or act on past events. + +[color=#a4885c]4.3B[/color] Special exception for the ship-saving feature: players who encounter their former personal ship may recover it, [bold]provided ownership is transferred by a Command role or, if none are available, by an administrator[/bold]. diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml index 82fa544d833..e0293972059 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml @@ -1,9 +1,7 @@  [color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] -[color=#a4885c]5.1[/color] Don't make meta references. *1 +[color=#a4885c]5.1[/color] Don't make meta references. Try to be creative by picking a believable and fitting name within the game's lore. ★ -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. +[color=#a4885c]5.2[/color] Ship names, particularly those of Command roles, must be appropriate and consistent with the sector's lore and the owner's character. Low roleplay names, direct meta references, and names unrelated to the setting are prohibited. Examples include naming the Overseer's Ravager "Goober", "Meow Meow Meow", or similarly inappropriate names. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml index b29b256ff67..fa3d906068a 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml @@ -1,17 +1,27 @@  [color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] -[color=#a4885c]6.1[/color] Your character is 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 rather than your own as the player. *1 +[color=#a4885c]6.1[/color] Your character is separate from you, the player. Their actions, feelings, and knowledge should be based on their in-character experiences, not your own. ★ -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. *1 +[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Accurate roleplay is never an excuse for rule violations. If you are unsure, Ahelp for clarification. ★ -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. *1 +[color=#a4885c]6.3[/color] By selecting a job, you are expected to fulfill the responsibilities of that role whenever reasonably required during the shift. ★ -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. *1 +[color=#a4885c]6.3A[/color] Choosing a job implies a commitment to that role for the duration of the shift. Frequently switching between roles is considered a violation of Rule 6.3. ★ -[color=#a4885c]6.5[/color] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away.*2 +[color=#a4885c]6.3B[/color] Transferring to a higher position, such as a Command role, is permitted only with proper in-character justification. Administrative convenience or gameplay necessity alone are not valid reasons. For example, becoming an Overseer solely to perform a deed transfer is not permitted. ★ -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) *2 +[color=#a4885c]6.3C[/color] Once a character assumes a Command role, they are expected to remain in that position for the rest of the shift, even if they cryo. You may play other characters in different roles, but the same character may not move from a Command role to another Command position or to a lower role. ★ -[color=#a4885c]6.7[/color]Roleplaying an underage character is strictly forbidden. So is talk of such activities.*3 +[color=#a4885c]6.4[/color] Do not intentionally interrupt or disregard roleplay in order to gain an unfair advantage while another player is actively roleplaying or typing. ★ + +[color=#a4885c]6.4A[/color] Using LOOC to argue about in-game situations or otherwise gain an advantage in roleplay is considered low-roleplay behavior and breaks immersion. For example, arguing in LOOC after being caught breaking into Security. ★ + +[color=#a4885c]6.4B[/color] Potential rule violations or disputes regarding the legality of actions should not be argued through LOOC. Use Ahelp to seek clarification. If no administrator is available, postpone, cancel, or de-escalate the situation until a ruling can be made. *1 + +[color=#a4885c]6.5[/color] Respect the consent, dignity, and boundaries of others. If someone asks you through LOOC to stop bothering them, you are expected to do so. If you believe this rule is being abused, Ahelp immediately. ★★ + +[color=#a4885c]6.6[/color] Do not dismantle critical station infrastructure, such as atmospheric systems, power cables, or other essential components, for non-essential activities without the knowledge and approval of Command. ★★ + +[color=#a4885c]6.7[/color] Avoid direct references to internet culture, memes, or netspeak in-character. Excessive use of phrases such as "tung tung tung sahur", "skibidi toilet", or similar expressions is considered low roleplay and immersion-breaking. ★★★ From 06db3ad0b27c456c11ac8f9d7bcf75f4a902443b Mon Sep 17 00:00:00 2001 From: DDrakov Date: Sun, 28 Jun 2026 10:55:54 +0700 Subject: [PATCH 2/5] Update 6-13 rules, comment faction rules for the time being, changes the ftl, update the row and naming of rules --- .../Locale/en-US/_Triad/guidebook/guides.ftl | 10 +++--- .../Prototypes/_Triad/Guidebook/rules.yml | 11 ++++--- .../Guidebook/Rules/CoreRules/RuleC0.xml | 9 +++--- .../Guidebook/Rules/CoreRules/RuleC10.xml | 14 +++++--- .../Guidebook/Rules/CoreRules/RuleC11.xml | 16 +++++++--- .../Guidebook/Rules/CoreRules/RuleC12.xml | 32 ++++++++++++++++--- .../Guidebook/Rules/CoreRules/RuleC13.xml | 31 +----------------- .../Guidebook/Rules/CoreRules/RuleC6.xml | 2 +- .../Guidebook/Rules/CoreRules/RuleC7.xml | 14 ++++++-- .../Guidebook/Rules/CoreRules/RuleC8.xml | 4 +-- .../Guidebook/Rules/CoreRules/RuleC9.xml | 29 +++++++++-------- 11 files changed, 94 insertions(+), 78 deletions(-) diff --git a/Resources/Locale/en-US/_Triad/guidebook/guides.ftl b/Resources/Locale/en-US/_Triad/guidebook/guides.ftl index 277ce390bb3..5239d6cf57b 100644 --- a/Resources/Locale/en-US/_Triad/guidebook/guides.ftl +++ b/Resources/Locale/en-US/_Triad/guidebook/guides.ftl @@ -6,10 +6,10 @@ guide-entry-section3 = Metagaming Section guide-entry-section4 = New Life Section guide-entry-section5 = Naming Section guide-entry-section6 = Roleplay Section -guide-entry-section7 = Powergaming Section +guide-entry-section7 = Point Of Interest and Safe Zone Section guide-entry-section8 = End-Of-Round Section -guide-entry-section9 = ERP Section +guide-entry-section9 = Erotic-Role-Play Section guide-entry-section10 = Command And Security Section -guide-entry-section11 = Antagonist Guidelines Section -guide-entry-section12 = Escalation Guidelines Section -guide-entry-section13 = Ship Saving Section +guide-entry-section11 = Escalation Guidelines Section +guide-entry-section12 = Ship Saving Section +guide-entry-section13 = Faction Section diff --git a/Resources/Prototypes/_Triad/Guidebook/rules.yml b/Resources/Prototypes/_Triad/Guidebook/rules.yml index 1be8275c050..4fcf6336e85 100644 --- a/Resources/Prototypes/_Triad/Guidebook/rules.yml +++ b/Resources/Prototypes/_Triad/Guidebook/rules.yml @@ -91,8 +91,9 @@ text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml" priority: 11 -- type: guideEntry - id: TriadRuleC13 - name: guide-entry-section13 - text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml" - priority: 12 +# Triad : In progress Faction rules +# - type: guideEntry +# id: TriadRuleC13 +# name: guide-entry-section13 +# text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml" +# priority: 12 diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml index a7cf0fbcd8c..914b25a75a5 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml @@ -26,14 +26,15 @@ - [textlink="Section 2. Gameplay Rules" link="TriadRuleC2"] - [textlink="Section 3. Metagaming Rules" link="TriadRuleC3"] - [textlink="Section 4. New-life Rules" link="TriadRuleC4"] - - [textlink="Section 5. Character Naming Rules" link="TriadRuleC5"] + - [textlink="Section 5. Naming Rules" link="TriadRuleC5"] - [textlink="Section 6. Roleplay Rules" link="TriadRuleC6"] - - [textlink="Section 7. Powergaming Rules" link="TriadRuleC7"] + - [textlink="Section 7. Point Of Interest and Safe Zone Rules" link="TriadRuleC7"] - [textlink="Section 8. End-Of-Round (EOR) Rules" link="TriadRuleC8"] - [textlink="Section 9. Erotic-Role-Play (ERP) Rules" link="TriadRuleC9"] - [textlink="Section 10. Command and Security Rules" link="TriadRuleC10"] - [textlink="Section 11. Antagonist Rules" link="TriadRuleC11"] - - [textlink="Section 12. Escalation Guidelines" link="TriadRuleC12"] - - [textlink="Section 13: Ship saving" link="TriadRuleC13"] + - [textlink="Section 12. Ship saving" link="TriadRuleC12"] + + diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml index fbd29fb7359..b3a485c61d6 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml @@ -1,13 +1,17 @@  [color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. *1 +[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. ★ -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. *1 +[color=#a4885c]10.2[/color] Both Security and Command are required to know Space Law, Standard Operating Procedures, and Alert Procedures ★ -[color=#a4885c]10.3[/color] Don't abuse your position of power. *1 +[color=#a4885c]10.3[/color] Don't abuse your position of power, this includes money withdrawal for “payment” upon one self without consulting the payment/hour or transferring your command ship deed to be used outside of your command roles. ★ -[color=#a4885c]10.4[/color] You are expected to roleplay with others, this includes antagonists. *1 +[color=#a4885c]10.4[/color] You are expected to roleplay with others and respond to situations that need your role to function.★ -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. *1 +[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. ★ + +[color=#a4885c]10.6[/color] Command characters must not have any disability, quirk, or traits that can impede the role function and communication. ★ + +[color=#a4885c]10.7[/color] Command personnel who signed up for the role but not actively do what the role demands to do (i.e only using the command role for looking at new ship/doing activities that are not within the command SoP) are heavily discouraged and connected to 10.1 rule break. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml index 6777977441a..982231fad82 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml @@ -1,11 +1,17 @@  -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] +[color=#ffff00][head=3]Section 11: Escalation Guidelines[/head][/color] -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. *1 +[color=#a4885c]11.1[/color] Escalate conflicts reasonably. Use common sense when deciding how far a situation should go. A spilled drink might lead to an argument or fistfight, but it should not normally escalate into a gunfight. ★ -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. *1 +[color=#a4885c]11.2[/color] Use words and intimidation before lethal force. When starting or escalating a conflict, you should talk, posture, threaten violence, brandish a weapon, or fire a warning shot before attempting to kill someone. ★ -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. *1 +[color=#a4885c]11.2A[/color] Use non-lethal options when appropriate. Command, security, and antagonists such as pirates are expected to carry and attempt to use non-lethal options before resorting to lethal force. Other roles with access to non-lethals should also make a reasonable effort to use them first. Punching someone is considered non-lethal. ★ -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. *1 +[color=#a4885c]11.3[/color] Accept surrender. If someone offers a genuine surrender, you must accept it, regardless of how heated the situation has become. ★ + +[color=#a4885c]11.4[/color] Do not fake surrender. You may not intentionally offer a false surrender. ★ + +[color=#a4885c]11.4A[/color] Exceptions are made for those in factions. You may fake surrender but it will have heavy IC consequences placed on each faction’s SoP. ★ + +[color=#a4885c]11.5[/color] Do not intentionally round-remove players. If you kill someone, you are expected to revive them when it is safe to do so. You may restrain them first. If they attempt to escape and you are forced to kill them again, you are not required to revive them a second time, but you must preserve their body. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml index a04ad761f42..f788519aacc 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml @@ -1,11 +1,33 @@  -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] +[color=#ffff00][head=3]Section 12: Ship saving Rules[/head][/color] -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. *1 +[color=#a4885c]12.1[/color] Ships must not exceed a maximum size of 80×50 tiles. ★ -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. *1 +[color=#a4885c]12.2[/color] Do not abuse the ship save system to avoid in-character consequences. ★★ -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. *1 +[color=#a4885c]12.3[/color] Do not exploit the ship stash system to duplicate items. This prohibition especially applies to contraband. ★★★ -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. *1 +[color=#a4885c]12.4[/color] Ship backups may only be loaded with prior administrator approval and are intended solely for server-related or other out-of-character (OOC) issues. You must submit an Ahelp before loading a backup. ★ + +[color=#a4885c]12.4A[/color] You may not restore a ship from backup if it was destroyed through normal in-character gameplay, including hostile entities such as automated defenses, drones, Long-Range Projectile Batteries (LPBs), or similar hazards. ★ + +[color=#a4885c]12.4B[/color] Whenever a ship backup is restored, you must notify the administration through an Ahelp or ticket so the restoration can be documented. + +[color=#a4885c]12.4C[/color] If you fail to save your ship within the 10-minute End-of-Round grace period due to your own negligence (for example, delaying the save or being AFK), you are not entitled to administrative compensation or restoration for any resulting loss of progress. + +[color=#a4885c]12.5[/color] Under no circumstances may you modify a ship save file without prior administrator approval, including modifications made to accommodate engine updates. ★★ + +[color=#a4885c]12.6[/color] Do not leave your ship unattended due to being AFK or otherwise absent for an extended period of time. ★ + +[color=#a4885c]12.6A[/color] An unattended ship may be declared abandoned by Command within the sector or local area and subsequently salvaged. Any loss resulting from leaving your ship unattended is the responsibility of the owner. + +[color=#a4885c]12.7[/color] All thrusters, regardless of size, must remain directly exposed to space. No walls may obstruct the exhaust path between a thruster and open space. Protective grills are permitted. ★★ + +[color=#a4885c]12.8A[/color] Multiple thrusters may not occupy the same location or share the same thruster engine block. ★ + +[color=#a4885c]12.8B[/color] For additional guidance regarding valid thruster layouts, refer to the Thruster Placement documentation in the Discord #admin-questions channel. + +[color=#a4885c]12.9[/color] Construction of complex or poorly optimized machinery that significantly impacts server performance is strongly discouraged. Players will normally receive up to two warnings to remove or modify the contraption. Failure to comply may result in the offending machinery being removed by administrators. ★ + +[color=#a4885c]12.9A[/color] Intentionally constructing or operating machinery for the purpose of degrading server performance or causing server lag constitutes abuse. Such behavior may result in immediate administrative action, including orders to cease, removal of the affected ship or machinery, administrative notes, or additional disciplinary action. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml index 80d8eb84495..aa5d3a272e2 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml @@ -1,32 +1,3 @@  -[color=#ffff00][head=3]Section 13: Ship saving[/head][/color] - -13.1[/color] Ships are to be no larger than 80x50 tiles. [color=#a4885c] *1 - -13.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. [color=#a4885c] *2 - -13.3[/color] Do not exploit the stash to duplicate items. This especially goes for contraband. [color=#a4885c] *3 - -13.4[/color] Do not use inventories to circumvent stash restrictions. [color=#a4885c] *2 - -13.5[/color] Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission. [color=#a4885c] *1 - -13.5A[/color] You may not load from backup if your ship was destroyed by hostile elements such as Automated defences/offences (Drones, LPB, ect) [color=#a4885c] - -13.6[/color] Do not under any circumstances modify a ship save file without admin permission (like with the engine update). [color=#a4885c] *2 - -13.7[/color] Do not go afk for extended periods on your ship (like logging off to sleep). The ship saving is provided to allow people to save progress without the need to do this. UNATTENDED SHIPS WILL BE REMOVED. [color=#a4885c] *1 - -13.8[/color] DO NOT ADD MORE THAN THE LISTED AMOUNTS PER RESPECTIVE STASH: [color=#a4885c] *3 - -Medical: 2 *3 - -Armory/Hardsuit: 1 *3 - -Default: 2 *3 - -Botany: 1 *3 - -13.9[/color] Thrusters regardless of size must be exposed to space at all times there should be no walls separating the thruster from space. (Grills may protect them) [color=#a4885c] *2 - +[color=#ffff00][head=3]Section 13: Faction Rules[/head][/color] diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml index fa3d906068a..b52fb38fcd4 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml @@ -17,7 +17,7 @@ [color=#a4885c]6.4A[/color] Using LOOC to argue about in-game situations or otherwise gain an advantage in roleplay is considered low-roleplay behavior and breaks immersion. For example, arguing in LOOC after being caught breaking into Security. ★ -[color=#a4885c]6.4B[/color] Potential rule violations or disputes regarding the legality of actions should not be argued through LOOC. Use Ahelp to seek clarification. If no administrator is available, postpone, cancel, or de-escalate the situation until a ruling can be made. *1 +[color=#a4885c]6.4B[/color] Potential rule violations or disputes regarding the legality of actions should not be argued through LOOC. Use Ahelp to seek clarification. If no administrator is available, postpone, cancel, or de-escalate the situation until a ruling can be made. ★ [color=#a4885c]6.5[/color] Respect the consent, dignity, and boundaries of others. If someone asks you through LOOC to stop bothering them, you are expected to do so. If you believe this rule is being abused, Ahelp immediately. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml index fe6a3d2fb9b..8de17cba77f 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml @@ -1,7 +1,15 @@  -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] +[color=#ffff00][head=3]Section 7: Point of Interest and Safe Zone Rules[/head][/color] -[color=#a4885c]7.1[/color] Do not hide Antag objective items. *1 +[color=#a4885c]7.1[/color] Point of Interest (PoI) structures must not be disabled, destroyed, or rendered inoperable unless authorized by higher command or required for a specific approved purpose. ★ -[color=#a4885c]7.2[/color] Do not make active use of known bugs in the game. *1 +[color=#a4885c]7.2[/color] Point of Interest locations must remain dedicated to their intended function unless higher command explicitly authorizes an alternative use. (Example: Establishing a temporary medical treatment area in Bahama Mama's during an emergency is permitted, but converting Edison Powerplant into a data center by using its infrastructure without approval is prohibited.) ★ + +[color=#a4885c]7.3[/color] Central Command (CC) and Medical Department (MD) are designated as Safe Zones. + +[color=#a4885c]7.3A[/color] Acts of uncivilized conduct within a Safe Zone—including murder, assault, theft, sabotage, or malicious damage to another player's ship or property—will be handled in-character by Security and may also result in out-of-character administrative action for serious violations. ★★ + +[color=#a4885c]7.3B[/color] A radius of 512 meters surrounding a designated Safe Zone structure is considered part of the Safe Zone. + +[color=#a4885c]7.4[/color] Point of Interest locations that are not designated Safe Zones, such as Edison Powerplant, Drillsite, and similar facilities, must not be intentionally damaged except during authorized circumstances such as faction conflicts, administrative events, or other approved scenarios. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml index 650eccd9308..84b1b5b408d 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml @@ -1,7 +1,7 @@  [color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. *1 +[color=#a4885c]8.1[/color] End-of-Round Griefing (EORG) is strictly prohibited under all circumstances. This includes, but is not limited to, engaging in combat, using explosives or hazardous chemicals, destroying property, or committing any other disruptive or malicious actions. ★ -[color=#a4885c]8.2[/color] Arrivals as well as the Evac shuttle (and evac hallway) are considered Safezones in which this rule takes effect. *1 +[color=#a4885c]8.2[/color] The End-of-Round (EOR) period begins 10 minutes after the round-end evacuation announcement (shuttle evacuation announcement). This grace period exists to allow players sufficient time to secure or recover their ships without interference. diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml index 72305f6074a..391bf36b726 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml @@ -1,26 +1,29 @@ - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] + +[color=#ffff00][head=3]Section 9: Erotic Roleplay (ERP) Rules[/head][/color] -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. *1 +[color=#a4885c]9.1[/color] Erotic Roleplay (ERP) does not take precedence over your assigned duties. If your role requires your attention or you are requested to perform your job, you must respond or return to your duties as soon as reasonably possible. ★ -[color=#a4885c]9.2[/color] DO NOT use ERP as bait for kill objectives, unless done with OOC consent of all parties involved. After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. *1 +[color=#a4885c]9.2[/color] ERP must not be used or offered as bait to lure, ambush, or kill another player. ★ -[color=#a4885c]9.3[/color] Do not kinkshame. *1 +[color=#a4885c]9.3[/color] Do not harass, ridicule, or shame other players for their consensual roleplay preferences. ★ -[color=#a4885c]9.4[/color] You MUST use the (-) subtle command for any and all erotic roleplay material. *1 +[color=#a4885c]9.4[/color] All ERP-related dialogue or roleplay must be conducted using the subtle (-) or whisper commands. ★ -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. *1 +[color=#a4885c]9.4A[/color] When engaging in ERP, ensure that any device capable of transmitting your voice (such as shuttle consoles, HandiComm, or similar communication systems) is disabled to avoid disturbing other players. ★ -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. *1 +[color=#a4885c]9.5[/color] Do not spam or excessively use radio channels for NSFW topics. This does not prohibit discussing such topics altogether; however, repeated hornyposting, shitposting, depression posting, or other disruptive behavior is prohibited. ★ -[color=#a4885c]9.7[/color] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in character.*2 +[color=#a4885c]9.6[/color] Do not engage in or publicly discuss extreme sexual fetishes. Public spaces include radio channels, spoken dialogue in public areas, overt public actions, or any activity visible through cameras. ★ -[color=#a4885c]9.8[/color] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP.*2 +[color=#a4885c]9.7[/color] ERP involving non-sentient creatures is prohibited. This includes creatures that resemble beasts, even if they may later become sentient. ★★ -[color=#a4885c]9.9[/color] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket.*3 +[color=#a4885c]9.8[/color] When roleplaying another player's character, you must obtain out-of-character (OOC) consent from that character's owner before engaging in ERP involving them. ★★ -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). *3 +[color=#a4885c]9.9[/color] Be mindful of both in-character (IC) and out-of-character (OOC) consent. If your OOC consent is violated or disregarded, immediately submit an Ahelp or open an administrative ticket. ★★★ -[color=#a4885c]9.11[/color] People are not permitted to engage in acts of ERP in high traffic zones shush as the CC Hallways and docking ports (Maints, Dorms, Offices and secure areas less travelled parts are fine) +[color=#a4885c]9.10[/color] Extreme roleplay themes, including but not limited to snuff, abuse, non-consensual scenarios (noncon), and similar content, are only permitted when all participating parties have provided prior OOC consent. If you are uncertain whether a scenario is permitted, contact an administrator through an Ahelp. Keep such roleplay private. ★★★ +[color=#a4885c]9.11[/color] ERP must not take place in public areas. Ensure you are in a private, secure location, such as a personal ship, a lockable room, dormitories, or another secluded area. + +[color=#a4885c]9.11A[/color] If another player discovers your ERP and requests that you stop or relocate, you must either move to a different private location or cease the activity. ★ From a353f4137621f5f398487ac9232f2e5ebed45469 Mon Sep 17 00:00:00 2001 From: DDrakov Date: Tue, 30 Jun 2026 18:45:37 +0700 Subject: [PATCH 3/5] Fix linter --- Resources/Prototypes/_Triad/Guidebook/rules.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Resources/Prototypes/_Triad/Guidebook/rules.yml b/Resources/Prototypes/_Triad/Guidebook/rules.yml index 4fcf6336e85..2a1d5e13437 100644 --- a/Resources/Prototypes/_Triad/Guidebook/rules.yml +++ b/Resources/Prototypes/_Triad/Guidebook/rules.yml @@ -17,7 +17,7 @@ - TriadRuleC10 - TriadRuleC11 - TriadRuleC12 - - TriadRuleC13 + # - TriadRuleC13 - type: guideEntry id: TriadRuleC1 From 6d358f5fe866a876b5016410f6fc61964c365669 Mon Sep 17 00:00:00 2001 From: DDrakov Date: Tue, 30 Jun 2026 19:53:37 +0700 Subject: [PATCH 4/5] Update rules from Eillyrea --- .../Locale/en-US/_Triad/guidebook/guides.ftl | 10 ++-- .../Prototypes/_Triad/Guidebook/rules.yml | 10 ++-- .../Guidebook/Rules/CoreRules/RuleC0.xml | 50 ++++++++++++------- .../Guidebook/Rules/CoreRules/RuleC1.xml | 28 +++-------- .../Guidebook/Rules/CoreRules/RuleC10.xml | 14 +++--- .../Guidebook/Rules/CoreRules/RuleC11.xml | 26 +++++++--- .../Guidebook/Rules/CoreRules/RuleC12.xml | 31 +----------- .../Guidebook/Rules/CoreRules/RuleC13.xml | 1 + .../Guidebook/Rules/CoreRules/RuleC2.xml | 20 ++++++-- .../Guidebook/Rules/CoreRules/RuleC3.xml | 12 ++--- .../Guidebook/Rules/CoreRules/RuleC4.xml | 12 +++-- .../Guidebook/Rules/CoreRules/RuleC5.xml | 6 ++- .../Guidebook/Rules/CoreRules/RuleC6.xml | 24 ++++----- .../Guidebook/Rules/CoreRules/RuleC7.xml | 14 +++--- .../Guidebook/Rules/CoreRules/RuleC8.xml | 36 +++++++++++-- .../Guidebook/Rules/CoreRules/RuleC9.xml | 28 +++-------- 16 files changed, 163 insertions(+), 159 deletions(-) diff --git a/Resources/Locale/en-US/_Triad/guidebook/guides.ftl b/Resources/Locale/en-US/_Triad/guidebook/guides.ftl index 5239d6cf57b..ebf7e643930 100644 --- a/Resources/Locale/en-US/_Triad/guidebook/guides.ftl +++ b/Resources/Locale/en-US/_Triad/guidebook/guides.ftl @@ -1,15 +1,15 @@ guide-entry-shipyard-gondola = Gondola -guide-entry-section1 = Behavior Section +guide-entry-section1 = Use of Language and Respect Section guide-entry-section2 = Game Server Section guide-entry-section3 = Metagaming Section guide-entry-section4 = New Life Section guide-entry-section5 = Naming Section guide-entry-section6 = Roleplay Section guide-entry-section7 = Point Of Interest and Safe Zone Section -guide-entry-section8 = End-Of-Round Section -guide-entry-section9 = Erotic-Role-Play Section -guide-entry-section10 = Command And Security Section -guide-entry-section11 = Escalation Guidelines Section +guide-entry-section8 = Erotic/Extreme Roleplay Section +guide-entry-section9 = Command, Security, and TDF Guidelines +guide-entry-section10 = Escalation Guidelines Section +guide-entry-section11 = Ship Saving and Design guide-entry-section12 = Ship Saving Section guide-entry-section13 = Faction Section diff --git a/Resources/Prototypes/_Triad/Guidebook/rules.yml b/Resources/Prototypes/_Triad/Guidebook/rules.yml index 2a1d5e13437..8b078940a52 100644 --- a/Resources/Prototypes/_Triad/Guidebook/rules.yml +++ b/Resources/Prototypes/_Triad/Guidebook/rules.yml @@ -85,11 +85,11 @@ text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml" priority: 10 -- type: guideEntry - id: TriadRuleC12 - name: guide-entry-section12 - text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml" - priority: 11 +# - type: guideEntry +# id: TriadRuleC12 +# name: guide-entry-section12 +# text: "/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml" +# priority: 11 # Triad : In progress Faction rules # - type: guideEntry diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml index 914b25a75a5..c1ac7ca01dd 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml @@ -1,13 +1,25 @@ - -[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] + +[head=1][color=#FFEF00]Introduction[/head][/color] -[color=#99ff99]Triad is an english speaking 18+ medium roleplay server[/color] +[color=#FFFACD]Triad is an 18+ roleplay server, with a focus on providing a place for players to roleplay in a mature environment. This has the allowance of sexual activities to happen, but this does not mean the priority of the server is erotic content.[/color] -[color=#a4885c][head=3]Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] +We recommend keeping the game at an arms length. Healthy distance between yourself and roleplay is essential for maintaining IC and OOC separation. Do not interfere with your physical or mental health by overcommitting to a game too heavily. - • Admins will instead be held accountable through use of the Admin code of conduct. +It's easy to get immersed in what's happening or invested in your characters' story and their successes. This is not an MMO to grind, this is a place to make and tell stories. Loss and setbacks are part of those stories. Try to tell your character's story of overcoming them instead of reacting negatively to a game. -[color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] +[color=#a4885c][head=2]Clarifications[/head][/color] + +[color=#a4885c]1.[/color] Rules are intended to be enforced as written; should a conflict with interpretation of rules as written occur; regardless of outcome of prompting action: the ambiguous rule will be re-written to be futureproofed. These rules are intended as a promise made to our players regarding other players and staff conduct. Which can be used to reasonably set expectations. + +[color=#a4885c]2.[/color] Rules bind staff and players alike; while there is some discretion for staff breaches when pursued in the interest of the current round, server, or community at large; any such instance will be investigated. + +[color=#a4885c]3.[/color] Ahelp is intended for immediate term communication and interventions; issues requiring broader discussion or appeals for any ahelp action are to be relegated to tickets. + +[color=#a4885c]4.[/color] All tickets can be adjudicated either privately in a ticket or publicly via the discord. Ticket transcripts will be sent to you upon their conclusion. + +[color=#a4885c]5.[/color] LTAP (leaving to avoid punishment) by disconnecting, ignoring admin messages or otherwise will result in an appeal-only ban. + +[color=#FFFACD]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] [color=#ffff00][head=3]Severity guidelines:[/head][/color] @@ -22,19 +34,19 @@ Each section contains its own list of rules. Click on the section name to view the full version. - - [textlink="Section 1. Behavioral Rules" link="TriadRuleC1"] - - [textlink="Section 2. Gameplay Rules" link="TriadRuleC2"] - - [textlink="Section 3. Metagaming Rules" link="TriadRuleC3"] - - [textlink="Section 4. New-life Rules" link="TriadRuleC4"] - - [textlink="Section 5. Naming Rules" link="TriadRuleC5"] - - [textlink="Section 6. Roleplay Rules" link="TriadRuleC6"] - - [textlink="Section 7. Point Of Interest and Safe Zone Rules" link="TriadRuleC7"] - - [textlink="Section 8. End-Of-Round (EOR) Rules" link="TriadRuleC8"] - - [textlink="Section 9. Erotic-Role-Play (ERP) Rules" link="TriadRuleC9"] - - [textlink="Section 10. Command and Security Rules" link="TriadRuleC10"] - - [textlink="Section 11. Antagonist Rules" link="TriadRuleC11"] - - [textlink="Section 12. Ship saving" link="TriadRuleC12"] - + - [textlink="Section 1. Use of Language and Respect Section" link="TriadRuleC1"] + - [textlink="Section 2. Gameplay Section" link="TriadRuleC2"] + - [textlink="Section 3. Metagaming Section" link="TriadRuleC3"] + - [textlink="Section 4. New-life Section" link="TriadRuleC4"] + - [textlink="Section 5. Naming Section" link="TriadRuleC5"] + - [textlink="Section 6. Roleplay Section" link="TriadRuleC6"] + - [textlink="Section 7. Point Of Interest and Safe Zone Section" link="TriadRuleC7"] + - [textlink="Section 8. Erotic/Extreme Roleplay Section" link="TriadRuleC8"] + - [textlink="Section 9. Command, Security, and TDF Guidelines" link="TriadRuleC9"] + - [textlink="Section 10. Escalation Guidelines" link="TriadRuleC10"] + - [textlink="Section 11. Ship Saving and Design Section" link="TriadRuleC11"] + + diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml index 5b74513f262..1e7c5c827a0 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml @@ -1,29 +1,15 @@  -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] +[color=#ffff00][head=3]Section 1: Use of Language and Respect[/head][/color] -[color=#a4885c]1.1[/color] Be respectful to others OOC. ★ +[color=#a4885c]1.1[/color] Use English as your primary method of communication. You may talk in other languages briefly but avoid partaking in longer conversations in another language. -[color=#a4885c]1.2[/color] Do not use hate speech, racism, or other bigoted remarks. ★ +[color=#a4885c]1.2[/color] Using any OOC channel (OOC/LOOC/SOOC/Ghost chat) to insult or belittle another player, their ingame conduct, or OOC conduct in any way is forbidden. ★★ -[color=#a4885c]1.3[/color] Do not metagame. ★ +[color=#a4885c]1.3[/color] We have a Zero Tolerance policy for any intentional slurs, hate speech, bigotry, racism, speciesism, sexism, or ableism. Any terms that use real or implied mental or physical disabilities to mock or denigrate players or their characters are prohibited. Unintentional incidents will be handled with more care. Repeated incidents will be looked upon worse. ★★★ -[color=#a4885c]1.4[/color] Do not spam or advertise. ★ +[color=#a4885c]1.4[/color] Do not intentionally create unnecessary conflict or disruption without reasonable in-character justification. ★★ -[color=#a4885c]1.5[/color] Do not intentionally take actions that negatively impact or disrupt others' enjoyment of the game. ★ +[color=#a4885c]1.5[/color] Respect others OOC consent, dignity and boundaries. Any incident of being asked to stop in any OOC channel must be met with an immediate agreement and ceasing of the upsetting action. If you feel this rule is abused for gameplay advantages, please ahelp. ★★★ -[color=#a4885c]1.6[/color] Avoid discussing controversial topics such as self-harm or rape in public. ★★ - -[color=#a4885c]1.7[/color] Do not evade bans. ★★ - -[color=#a4885c]1.8[/color] Do not intentionally create unnecessary conflict or disruption without reasonable in-character justification. ★★ - -[color=#a4885c]1.9[/color] Do not cryo or disconnect to avoid in-character consequences. ★ - -[color=#a4885c]1.10[/color] Cheating and exploiting bugs are forbidden. ★★★ - -[color=#a4885c]1.11[/color] Respect others' OOC consent and preferences. ★★★ - -[color=#a4885c]1.11[/color] Suicide RP is prohibited. Many players may be dealing with personal struggles, and the game should remain a comfortable environment for everyone. Therefore, portraying suicide is not allowed, regardless of roleplay context. ★★ - -[color=#a4885c]1.12[/color] Roleplaying an underage character is strictly forbidden. So is talk of such activities. ★★★ +[color=#a4885c]1.6[/color] Do not spam or advertise other servers, products, services or otherwise for OOC content. You are permitted to advertise your IC shop, services, and so forth in character. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml index b3a485c61d6..999b133e6eb 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC10.xml @@ -1,17 +1,17 @@  [color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. ★ +[color=#a4885c]10.1[/color] Escalate conflicts reasonably. Use common sense when deciding how far a situation should go. A spilled drink might lead to an argument or fistfight, but should not escalate into a gunfight. ★★ -[color=#a4885c]10.2[/color] Both Security and Command are required to know Space Law, Standard Operating Procedures, and Alert Procedures ★ +[color=#a4885c]10.2[/color] When instigating, talk and posture first. Threaten with violence, brandish a weapon, or even fire a warning shot before engaging in combat. ★ -[color=#a4885c]10.3[/color] Don't abuse your position of power, this includes money withdrawal for “payment” upon one self without consulting the payment/hour or transferring your command ship deed to be used outside of your command roles. ★ +[color=#a4885c]10.2A[/color] If you are Command, Security, or an Antagonist, you are expected to have and attempt to use some form of non-lethal force before resorting to lethal force. If you are none of those roles and have access to non-lethal options, you should still attempt to use them. -[color=#a4885c]10.4[/color] You are expected to roleplay with others and respond to situations that need your role to function.★ +[color=#a4885c]10.2B[/color] If someone boards your ship, escalation rules are more lenient for the purpose of removing them from your ship. -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. ★ +[color=#a4885c]10.3[/color] Accept surrender if it is offered, regardless of how heated the situation is. ★ -[color=#a4885c]10.6[/color] Command characters must not have any disability, quirk, or traits that can impede the role function and communication. ★ +[color=#a4885c]10.3A[/color] Do not intentionally offer a false surrender. ★★ -[color=#a4885c]10.7[/color] Command personnel who signed up for the role but not actively do what the role demands to do (i.e only using the command role for looking at new ship/doing activities that are not within the command SoP) are heavily discouraged and connected to 10.1 rule break. ★ +[color=#a4885c]10.4[/color] Do not intentionally round-remove players. If you kill someone, you are not expected to revive them, but you must not take any actions that would prevent Medical from reviving them. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml index 982231fad82..57f7ee2a21d 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml @@ -1,17 +1,27 @@  -[color=#ffff00][head=3]Section 11: Escalation Guidelines[/head][/color] +[color=#ffff00][head=3]Section 11: Ship Saving and Design[/head][/color] -[color=#a4885c]11.1[/color] Escalate conflicts reasonably. Use common sense when deciding how far a situation should go. A spilled drink might lead to an argument or fistfight, but it should not normally escalate into a gunfight. ★ +[color=#a4885c]11.1[/color] Ships are to be no larger than 80×50 tiles. ★ -[color=#a4885c]11.2[/color] Use words and intimidation before lethal force. When starting or escalating a conflict, you should talk, posture, threaten violence, brandish a weapon, or fire a warning shot before attempting to kill someone. ★ +[color=#a4885c]11.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. ★★ -[color=#a4885c]11.2A[/color] Use non-lethal options when appropriate. Command, security, and antagonists such as pirates are expected to carry and attempt to use non-lethal options before resorting to lethal force. Other roles with access to non-lethals should also make a reasonable effort to use them first. Punching someone is considered non-lethal. ★ +[color=#a4885c]11.3[/color] Do not exploit the stash to duplicate items. ★★★ -[color=#a4885c]11.3[/color] Accept surrender. If someone offers a genuine surrender, you must accept it, regardless of how heated the situation has become. ★ +[color=#a4885c]11.4[/color] Ship backups are only to be used in the event of bugs, server issues, or other OOC problems. Loading backups may only be done with admin permission. Request this through an ahelp in-game or a ticket on the Discord. ★★ -[color=#a4885c]11.4[/color] Do not fake surrender. You may not intentionally offer a false surrender. ★ +[color=#a4885c]11.4A[/color] You may not load a ship backup if your ship was destroyed by hostile elements such as automated defenses or offenses (Drones, LPBs, etc.). -[color=#a4885c]11.4A[/color] Exceptions are made for those in factions. You may fake surrender but it will have heavy IC consequences placed on each faction’s SoP. ★ +[color=#a4885c]11.4B[/color] You may not load from a backup if your ship deed was lost. Recover that ship through IC means. -[color=#a4885c]11.5[/color] Do not intentionally round-remove players. If you kill someone, you are expected to revive them when it is safe to do so. You may restrain them first. If they attempt to escape and you are forced to kill them again, you are not required to revive them a second time, but you must preserve their body. ★ +[color=#a4885c]11.4C[/color] Any ship that was not saved due to player negligence is not entitled to compensation from the administration for loss of progress when loading a backup. An ahelp is still required. + +[color=#a4885c]11.5[/color] Thrusters, regardless of size, must be exposed to space at all times. No structures (except grilles) may block a thruster's exhaust to space. Do not build any entities on the same tile as thrusters. ★★ + +[color=#a4885c]11.5A[/color] Thrusters should not be placed at the exhaust of another thruster. ★ + +[color=#a4885c]11.5B[/color] For more information, refer to **Thruster Placement** in **Discord → Admin Questions → Thruster Placement**. + +[color=#a4885c]11.5C[/color] Cameras and lights may be placed on the same tile as thrusters. + +[color=#a4885c]11.6[/color] Machine setups that cause server lag are not allowed. Any player who owns such a setup on their ship will be given a single warning to remove it if it causes server lag. Failure to comply will result in the ship being deleted. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml index f788519aacc..595affe7555 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC12.xml @@ -1,33 +1,4 @@  + [color=#ffff00][head=3]Section 12: Ship saving Rules[/head][/color] - -[color=#a4885c]12.1[/color] Ships must not exceed a maximum size of 80×50 tiles. ★ - -[color=#a4885c]12.2[/color] Do not abuse the ship save system to avoid in-character consequences. ★★ - -[color=#a4885c]12.3[/color] Do not exploit the ship stash system to duplicate items. This prohibition especially applies to contraband. ★★★ - -[color=#a4885c]12.4[/color] Ship backups may only be loaded with prior administrator approval and are intended solely for server-related or other out-of-character (OOC) issues. You must submit an Ahelp before loading a backup. ★ - -[color=#a4885c]12.4A[/color] You may not restore a ship from backup if it was destroyed through normal in-character gameplay, including hostile entities such as automated defenses, drones, Long-Range Projectile Batteries (LPBs), or similar hazards. ★ - -[color=#a4885c]12.4B[/color] Whenever a ship backup is restored, you must notify the administration through an Ahelp or ticket so the restoration can be documented. - -[color=#a4885c]12.4C[/color] If you fail to save your ship within the 10-minute End-of-Round grace period due to your own negligence (for example, delaying the save or being AFK), you are not entitled to administrative compensation or restoration for any resulting loss of progress. - -[color=#a4885c]12.5[/color] Under no circumstances may you modify a ship save file without prior administrator approval, including modifications made to accommodate engine updates. ★★ - -[color=#a4885c]12.6[/color] Do not leave your ship unattended due to being AFK or otherwise absent for an extended period of time. ★ - -[color=#a4885c]12.6A[/color] An unattended ship may be declared abandoned by Command within the sector or local area and subsequently salvaged. Any loss resulting from leaving your ship unattended is the responsibility of the owner. - -[color=#a4885c]12.7[/color] All thrusters, regardless of size, must remain directly exposed to space. No walls may obstruct the exhaust path between a thruster and open space. Protective grills are permitted. ★★ - -[color=#a4885c]12.8A[/color] Multiple thrusters may not occupy the same location or share the same thruster engine block. ★ - -[color=#a4885c]12.8B[/color] For additional guidance regarding valid thruster layouts, refer to the Thruster Placement documentation in the Discord #admin-questions channel. - -[color=#a4885c]12.9[/color] Construction of complex or poorly optimized machinery that significantly impacts server performance is strongly discouraged. Players will normally receive up to two warnings to remove or modify the contraption. Failure to comply may result in the offending machinery being removed by administrators. ★ - -[color=#a4885c]12.9A[/color] Intentionally constructing or operating machinery for the purpose of degrading server performance or causing server lag constitutes abuse. Such behavior may result in immediate administrative action, including orders to cease, removal of the affected ship or machinery, administrative notes, or additional disciplinary action. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml index aa5d3a272e2..cd6da53cca8 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml @@ -1,3 +1,4 @@  + [color=#ffff00][head=3]Section 13: Faction Rules[/head][/color] diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml index 95641e9e3ea..c7422fb2bed 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml @@ -1,11 +1,23 @@ [color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] -[color=#a4885c]2.1[/color] If you are banned from a role, you may not play that role. This includes seeking or accepting promotions into restricted roles, as well as taking ghost roles that occupy those positions. ★★ +[color=#a4885c]2.1[/color] If banned from a role, you must not play that role. This includes seeking or accepting promotions into roles you are banned from, or taking ghost roles which hold the role. ★★ -[color=#a4885c]2.2[/color] Do not intentionally become a major problem, nuisance, or disruption to civilians while not being an antagonist (i.e. self-antagging). ★★ +[color=#a4885c]2.2[/color] It is forbidden to livestream rounds. ★★★ -[color=#a4885c]2.3[/color] Livestreaming rounds to others or sharing recorded gameplay outside of the Triad Sector without the consent of all parties involved is strictly prohibited. ★★ +[color=#a4885c]2.3[/color] Ghosting with the intent of checking which players may be ERPing is strictly forbidden. ★★ -[color=#a4885c]2.4[/color] Ghosting with the sole purpose of spying on the private activities of others is not permitted. ★★ +[color=#a4885c]2.4[/color] Do not utilize any known or unknown glitches, exploits or bugs to gain advantage. ★★★ + +[color=#a4885c]2.4A[/color] If you find something suspicious: report it on the Discord in an ahelp ticket. If it is something which requires immediate action, ahelp it. + +[color=#a4885c]2.5[/color] Ban evasion will result in a permanent community ban. ★★★ + +[color=#a4885c]2.6[/color] All characters must both be and act in a way resembling the age of adulthood. Any characters in violation of this are strictly forbidden, as is discussion of such activities. ★★★ + +[color=#a4885c]2.7[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. ★★ + +[color=#a4885c]2.7A[/color] EOR safe time starts with the end of round announcement, when there are 10 minutes left in the shift, and continues until we are in the lobby. This is to allow time for players to save their ships without disruption. + +[color=#a4885c]2.8[/color] Do not go AFK for extended periods with your ship spawned in. If you need to be away from the game for an extended period, save or sell your ship. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml index a041e455573..eb5fec9158f 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml @@ -1,16 +1,12 @@  [color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] -[color=#a4885c]3.1[/color] Use each chat channel for its intended purpose. ★ +[color=#a4885c]3.1[/color] Use chat channels for their intended purpose. Keep IC channels for roleplay, and OOC channels for player discussion. ★ -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of events that occurred while they were dead. ★ +[color=#a4885c]3.2[/color] Do not engage in meta-communications (via Discord, OOC, or other third-party software) if said communication is to gain an advantage in any form of PvP content. ★ -[color=#a4885c]3.3[/color] Do not use information obtained through meta-communication to perform PvP or other hostile actions against players. ★ +[color=#a4885c]3.2A[/color] Discussion about the current round is allowed on the Triad Discord server. -[color=#a4885c]3.3A[/color] Meta-communication is permitted only for discussing PvE content. All other information must be communicated through in-game channels. ★ - -[color=#a4885c]3.4[/color] Discussion about the current round is permitted on the Triad Discord server. However, acting on any information obtained through these discussions is considered metagaming, regardless of the nature of the information. ★ - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. Using in-character or out-of-character information to unfairly target, favor, or grant advantages to others is prohibited. ★ +[color=#a4885c]3.3[/color] Do not intentionally, repeatedly, and maliciously continue to target another player for reasons of an OOC dislike of them (metagrudging). IC grudges are fine and acceptable where all parties are consenting. Please speak with each other if you suspect the other party may be unhappy with an IC grudge. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml index 252cfddbd75..00a6e8b51df 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml @@ -1,13 +1,15 @@  [color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. ★ +[color=#a4885c]4.1[/color] Characters do not have any knowledge of what happened while they were dead, sleeping, or in critical condition. ★★ -[color=#a4885c]4.2[/color] Characters who are revived retain only vague memories of the circumstances surrounding their death. They may remember broad details, but not specific events or individuals involved. For example, if you were shot, you may remember being shot but not who shot you. If you accidentally set yourself on fire with a welder, you may remember being burned but not how it occurred. ★ +[color=#a4885c]4.2[/color] When a character is brought back to life, they cannot recall more than vague details of how they died. Examples: If you were shot, you only remember that you were shot, not who by. If you set yourself on fire, you remember burning and nothing more. ★ -[color=#a4885c]4.3[/color] Players who respawn instead of being resurrected lose all memories of the current shift and may not return to the site of their previous death. ★ +[color=#a4885c]4.3[/color] Do not respawn if your body or brain is still in the round and recoverable. Ahelp if you are unrevivable and would like to respawn. ★★ -[color=#a4885c]4.3A[/color] Players who receive information about their death or previous circumstances from others may reclaim or repair any lost property, but should not use such information to regain memories or act on past events. +[color=#a4885c]4.4[/color] Characters who come back via respawn, as opposed to being revived by another character, are to act as a freshly joined participant to the round. They are not to use their metaknowledge to try and recover any assets. This includes ships and equipment. ★★ -[color=#a4885c]4.3B[/color] Special exception for the ship-saving feature: players who encounter their former personal ship may recover it, [bold]provided ownership is transferred by a Command role or, if none are available, by an administrator[/bold]. +[color=#a4885c]4.4A[/color] Characters that respawn with a ship already loaded into the sector can work out IC, when they see a shipyard console or other method, and can take steps to recover their ship and deed. + +[color=#a4885c]4.5[/color] You may enter Cryosleep and respawn as your character in instances where you are in a cloned body or otherwise not in your default character's body. diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml index e0293972059..71b706f455d 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC5.xml @@ -1,7 +1,9 @@  [color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] -[color=#a4885c]5.1[/color] Don't make meta references. Try to be creative by picking a believable and fitting name within the game's lore. ★ +[color=#a4885c]5.1[/color] In-character names must not make obvious references or be a play on words, and must not be obscene. ★ -[color=#a4885c]5.2[/color] Ship names, particularly those of Command roles, must be appropriate and consistent with the sector's lore and the owner's character. Low roleplay names, direct meta references, and names unrelated to the setting are prohibited. Examples include naming the Overseer's Ravager "Goober", "Meow Meow Meow", or similarly inappropriate names. ★ +[color=#a4885c]5.2[/color] Do not name your character after another player's character. Do not attempt to impersonate another character without their OOC consent. ★★ + +[color=#a4885c]5.3[/color] Ship names, especially Command ships, must be of a reasonable standard for an MRP server. For example, do not name a ship "Goober" or "MeowMeowMeow". ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml index b52fb38fcd4..81b5aa5e66e 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC6.xml @@ -1,27 +1,21 @@  [color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] -[color=#a4885c]6.1[/color] Your character is separate from you, the player. Their actions, feelings, and knowledge should be based on their in-character experiences, not your own. ★ +[color=#a4885c]6.1[/color] Your character is 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 rather than your own as the player. ★★ -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Accurate roleplay is never an excuse for rule violations. If you are unsure, Ahelp for clarification. ★ +[color=#a4885c]6.2[/color] Playing a character accurately should never result in rulebreaks. Do not intentionally design your character in such a way that they break any other rule by existing. ★★ -[color=#a4885c]6.3[/color] By selecting a job, you are expected to fulfill the responsibilities of that role whenever reasonably required during the shift. ★ +[color=#a4885c]6.3[/color] If you choose a Command, Security, EMS, or faction role, you are required to participate in the round as that role when necessary. ★ -[color=#a4885c]6.3A[/color] Choosing a job implies a commitment to that role for the duration of the shift. Frequently switching between roles is considered a violation of Rule 6.3. ★ +[color=#a4885c]6.3A[/color] Choosing a job means you are actively playing that role during that shift. Do not change roles in quick succession. ★ -[color=#a4885c]6.3B[/color] Transferring to a higher position, such as a Command role, is permitted only with proper in-character justification. Administrative convenience or gameplay necessity alone are not valid reasons. For example, becoming an Overseer solely to perform a deed transfer is not permitted. ★ +[color=#a4885c]6.3B[/color] Switching your role to a higher position, such as a Command role, is allowed but only with an RP promotion and not for an OOC reason (e.g. needing to transfer a deed by switching from Mercenary to Overseer or DoC). ★ -[color=#a4885c]6.3C[/color] Once a character assumes a Command role, they are expected to remain in that position for the rest of the shift, even if they cryo. You may play other characters in different roles, but the same character may not move from a Command role to another Command position or to a lower role. ★ +[color=#a4885c]6.3C[/color] Once you take a Command role, you must commit to that role while you are in that shift as that character. Do not rejoin on the same character as a non-Command role in the same round you played Command. ★ -[color=#a4885c]6.4[/color] Do not intentionally interrupt or disregard roleplay in order to gain an unfair advantage while another player is actively roleplaying or typing. ★ +[color=#a4885c]6.4[/color] When players are engaging in roleplay such as hostage-taking, robberies, or otherwise, do not transition to mechanical combat while they are still roleplaying or typing. ★ -[color=#a4885c]6.4A[/color] Using LOOC to argue about in-game situations or otherwise gain an advantage in roleplay is considered low-roleplay behavior and breaks immersion. For example, arguing in LOOC after being caught breaking into Security. ★ +[color=#a4885c]6.4A[/color] Leeway is given if the scene is near its conclusion, but all players are expected to engage with it in good faith, even if this puts them at a disadvantage. -[color=#a4885c]6.4B[/color] Potential rule violations or disputes regarding the legality of actions should not be argued through LOOC. Use Ahelp to seek clarification. If no administrator is available, postpone, cancel, or de-escalate the situation until a ruling can be made. ★ - -[color=#a4885c]6.5[/color] Respect the consent, dignity, and boundaries of others. If someone asks you through LOOC to stop bothering them, you are expected to do so. If you believe this rule is being abused, Ahelp immediately. ★★ - -[color=#a4885c]6.6[/color] Do not dismantle critical station infrastructure, such as atmospheric systems, power cables, or other essential components, for non-essential activities without the knowledge and approval of Command. ★★ - -[color=#a4885c]6.7[/color] Avoid direct references to internet culture, memes, or netspeak in-character. Excessive use of phrases such as "tung tung tung sahur", "skibidi toilet", or similar expressions is considered low roleplay and immersion-breaking. ★★★ +[color=#a4885c]6.5[/color] Do not directly refer to internet culture or use netspeak while roleplaying, for example "lol" or "skibidi toilet". ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml index 8de17cba77f..b7077ae2411 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC7.xml @@ -1,15 +1,15 @@ - + [color=#ffff00][head=3]Section 7: Point of Interest and Safe Zone Rules[/head][/color] -[color=#a4885c]7.1[/color] Point of Interest (PoI) structures must not be disabled, destroyed, or rendered inoperable unless authorized by higher command or required for a specific approved purpose. ★ +[color=#a4885c]7.1[/color] Under no circumstances should a Point of Interest be intentionally disabled or destroyed without a specific purpose or an order from a member of Command or an Admin. ★ -[color=#a4885c]7.2[/color] Point of Interest locations must remain dedicated to their intended function unless higher command explicitly authorizes an alternative use. (Example: Establishing a temporary medical treatment area in Bahama Mama's during an emergency is permitted, but converting Edison Powerplant into a data center by using its infrastructure without approval is prohibited.) ★ +[color=#a4885c]7.2[/color] Venmar Station and Medical Dispatch are categorized as Safe Zones. While in a Safe Zone, you must not use any explosives or destructive devices, or fire your ship guns. -[color=#a4885c]7.3[/color] Central Command (CC) and Medical Department (MD) are designated as Safe Zones. +[color=#a4885c]7.2A[/color] A 512m area around the Safe Zone stations is also considered a Safe Zone. -[color=#a4885c]7.3A[/color] Acts of uncivilized conduct within a Safe Zone—including murder, assault, theft, sabotage, or malicious damage to another player's ship or property—will be handled in-character by Security and may also result in out-of-character administrative action for serious violations. ★★ +[color=#a4885c]7.2B[/color] Do not flee to Safe Zones purely to avoid consequences for antagonistic actions. ★ -[color=#a4885c]7.3B[/color] A radius of 512 meters surrounding a designated Safe Zone structure is considered part of the Safe Zone. +[color=#a4885c]7.3[/color] Antagonistic actions such as murders, attacks, and thefts are to be handled IC. Major damage such as bombings or station destruction will be handled by an Admin. ★★ -[color=#a4885c]7.4[/color] Point of Interest locations that are not designated Safe Zones, such as Edison Powerplant, Drillsite, and similar facilities, must not be intentionally damaged except during authorized circumstances such as faction conflicts, administrative events, or other approved scenarios. ★ +[color=#a4885c]7.4[/color] Do not steal anything from a Point of Interest that is critical to its function. ★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml index 84b1b5b408d..7883c1413d2 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC8.xml @@ -1,7 +1,37 @@  -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] +[color=#ffff00][head=3]Section 8: Erotic/Extreme Roleplay Rules[/head][/color] -[color=#a4885c]8.1[/color] End-of-Round Griefing (EORG) is strictly prohibited under all circumstances. This includes, but is not limited to, engaging in combat, using explosives or hazardous chemicals, destroying property, or committing any other disruptive or malicious actions. ★ +[color=#FFFACD]We are an 18+ server with an explicit welcoming to mature themes and the full range of performed gender and sexuality: Extreme content is not necessarily just sexual; but can include dismemberment outside of medical/surgical contexts or other extreme violence. What is performed in the complete privacy of Subtle Emotes will not be audited unless directly relevant to a ticket.[/color] -[color=#a4885c]8.2[/color] The End-of-Round (EOR) period begins 10 minutes after the round-end evacuation announcement (shuttle evacuation announcement). This grace period exists to allow players sufficient time to secure or recover their ships without interference. +[color=#a4885c]8.1[/color] ERP does not take priority over Command, Security, EMS, or faction roles. If you are requested or needed, you must respond and return to your duties immediately. ★ + +[color=#a4885c]8.2[/color] Do not use ERP, or the offer of ERP, as a means of forwarding any antagonistic goals without OOC consent from those involved. ★ + +[color=#a4885c]8.3[/color] Do not kinkshame. ★ + +[color=#a4885c]8.4[/color] You must use Subtle, Whisper, and Subtle OOC for any and all erotic or extreme roleplay material. ★★★ + +[color=#a4885c]8.4A[/color] Do not engage in, or discuss, extreme or sexual topics in any public setting. This includes privately informing people of previous extreme or erotic scenes without consulting all parties involved beforehand. + +[color=#a4885c]8.4B[/color] Extreme or erotic scenes involving CNC or similar themes should never be reported as crimes. + +[color=#a4885c]8.4C[/color] Do not involve anyone in suicide RP outside of consenting parties. This includes medical implants announcing the scene to non-consenting parties. + +[color=#a4885c]8.5[/color] Radio, Handicomms, and Local are visible to ghosted players. Without the ability to "walk away" from content they find objectionable or do not wish to engage with, keep anything above mild to moderate innuendo to Whisper or Subtle. ★ + +[color=#a4885c]8.5A[/color] Sexual implications or risqué banter are acceptable. + +[color=#a4885c]8.5B[/color] Visceral descriptions or promises of BDSM-coded degradation are not permitted. + +[color=#a4885c]8.5C[/color] Turn off devices that can transmit voices (shuttle consoles, Handicomms, etc.) to avoid disturbing other players and ghosts. + +[color=#a4885c]8.6[/color] Engaging in ERP with a non-sentient creature is prohibited. This includes creatures that resemble any real-world animal, regardless of whether they have been made sentient using Cognizine. ★★★ + +[color=#a4885c]8.6A[/color] This includes spiders, carp/sharkminnows, station pets or emotional support animals, mice, mothroaches, bats, monkeys, and similar creatures. + +[color=#a4885c]8.6B[/color] This does not include silicons, xenos, full-sized dragons, slimes, flesh monsters, kobolds, and similar sentient species. + +[color=#a4885c]8.7[/color] When roleplaying another person's character, OOC consent from the original owner of the character is required before engaging in ERP. ★★ + +[color=#a4885c]8.8[/color] You are not permitted to ERP in public. You must be in a location with a reasonable expectation of privacy, such as your ship or behind bolted or welded doors. ★★ diff --git a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml index 391bf36b726..10265c9fccc 100644 --- a/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml +++ b/Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC9.xml @@ -1,29 +1,17 @@ -[color=#ffff00][head=3]Section 9: Erotic Roleplay (ERP) Rules[/head][/color] +[color=#ffff00][head=3]Section 9: Command, Security, and TDF Guidelines[/head][/color] -[color=#a4885c]9.1[/color] Erotic Roleplay (ERP) does not take precedence over your assigned duties. If your role requires your attention or you are requested to perform your job, you must respond or return to your duties as soon as reasonably possible. ★ +[color=#a4885c]9.1[/color] Command, Security, and TDF roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. ★ -[color=#a4885c]9.2[/color] ERP must not be used or offered as bait to lure, ambush, or kill another player. ★ +[color=#a4885c]9.2[/color] Command, Security, and TDF members are required to know Sector Law and Standard Operating Procedures. ★ -[color=#a4885c]9.3[/color] Do not harass, ridicule, or shame other players for their consensual roleplay preferences. ★ +[color=#a4885c]9.3[/color] Do not abuse your position of power. This includes taking unearned payments or utilizing your command ship when not playing a Command role. ★★ -[color=#a4885c]9.4[/color] All ERP-related dialogue or roleplay must be conducted using the subtle (-) or whisper commands. ★ +[color=#a4885c]9.3A[/color] Command, Security, and TDF members are not permitted to accept bribes or sexual favors in exchange for special treatment. -[color=#a4885c]9.4A[/color] When engaging in ERP, ensure that any device capable of transmitting your voice (such as shuttle consoles, HandiComm, or similar communication systems) is disabled to avoid disturbing other players. ★ +[color=#a4885c]9.4[/color] You are expected to roleplay with others and respond to situations that require your role to function. ★ -[color=#a4885c]9.5[/color] Do not spam or excessively use radio channels for NSFW topics. This does not prohibit discussing such topics altogether; however, repeated hornyposting, shitposting, depression posting, or other disruptive behavior is prohibited. ★ +[color=#a4885c]9.5[/color] If you are in a Command role, inform your department and Command before entering cryosleep or disconnecting. ★ -[color=#a4885c]9.6[/color] Do not engage in or publicly discuss extreme sexual fetishes. Public spaces include radio channels, spoken dialogue in public areas, overt public actions, or any activity visible through cameras. ★ - -[color=#a4885c]9.7[/color] ERP involving non-sentient creatures is prohibited. This includes creatures that resemble beasts, even if they may later become sentient. ★★ - -[color=#a4885c]9.8[/color] When roleplaying another player's character, you must obtain out-of-character (OOC) consent from that character's owner before engaging in ERP involving them. ★★ - -[color=#a4885c]9.9[/color] Be mindful of both in-character (IC) and out-of-character (OOC) consent. If your OOC consent is violated or disregarded, immediately submit an Ahelp or open an administrative ticket. ★★★ - -[color=#a4885c]9.10[/color] Extreme roleplay themes, including but not limited to snuff, abuse, non-consensual scenarios (noncon), and similar content, are only permitted when all participating parties have provided prior OOC consent. If you are uncertain whether a scenario is permitted, contact an administrator through an Ahelp. Keep such roleplay private. ★★★ - -[color=#a4885c]9.11[/color] ERP must not take place in public areas. Ensure you are in a private, secure location, such as a personal ship, a lockable room, dormitories, or another secluded area. - -[color=#a4885c]9.11A[/color] If another player discovers your ERP and requests that you stop or relocate, you must either move to a different private location or cease the activity. ★ +[color=#a4885c]9.6[/color] Characters in Command roles must be the sort of character that could reasonably have attained their position and can reasonably perform their duties. If you are playing a character with disabilities in a position that other players rely on, it is your responsibility to ensure that you and your character can work around those barriers. ★ From 82e5fd85bfcd258a3dc066c089d34b54169fc40e Mon Sep 17 00:00:00 2001 From: DDrakov <157034866+DDrakov@users.noreply.github.com> Date: Wed, 1 Jul 2026 08:39:45 +0700 Subject: [PATCH 5/5] Update Resources/Prototypes/_Triad/Guidebook/rules.yml --- Resources/Prototypes/_Triad/Guidebook/rules.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Resources/Prototypes/_Triad/Guidebook/rules.yml b/Resources/Prototypes/_Triad/Guidebook/rules.yml index 8b078940a52..48facbfab41 100644 --- a/Resources/Prototypes/_Triad/Guidebook/rules.yml +++ b/Resources/Prototypes/_Triad/Guidebook/rules.yml @@ -16,7 +16,7 @@ - TriadRuleC9 - TriadRuleC10 - TriadRuleC11 - - TriadRuleC12 +# - TriadRuleC12 # - TriadRuleC13 - type: guideEntry