This is an old revision of the document!
Ratting
Fraternity and Winter Coalition Communal Space
PVE Ratting Rules I. Core Rules
1 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.
2 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.
3 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.
4 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.
5 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.
II. Communication Examples 1. Effective Communication Noraus: AOE +1, rock haven priority. Tang: 1 (Copy/Acknowledged). 2. 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. 3. 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)
1 AOE Liability: Casualties caused by AOE fleets are considered "no fault" (no liability) unless the action was intentional or malicious. No compensation is required.
2 Violation Liability: Any losses resulting from rule violations must be SRP (paid for) by the offending pilot, barring special circumstances.
3 Dispute Resolution: If losses occur due to a dispute and private negotiation fails, please contact an Alliance Diplo for arbitration.