Skip to content

Rules 1.3.2 - #465

Draft
Eillyrea wants to merge 4 commits into
Triad-Sector:mainfrom
Eillyrea:Rules-1.3.2
Draft

Rules 1.3.2#465
Eillyrea wants to merge 4 commits into
Triad-Sector:mainfrom
Eillyrea:Rules-1.3.2

Conversation

@Eillyrea

@Eillyrea Eillyrea commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

About the PR

Update Rule 1.7D
Do not hide contraband or other antagonistic activity behind a Privacy holobarrier. Keep all antagonistic activity in a location publicly accessible.

Added rule 3.4
Do not powergame encounters by utilising metaknowledge of where hostile entities spawn and how to optimally overcome them, or to circumvent gameplay loops. E.g. building walls to block turrets behind blast doors or TDF checking every POI for dead drop notes before alerted to them.

Update Rule 6.3
If you choose a Command, or Faction role, you are required to participate in the round as that role when your role is required.

Update Rule 7.5
If you've participated in a raid upon LPB or Sevastopol, please give a minimum of 3 shifts before you rush for the content again. This is to give other players a chance to experience the content. After 6 hours into the shift, this embargo is lifted.

(It's meant to be 2/3rds of the shift but wasn't updated with the shift end timer)

Update: Category 9
Renamed to "Command, Faction, and Self-Antag Guidelines"

Added rule 9.1A
Factions as they exist are the TDF and TFA. Including within the TFA: Venmar staff, Edison staff and Medical Dispatch staff.

Added Rule 9.1B
Self-antagging is allowed, to grant players freedom in the characters they play. This does not mean that PvP is fully enabled. Murder and killing should be a last resort, antags exist to generate stories.

Deleted Rule 9.4
It is the same rule as 6.3, Rules 9.5-9.7's numbers adjusted to compensate for the missing rule

Deleted Rule 11.4C

Added Rule 10.5, 10.5A, 10.5B, 10.5C
With Ship to Ship combat, follow all Escalation Guidelines as well as these. Once a surrender has been made, all hostilities must cease. ★★

  • When your opponents ship has stopped moving or firing it's guns at you, cease fire and request that they surrender.

  • Do not fire upon a ship that has lost combat capabilities, but is still operational. For example it's pilot has been killed.

  • When demanded to surrender, you do not need to be accept, but you must respond if capable. No response is considered a surrender.

Why / Balance

Rules

Media

Requirements

  • I have read relevant guidelines/documentation to this PR found on our devwiki.
  • I have added media to this PR or it does not require an ingame showcase.
  • I can confirm this PR contains either no AI-generated content, or AI-generated content that meets our guidelines.

How to test

Breaking changes

Changelog

🆑

  • add: Rules: 3.4, 9.1A, 9.1B, 10.5, 10.5A, 10.5B, 10.5C
  • remove: Rules: 9.4, 11.4C
  • tweak: Rules: 1.7D, 7.5. 6.3

@github-actions github-actions Bot added No C# Doesn't contain any C# code FTL Changes to localization files Docs Improvements or additions to documentation/guidebooks size/S S: Untriaged labels Aug 4, 2026

@DDrakov DDrakov left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think with this, should leave as is until the new rework of AI and the rework of dungeon is in progress or done.

Comment thread Resources/ServerInfo/_Triad/Guidebook/Rules/CoreRules/RuleC3.xml
@Eillyrea

Eillyrea commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator Author

I think with this, should leave as is until the new rework of AI and the rework of dungeon is in progress or done.

Rules are not static, there is no "Leave as is", they are updated as and when is required and maintaining the rules is part of administrative work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Docs Improvements or additions to documentation/guidebooks FTL Changes to localization files No C# Doesn't contain any C# code S: Untriaged size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants