en:rules:pve:ratting

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
en:rules:pve:ratting [2025/12/01 17:40] – Arrowspeeed_Bountyen:rules:pve:ratting [2026/03/13 23:23] (current) – Arrowspeeed_Bounty
Line 1: Line 1:
 ====== Ratting ======  ====== 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.    
-         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. 
 +  * If you leave the site for any reason, ownership is automatically released.  
 +  * If you are not present in an appropriate ship for running the site, ownership is automatically released.   
 +  * The ownership of sites includes the wreck, salvage, loot, and escalations in it.  
 +  * Do not put Mobile Tractor Unit (MTU) in sites not owned by you.  Site owner is free to destroy it if you do.  
 +  * 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. 
 +    * In an AOE fleet, you may include only one support ship: either a sniper or an EWAR ship 
 +  * 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. 
 +  * If you are attacked or take damage from a blue, leave the area to avoid being destroyed if possible safely. If you don't, related cases will not be accepted by the diplo team. 
 + 
 +Communication Examples  
 +  * Effective Communication   
 +    * Noraus: AOE +1, rock haven priority. 
 +    * 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. 
 + 
 +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. 
 +  * 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. 
 +  * Do not spam 1 in the escalation trading channel, 
 + 
 +== Specisl Ratting Rules == 
 + 
 +Escalations 
 +  * Check details before accepting an escalation.  
 +  * Do not spam 1 in the escalation trading channel 
 +  * No "relisting" of escalation (buying to resell) 
 +  * Scanned combat signal DEDs cannot be sold, only escalations can be traded 
 +  * No trolling/politics in the escalation trade channel 
 +  * If the seller does not list a price when selling, the buyer may cancel the purchase 
 +  * Escalations can only be traded in the trading channel; buying from alliance channel or some private channel/chat is considered as relisting and results in blacklisting 
 + 
 +Asteroid Belts 
 +Belt Dreads / Bosses / Officer Spawns 
 + 
 +  * Only cruiser-class hulls or larger may claim ownership. First come, first served. 
 +  * Among qualified hulls, first come, first served. 
 +  * If you move more than 300 km outside the Boss’s engagement range, ownership is automatically forfeited. 
 + 
 +Bubbles  
 +  * To be added
  
-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. 
  
  
  
  • Last modified: 2025/12/01 17:40
  • by Arrowspeeed_Bounty