Server 65 – Rules of Engagement (RoE)

Modified on 4-7-2022

Index

Section A: Governance & Authority of the ROE

Section B: Legal & Illegal Hits

Appendices
Appendix I: Maintenance & Updates
Appending II: Voting
Appending III: Violations & Reporting
Appending IV: Definitions
SECTION A: GOVERNANCE & AUTHORITY OF THE ROE

1. Except where noted, these Rules apply to Server 65, and not to the Discord. The Admiralty of the Discord
is responsible for setting and maintaining its own rules structure.
2. These Rules were debated, considered, and approved by 2/3 vote of the Admiralty of the Discord on date 4-7-22
The process for amending these Rules is outlined in the Maintenance and Updates section.
3. Admirals and Alliances may extend these Rules, but such extensions will be considered courtesy, and subject
to diplomatic use and suspension. See Appendix I
4. Attached Appendices (definitions, etc.) shall be considered as part and parcel carrying the same force as a Rule
if a passage in an Appendix covers material not otherwise cited within a Rule.
5. In the event of a conflict between a Rule and an Appendix passage presenting as a Rule under Rule 4, the
Rule shall prevail.
6. Ship Classifications are determined by in game symbols and are absolute. Commanders are forbidden
from setting their own Classifications in all circumstances.
7. Any Commander or Alliance may be deemed Renegade if voted upon by the Admiralty with 2/3 majority
vote. Behaviors that may lead to Renegade include but is not limited to:
• Blatant disregard for ROE or multiple violations of ROE that are not resolved amicably
• Waging excessive wars to bypass ROE

SECTION B: LEGAL & ILLEGAL HITS

1. Survey ships are only protected if they meet these criteria while mining: - Remaining UPC (Under Protected
Cargo) AND not occupying a Zero Node. See rule 4 about z-node hits in Origin Space. (2) Screen Shots are
required before hitting a Z-node, (1) showing the Commander's name and (1) showing the node is zeroed.

2. No Commander shall attack any vessel of any kind participating in an Armada. Participating means any ship
within their alliance's Armada circle. Ships outside the circle (even if they are moving towards the circle) have no
protection.

3. Systems requiring a Token or other Expendable Item to enter shall be PvE areas only.

4. Outside of scheduled capture/takeover events, Origin space offers UPC protection for miners while on-node
(including zero-node) but offers no protections for armadas started in another alliance's territory. Armadas
started within an alliance's own territory are still protected.

5. During any Scopely PVP Event (including territory captures/takeovers and events where points are earned for
attacking other players), any apparent ROE violations are waived/absolved by a statement (and if requested, a
screenshot showing) that a specific attack was in accordance with the scoring rules of an active PVP event.

6. When war is declared, it negates all ROE provisions between the warring parties. War is to be declared in game
and on Discord in advance of any hostilities. Any violations of ROE that happened before declaration of war are
not excused by a later declaration of war.
 APPENDICIES

APPENDIX I: MAINTENANCE AND UPDATES:

These Rules are not unchanging. As circumstances and play conditions change, through updates and/or general
maturation of the Server, so must these Rules.

i. If a Commander wishes to propose a change to a Rule, they must do so through their Alliance leadership, who
then may, at their discretion, raise the request to the Admiralty.
ii. Only one Rule may be amended, added, or removed outright per request. A Commander may open multiple
requests for multiple proposed Rules changes, but each will be considered separately (in the order filed), and
none shall be allowed to be contingent on any other request being successful or unsuccessful.
iii. A change may be subject to an informal ‘show of support’ canvas in a public and transparent fashion by the Arbiter
of the Rules, requiring 2/3 to succeed. Moving to a formal adoption vote may be made contingent on the success
of this informal poll.
iv. The will of the server community will always prevail. No party may hold a veto over any proposed rule change once
it has been submitted for consideration by an Admiral. Accordingly, 2, 3, and 4 in this section are specifically exempt
from any proposed changes and cannot be altered.

APPENDIX II: VOTING:

The following provisions apply to voting as is referred to within this document. Should a vote be required:

i. Polls shall be co-originated by and at the direction of the Arbiter of the Rules.
ii. The rolls shall be determined at the time a motion for a poll is made and frozen until the end of the vote. Only
Qualified Alliances who are still present in-game at a vote's close shall be counted.
iii. An Alliance is Qualified, or allowed to vote if they have an active member in Council at the time the rolls are frozen.
A member must belong to Council for one (1) week in order to represent a Qualified Alliance.
iv. All Qualified Alliances are apportioned one ballot per vote.
v. At the time of any poll, voting will occur on the Server Discord and be restricted to Qualified Alliances. This polling
will happen in coordination with server moderators.
vi. The qualifying threshold on any given vote shall be 2/3 of votes cast yay/nay. Votes of abstention are not
considered of the sum total for this purpose. Votes will remain open until:
a) All voting members at the time the rolls are frozen have cast their vote.
or
b) A maximum of one week has passed.

