Post by Admin on Oct 8, 2022 20:46:43 GMT
So this is what Hydrazine of [BORG] posted at the Discord he's hosting.
I'd like to keep this particularthread limited ONLY to discussion of the rules themselves, and not as to whether we will obey them fully or not. That will be a separate thread and I ask you to try and limit that discussion to that thread.
OK....here goes....
đź—’ ROE Cliff Notes Version
Understanding that the full version of this document and all the rules herein is very complex, a simpler
version is presented.
For players below level 15 the simpler rules apply and leniency should be given
where possible to violations.
The goal of the ROE is to make the game more fun to play, not to overwhelm the players with Do’s and Don’t’s.
â—Ź No killing in Armadas, Token Space, Deep Space
â—Ź Miners OPC and 0 node are legit kill
â—Ź Shield or Share
Star Trek Fleet Command (STFC) is a PVP game so killing and getting killed is to be expected;
therefore, as the members of server Epsilon 91 we create these Rules of Engagement (ROE) to promote
“Fair Play” which is essential to keeping this server entertaining, yet civilized. Keep in mind that you can
get PVP kills and others can also kill you – karma can be quite instant in this game. So, even if your
action is lawful and in accordance with ROE, it can still be considered a hostile act and incur retribution
in lawful manners.
đźš©Implementation of Server ROE
This ROE is a generic, server-level set of rules, and alliances are fully encouraged to enforce their “own” ROE.
However, any alliance-based modification of ROE as described henceforth, shall only be “additive” in nature.
This means that alliances can only make these rules more strict.
If the alliance-specific ROE is less restrictive than the server ROE, then they will be found in breach of server ROE.
đźš©Enforcement of Server ROE
The methods of ROE enforcement is on a per-alliance basis.
Keep in mind that diplomacy is always prefered than going into war.
Many ROE violations are simply due to mis-understanding of the ROE,
human error, or even game bugs, and can be resolved by talking it out in a civilized manner.
It is very important that participating alliances only act when there is indisputable “proof” of roe violation;
for example, a screenshot of the battle report.
Acting on “he said/she said” evidence is not going to help resolve the issue or clarify the timeline.
Unless stated within the rule, the party and its alliance reporting the violation has the burden of the proof.
An alliance may choose not to follow this ROE and cause grievance against the entire server population.
As such,with proof of non-participation, such alliance may be declared as Enemy of every participating alliance of this server ROE (edited)
– Participation of Server ROE
Participation of this server ROE is voluntary for each alliance. Participation does not infer or imply, an “Ally” or “Friendly” status between any of the participating alliances
[9:50 AM]
⚠️ ROE # 1. No Kill List
The following are not to be killed except during active War/KOS
â—Ź Any ships participating in Armadas
â—‹ Including up to one (1) minute for them to exit the area afterwards
● Any Ship in a system which has a cost associated with entering, commonly known as “Token
Systems”. Examples of such systems:
â—‹ Borg systems
â—‹ Rogue systems
â—‹ and any other current, and/or future token systems .
⚠️ ROE # 2. Mining Etiquette
Everyone should enjoy safe mining in order to grow, but should not clog up the mining nodes.
This inconveniences other players and directly affects their play.
NOTE: Due to the North Star’s combat ability, and its use as such, it is considered a survey ship only when actively mining on such a node.
This ROE may be ignored if the opposing alliance is marked as an “Enemy” for legitimate
reasons. See #6.
2a. Acceptable kills during mining:
â—Ź The ship is a survey ship, and is over the protected cargo limit, also known
as OPC
â—Ź The ship is a warship
2b. Special Notes Regarding “0 Node + UPC Kills”
It is an allowable attack per ROE if the miner being attacked is on a depleted node showing zero (0) resource or material left and an in game private message has been sent
(“0 node”, or “zero” is
sufficient) AND two (2) minutes has elapsed since the warning has been sent, so that screen shots of the battle report and message may be used for provenance in resolving any conflict regarding a UPC
attack on a miner. 2c. Any warship / mining vessel left derelict (floaters) or clogging mission planets can be targeted. (edited)
⚠️ ROE # 3. Warships are Fair Game
Warships are considered a fair target at all times.
Except when Discovery is mining Mycelium.
⚠️ ROE # 4. Shield or Share
An attack against a station is always considered lawful.
An attack towards any ship, participating in a defence or attack against a station, is considered lawful.
It is your responsibility, and yours alone to raise a shield to prevent attack. This includes stations inside
of claimed territories.
⚠️ ROE # 5. Territory Takeover is Fair Game
Anything is allowed inside the territory during the territory allocated takeover time.
It is designed by Scopely as a battleground for alliance to fight each other and therefore will be designated as such.
Outside of takeover times standard ROE applies to any players inside territories.
⚠️ ROE #6. Alliance KOS/Wars
Under some circumstances, such as repeated ROE violations, an Alliance may wish to declare another Alliance as “Kill on Sight” (KOS).
Generally this means that none of the ships of the target Alliance are protected by ROE.
However, the aggressor has a duty to inform their target of the new KOS status.
To avoid wars being called too frequently and unnecessarily any declaration of war must be in effect for at least 48 hours (2 days).
This reduces the appeal of declaring a war in order to dodge ROE for a short period of time before attempting to hide behind a truce.
⚠️ ROE #7. Retaliation
Inevitably someone will break or be ignorant of the standard ROE terms.
If ROE is violated, then the victim may respond in kind to the perpetrator within a twenty-four (24) hour period.
The victim should not turn around and use an ROE violation to grief the perpetrator for the next 24 hours.
Nor does this allow alliance members or allies of the victim to attack the perpetrator outside of ROE.
As always the burden of proof rests on the attacker.
Anyone retaliating to an ROE violation is encouraged to have screenshots to back up their attacks and is also encouraged to contact the original perpetrator
before attacking in order to resolve any misunderstandings
[/font]
I'd like to keep this particularthread limited ONLY to discussion of the rules themselves, and not as to whether we will obey them fully or not. That will be a separate thread and I ask you to try and limit that discussion to that thread.
OK....here goes....
đź—’ ROE Cliff Notes Version
Understanding that the full version of this document and all the rules herein is very complex, a simpler
version is presented.
For players below level 15 the simpler rules apply and leniency should be given
where possible to violations.
The goal of the ROE is to make the game more fun to play, not to overwhelm the players with Do’s and Don’t’s.
â—Ź No killing in Armadas, Token Space, Deep Space
â—Ź Miners OPC and 0 node are legit kill
â—Ź Shield or Share
Star Trek Fleet Command (STFC) is a PVP game so killing and getting killed is to be expected;
therefore, as the members of server Epsilon 91 we create these Rules of Engagement (ROE) to promote
“Fair Play” which is essential to keeping this server entertaining, yet civilized. Keep in mind that you can
get PVP kills and others can also kill you – karma can be quite instant in this game. So, even if your
action is lawful and in accordance with ROE, it can still be considered a hostile act and incur retribution
in lawful manners.
đźš©Implementation of Server ROE
This ROE is a generic, server-level set of rules, and alliances are fully encouraged to enforce their “own” ROE.
However, any alliance-based modification of ROE as described henceforth, shall only be “additive” in nature.
This means that alliances can only make these rules more strict.
If the alliance-specific ROE is less restrictive than the server ROE, then they will be found in breach of server ROE.
đźš©Enforcement of Server ROE
The methods of ROE enforcement is on a per-alliance basis.
Keep in mind that diplomacy is always prefered than going into war.
Many ROE violations are simply due to mis-understanding of the ROE,
human error, or even game bugs, and can be resolved by talking it out in a civilized manner.
It is very important that participating alliances only act when there is indisputable “proof” of roe violation;
for example, a screenshot of the battle report.
Acting on “he said/she said” evidence is not going to help resolve the issue or clarify the timeline.
Unless stated within the rule, the party and its alliance reporting the violation has the burden of the proof.
An alliance may choose not to follow this ROE and cause grievance against the entire server population.
As such,with proof of non-participation, such alliance may be declared as Enemy of every participating alliance of this server ROE (edited)
– Participation of Server ROE
Participation of this server ROE is voluntary for each alliance. Participation does not infer or imply, an “Ally” or “Friendly” status between any of the participating alliances
[9:50 AM]
⚠️ ROE # 1. No Kill List
The following are not to be killed except during active War/KOS
â—Ź Any ships participating in Armadas
â—‹ Including up to one (1) minute for them to exit the area afterwards
● Any Ship in a system which has a cost associated with entering, commonly known as “Token
Systems”. Examples of such systems:
â—‹ Borg systems
â—‹ Rogue systems
â—‹ and any other current, and/or future token systems .
⚠️ ROE # 2. Mining Etiquette
Everyone should enjoy safe mining in order to grow, but should not clog up the mining nodes.
This inconveniences other players and directly affects their play.
NOTE: Due to the North Star’s combat ability, and its use as such, it is considered a survey ship only when actively mining on such a node.
This ROE may be ignored if the opposing alliance is marked as an “Enemy” for legitimate
reasons. See #6.
2a. Acceptable kills during mining:
â—Ź The ship is a survey ship, and is over the protected cargo limit, also known
as OPC
â—Ź The ship is a warship
2b. Special Notes Regarding “0 Node + UPC Kills”
It is an allowable attack per ROE if the miner being attacked is on a depleted node showing zero (0) resource or material left and an in game private message has been sent
(“0 node”, or “zero” is
sufficient) AND two (2) minutes has elapsed since the warning has been sent, so that screen shots of the battle report and message may be used for provenance in resolving any conflict regarding a UPC
attack on a miner. 2c. Any warship / mining vessel left derelict (floaters) or clogging mission planets can be targeted. (edited)
⚠️ ROE # 3. Warships are Fair Game
Warships are considered a fair target at all times.
Except when Discovery is mining Mycelium.
⚠️ ROE # 4. Shield or Share
An attack against a station is always considered lawful.
An attack towards any ship, participating in a defence or attack against a station, is considered lawful.
It is your responsibility, and yours alone to raise a shield to prevent attack. This includes stations inside
of claimed territories.
⚠️ ROE # 5. Territory Takeover is Fair Game
Anything is allowed inside the territory during the territory allocated takeover time.
It is designed by Scopely as a battleground for alliance to fight each other and therefore will be designated as such.
Outside of takeover times standard ROE applies to any players inside territories.
⚠️ ROE #6. Alliance KOS/Wars
Under some circumstances, such as repeated ROE violations, an Alliance may wish to declare another Alliance as “Kill on Sight” (KOS).
Generally this means that none of the ships of the target Alliance are protected by ROE.
However, the aggressor has a duty to inform their target of the new KOS status.
To avoid wars being called too frequently and unnecessarily any declaration of war must be in effect for at least 48 hours (2 days).
This reduces the appeal of declaring a war in order to dodge ROE for a short period of time before attempting to hide behind a truce.
⚠️ ROE #7. Retaliation
Inevitably someone will break or be ignorant of the standard ROE terms.
If ROE is violated, then the victim may respond in kind to the perpetrator within a twenty-four (24) hour period.
The victim should not turn around and use an ROE violation to grief the perpetrator for the next 24 hours.
Nor does this allow alliance members or allies of the victim to attack the perpetrator outside of ROE.
As always the burden of proof rests on the attacker.
Anyone retaliating to an ROE violation is encouraged to have screenshots to back up their attacks and is also encouraged to contact the original perpetrator
before attacking in order to resolve any misunderstandings
[/font]
