Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions Resources/Locale/en-US/_Triad/guidebook/guides.ftl
Original file line number Diff line number Diff line change
@@ -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 = Powergaming Section
guide-entry-section8 = End-Of-Round Section
guide-entry-section9 = ERP 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-section7 = Point Of Interest and Safe Zone 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
25 changes: 13 additions & 12 deletions Resources/Prototypes/_Triad/Guidebook/rules.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@
- TriadRuleC9
- TriadRuleC10
- TriadRuleC11
- TriadRuleC12
- TriadRuleC13
# - TriadRuleC12
# - TriadRuleC13

- type: guideEntry
id: TriadRuleC1
Expand Down Expand Up @@ -85,14 +85,15 @@
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

- 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
251 changes: 33 additions & 218 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC0.xml

Large diffs are not rendered by default.

24 changes: 7 additions & 17 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC1.xml
Original file line number Diff line number Diff line change
@@ -1,25 +1,15 @@
<Document>
[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. *1
[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] Don't use hate speech, racism, or bigoted comments. *1
[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]Don't metagame.*1
[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] Don't spam or advertise. *1
[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 would negatively impact or disrupt others enjoyment of the game. *1
[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 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=#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. ★★
</Document>
Original file line number Diff line number Diff line change
@@ -1,13 +1,17 @@
<Document>
[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] 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, Alert Procedure, and Company Policy. *1
[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. *1
[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, this includes antagonists. *1
[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. *1
[color=#a4885c]10.3[/color] Accept surrender if it is offered, regardless of how heated the situation is. ★

[color=#a4885c]10.3A[/color] Do not intentionally offer a false surrender. ★★

[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. ★★
</Document>
26 changes: 21 additions & 5 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC11.xml
Original file line number Diff line number Diff line change
@@ -1,11 +1,27 @@
<Document>
[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color]
[color=#ffff00][head=3]Section 11: Ship Saving and Design[/head][/color]

[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. *1
[color=#a4885c]11.1[/color] Ships are to be no larger than 80×50 tiles. ★

[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. *1
[color=#a4885c]11.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. ★★

[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. *1
[color=#a4885c]11.3[/color] Do not exploit the stash to duplicate items. ★★★

[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. *1
[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.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.4B[/color] You may not load from a backup if your ship deed was lost. Recover that ship through IC means.

[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. ★★
</Document>
Original file line number Diff line number Diff line change
@@ -1,11 +1,4 @@
<Document>
[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
<!-- Unused as of now -->
[color=#ffff00][head=3]Section 12: Ship saving Rules[/head][/color]
</Document>
32 changes: 2 additions & 30 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC13.xml
Original file line number Diff line number Diff line change
@@ -1,32 +1,4 @@
<Document>
[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

<!-- Unused as of now -->
[color=#ffff00][head=3]Section 13: Faction Rules[/head][/color]
</Document>
20 changes: 16 additions & 4 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC2.xml
Original file line number Diff line number Diff line change
@@ -1,11 +1,23 @@
<Document>
[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 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 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] It is forbidden to livestream rounds. ★★★

[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] Ghosting with the intent of checking which players may be ERPing is strictly forbidden. ★★

[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] 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. ★
</Document>
13 changes: 4 additions & 9 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml
Original file line number Diff line number Diff line change
@@ -1,17 +1,12 @@
<Document>
[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 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 what happened while they were dead. *1
[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 any information gained by meta-communication. *1
[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 so long as its ONLY about PvE content any other content should NOT be said unless its though In-game chats
[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. ★★

[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
</Document>
12 changes: 10 additions & 2 deletions Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC4.xml
Original file line number Diff line number Diff line change
@@ -1,7 +1,15 @@
<Document>
[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] Characters do not have any knowledge of what happened while they were dead, sleeping, or in critical condition. ★★

[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] 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] 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.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.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.
</Document>
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
<Document>
[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] In-character names must not make obvious references or be a play on words, and must not be obscene. ★

Try to be creative by picking a believable and fitting name and/or surname.
[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. ★★

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.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". ★
</Document>
Loading
Loading