Differences

This shows you the differences between two versions of the page.

--- en:rules:pve:ratting [2025/12/01 17:40] – Arrowspeeed_Bounty
+++ en:rules:pve:ratting [2025/12/01 18:07] (current) – Arrowspeeed_Bounty
@@ Line 1: / Line 1: @@
 ====== Ratting ======
-==== Fraternity and Winter Coalition Communal Space ====
+=== Fraternity and Winter Coalition Communal Space ===
+== PVE Ratting Rules ==
-PVE Ratting Rules
+Core Rules
-I. Core Rules
+  * No Site Calling: Calling out anomalies in chat is no longer required, with the exception of AOE. **Ratting channels will no longer be used** Use local or another method for communication instead of ratting channels.
-      	No  Site Calling: Calling out anomalies in chat is no longer required, with the exception of AOE.   Ratting channels will no longer be used. Use local or another method for communication instead of ratting channels.
+  * Priority. All rat sites operate on a strictly "First Come, First Served" (FCFS) basis.
+  * Haven Priority:
+    * AOE fleets (Smartbombers and Thunderchild or Stormbringer) hold the highest priority for Havens.
+    * If an AOE fleet is present, conventional ratters in local must yield the Haven.
+    * If two or more AOE fleets are present in local, pilots are encouraged to coordinate via private chat to avoid collision/conflict.
+  * Ship Efficiency & Multiboxing:
+    * Low-efficiency ships (e.g., Vexors) are reserved only for pilots with insufficient skills (low SP).
+    * Multiboxing these slow ships are prohibited, as it negatively impacts the system overall spawn rate.
+  * Resource Allocation (Crowded Systems): In cases of overcrowding or insufficient system resources, pilots must follow the Alliance Recommended Model.
+    * Ishtars (CN call YST) run Hubs.
+    * Marauders run Sanctums.
+    * AOE fleets run Havens.
+  * Enforcement: Any behavior deemed to be impeding another pilot rating will result in an immediate docking ban followed by a kick, once confirmed by Alliance Diplo.
-Priority. All rat sites operate on a strictly "First Come, First Served" (FCFS) basis.
+Communication Examples
-      	Haven Priority:
+  * Effective Communication
-        	◦       	AOE fleets (Smartbombers and Thunderchild or Stormbringer) hold the highest priority for Havens.
+    * Noraus: AOE +1, rock haven priority.
-        	◦       	If an AOE fleet is present, conventional ratters in local must yield the Haven.
+    * 1 (Copy/Acknowledged).
-        	◦       	If two or more AOE fleets are present in local, pilots are encouraged to coordinate via private chat to avoid collision/conflict.
+  * Not-Effective Communication
-      	Ship Efficiency & Multiboxing:
+    * Tang: AOE +1, rock haven priority.
-        	◦       	Low-efficiency ships (e.g., Vexors) are reserved only for pilots with insufficient skills (low SP).
+    * Noraus: I am in an Ishtar, and I refuse to yield.
-        	◦       	Multiboxing these slow ships are prohibited, as it negatively impacts the system overall spawn rate.
+    * Result: The Ishtar warps into the AOE fleet and is destroyed. No SRP will be provided for this incident.
-      	Resource Allocation (Crowded Systems): In cases of overcrowding or insufficient system resources, pilots must follow the Alliance Recommended Model.
+  * Exploiting/Griefing Example
-        	◦       	Ishtars (CN call YST) run Hubs.
+    * Scenario: A Haven is open locally, but an AOE pilot deliberately competes for other anomalies (e.g., a Hub) while "holding" the Haven hostage so others cannot run it.
-        	◦       	Marauders run Sanctums.
+    * Tang: Noraus, you aren't running the Haven with your AOE, can I take it?
-        	◦       	AOE fleets run Havens.
+    * Noraus: No.
-      	Enforcement: Any behavior deemed to be impeding another pilot rating will result in an immediate ban followed by a kick, once confirmed by Alliance Diplo.
+    * Action: In such cases, please submit chat logs and screenshots. Verified incidents will be penalized according to Enforcement Rule #5.
-II. Communication Examples
-. 	Effective Communication
-Noraus: AOE +1, rock haven priority.
-Tang: 1 (Copy/Acknowledged).
-. 	Not-Effective Communication
-Tang: AOE +1, rock haven priority.
-Noraus: I am in an Ishtar, and I refuse to yield.
-Result: The Ishtar warps into the AOE fleet and is destroyed. No SRP will be provided for this incident.
-. 	Exploiting/Griefing Example
-Scenario: A Haven is open locally, but an AOE pilot deliberately competes for other anomalies (e.g., a Hub) while "holding" the Haven hostage so others cannot run it.
-Tang: Noraus, you aren't running the Haven with your AOE, can I take it?
-Noraus: No.
-Action: In such cases, please submit chat logs and screenshots. Verified incidents will be penalized according to Enforcement Rule #5.
- III. PVE SRP (Ship Replacement Program)
+PVE SRP (Ship Replacement Program)
-      	AOE Liability: Casualties caused by AOE fleets are considered "no fault" (no liability) unless the action was intentional or malicious. No compensation is required.
+  * AOE Liability: Casualties caused by AOE fleets are considered "no fault" (no liability) unless the action was intentional or malicious. No compensation is required.
-      	Violation Liability: Any losses resulting from rule violations must be SRP (paid for) by the offending pilot, barring special circumstances.
+  * Violation Liability: Any losses resulting from rule violations must be SRP (paid for) by the offending pilot, barring special circumstances.
-      	Dispute Resolution: If losses occur due to a dispute and private negotiation fails, please contact an Alliance Diplo for arbitration.
+  * Dispute Resolution: If losses occur due to a dispute and private negotiation fails, please contact an Alliance Diplo for arbitration.