APPENDIX III: VIOLATIONS & REPORTING

Violations of these Rules will be resolved in the following order:

a) Contact your Diplomacy Officer, or your Admiral, as dictated by the customs of the Alliance to which you
belong. Your leadership will then contact the corresponding leadership at the Accused’s Alliance.
b) Post screenshots to the Discord for adjudication by the server Admiralty. In the event the Admiralty cannot
agree, the Arbiter of the Rules may be asked to mediate. Any rulings made by the Arbiter is final and both
alliances shall agree to the terms set forth.
c) For any disputes involving the Arbiter of the Rules or their Alliance, the Arbiter of the Rules will recuse
themselves and the alternate Arbiter shall resolve the dispute.
APPENDIX IV: DEFINITIONS
AC — Short for Alliance Chat.

Admiralty – The group leadership of the S65 Discord as composed of leadership of the participating Alliances. A
Commander does not need to be an Admiral to be considered part of the Admiralty if they hold a lower rank and are
their Alliance’s designated representative to the body. The Admiralty is currently defined as the Council on s65.

Advance Notice – A courtesy practice of messaging an intended attack target with the reason for the attack and why
the hit is legal under the Rules before initiating said attack.

Arbiter of the Rules – An elected position within the Discord who’s office holder maintains final and binding say over
disputes arising under the Rules in the event the Admiralty cannot reach an agreement over any given RoE matter. The
Arbiter of the Rules is also responsible for facilitating votes for any matter requiring such.

Commander – You, as represented within the universe of Star Trek Fleet Command on your server.

Coords — Short for Coordinates. Used with in-game mapping system to specify the location of a station, a ship, an ally,
an enemy target, or any other point of interest.

Discord — Social Media app with extended game discussion. Many Alliances require Discord for resolving conflicts
and diplomatic incidents. See the Official STFC Discord (as maintained by Scopely) here: https://discord.gg/stfc. For
the S65 Discord (as maintained by the Commanders of S65), please see here: https://discord.gg/8SSCUZvg9X.

Fair Play — The cornerstone principle of ROE.

Floater — A ship of any class not on any Node or Station that is not moving for an extended period such that it
appears abandoned by its Commander. Many Alliances regard Floaters as space junk and are only too happy to clear
the way.

GC — Short for Galaxy Chat.

Illegal Ship — Use of a non-survey starship on a mining node.

KOS — Kill On Sight. This dubious designation declares its recipient as a public enemy. Once you've been marked KOS
by an Alliance, all members are authorized to attack you the moment you're in target range, regardless of RoE, with or
without provocation.

Node — A mining location (different from a Capture Node) where a Survey class ship is permitted to park for an
extended period expressly to extract Resources or Materials.

OPC — Over Protected Cargo. See Protected Cargo.

Peace Shield — Protects your home station against enemy attack and raiding of Resources. While active, you, in turn,
cannot attack other players without first deactivating your Peace Shield.

PM or DM — Short for Private Message or Direct Message.

Protected Cargo – The amount of resources a ship can hold in the carbo bay that can not be taken by another player.

PvE — Player vs. Environment. Describes combat of one player versus non-player characters built into the game such as
mission hostiles. Armadas are generally regarded as a form of group PvE.

PvP — Player vs. Player. Describes combat of one player versus another player.
Renegade Alliance – An Alliance that has chosen not to acknowledge or follow the RoE as set forth in this document, or has
been deemed in non-compliance by the Admiralty of the Discord

Renegade Commander – A Commander (as a Non-Affiliated Commander, or a Commander within an Alliance) who has chosen
to not acknowledge or follow the RoE as set forth in this document, or has been deemed in non-compliance by the Admiralty of
the Discord

ROE — Rules of Engagement.

RSS — Slang for Resources, such as Parsteel, Tritanium, Dilithium, etc. Used primarily as an abbreviation in text chat,
particularly in reference to raiding.

Tag — The 4-letter or shorter abbreviated name that identifies members of an Alliance.

Takeover — Every Zone in Origin Space has an automatically recurring weekly event called a Takeover in which
possession of that Zone is up for grabs. Each Alliance that joins a Takeover scores points by having ships present in the
systems comprising the Zone in play. Point values quadruple for ships on Capture Nodes.

Territory Capture (TC) — The star systems within Origin Sector are grouped into territorial Zones. Alliances fight to
control each Zone during a Takeover to gain Alliance-wide access to each Zone’s own features and player
enhancements.

UPC — Under Protected Cargo. See Protected Cargo.

UPCL — Under Protected Cargo Limit. Same as UPC. See Protected Cargo.

UPL — Under Protected Limit. Same as UPC. See Protected Cargo.

Warships — All ships that comprise the Combat Triangle – Battleship, Explorer, and Interceptor – regardless of faction –
are ALL classified as Warships.

Zero-Node (Z-node) — When all available resources have been mined from a Node, and it shows 0 available, then the
ship occupying it is designated as Zero Node.