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 [2022/10/31 00:32] – Maria_Tayloren:rules:pve:ratting [2025/12/01 18:07] (current) – Arrowspeeed_Bounty
Line 1: Line 1:
-====== Rattings ====== +====== Ratting ====== 
  
-**<color #ed1c24>Supers can rat under the super umbrella range（except 4-HWWF and P3EN-E). Supers must follow supercarrier traffic lights. Dreads are not allowed to rat under umbrella</color>**+=== Fraternity and Winter Coalition Communal Space === 
 +== PVE Ratting Rules ==
  
-===== Basic Rules =====+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.    
 +  * 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.
  
-  - For ratting activities in the sovereignty area, please keep yourself within the [[https://docs.google.com/presentation/d/1K9Ijo1H8-z3u3bdBbzyLHGn-N1Ay4gDZgyri2aVInmM/edit#slide=id.p|permitted PVE area]]. Generally, your activity is limited within systems containing a TCU of your resident alliance. +Communication Examples  
-    - Capitals are exclusively allowed to bait with proper reinforcements in ''4-HWWF''. Other activities here are strictly forbidden. +  * Effective Communication   
-  - Do not attack alliance members or other entities with a Positive standing in any scenario. Please contact the Coalition directors should you encounter any issues. +    * Noraus: AOE +1, rock haven priority. 
-  - The Standing Fleet and the Mumble Standing Channel are mandatory to join when ratting. If you are tackled, ask for help in Mumble and provide accurate information. +    * 1 (Copy/Acknowledged). 
-  - Do not AFK in super capitals while tethering. Please dock or safe-log if you leave.  +  * Not-Effective Communication 
-  - The CONCORD Rogue Analysis Beacon should only be deployed in Asteroid Belts with Ores. Only use Rorquals with PANIC to run those sites within the supercapital umbrella. +    * Tang: AOE +1, rock haven priority. 
-  - The ship priorities are not influenced by traffic lights. +    * Noraus: I am in an Ishtar, and I refuse to yield. 
-  - The penality involves: warning, docking ban, fine, kill-on-sight, membership removal, and blacklisting. +    * Result: The Ishtar warps into the AOE fleet and is destroyed. No SRP will be provided for this incident. 
-  +  * Exploiting/Griefing Example 
-===== Site Calling =====+    * 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.
  
-  - You must call the site in the dedicated channel before warping to sites in sovereignity space. Use the latter 3 number code when calling sites.(e.g. send ''123'' to the channel for site ''ABC-123'') +PVE SRP (Ship Replacement Program)  
-  - Call sites with the actual ratting character, even if you have multiple characters ratting at the same time. Do not call sites for alts using a single character. +  * AOE Liability: Casualties caused by AOE fleets are considered "no fault" (no liability) unless the action was intentional or malicious. No compensation is required. 
-  - Only call the next site after the previous site is finished. Capitals are allowed to align and call the next site preemptively after the final wave spawns.  +  * Violation Liability: Any losses resulting from rule violations must be SRP (paid for) by the offending pilot, barring special circumstances. 
-  - If you called a wrong site, correct it immediately before calling a new one. Please report to Coalition Director if you find out that someone does calling and corrections in an abnormally frequent fashion. +  * Dispute Resolution: If losses occur due to a dispute and private negotiation fails, please contact an Alliance Diplo for arbitration.
-  - Before you start calling sites in a new solar system, declare your ship type first in the ratting channel for each character. +
-  - When a player with a higher priority ship starts calling sites, the other players should cease calling new ones immediately. You are still allowed to finish the current site before you switch.+
  
-===== Ownerships ===== 
  
-  - If you leave the site for any reason, the ownership is automatically released. Other players are free to occupy the site from the point on. In case you return and the site is not occupied by others, please finish the site than calling a new one. 
-  - Your ownership will be revoked if not attacking rats in a reasonable period of time. 
-  - The ownership of sites includes the wreck, loot, and escalations in it. Ask for owner's permission before salvaging the site. 
-  - Do not put Mobile Tractor Unit (MTU) in sites not owned by you. The site owner is free to destroy the MTU owned by others after taking full screenshots, including the ratting channel.  
-  - The priorities:  
-      * haven and sanctums: supercarrier > carrier = subcaps ＝ smartbomb ＝ marauder  
-      * Other anomalies：First-come-first-serve 
-  - Officers, Capital Rats and other Faction Rats 
-      * Only eligible ratting ships (Cruiser and above) have the right to claim ownership. Frigates and Destroyers are not allowed. 
-      * Ownership is based on first-come-first-serve basis. 
-      * If you are out of the 300km range of the NPC, the ownership is automatically released. 
- 
-===== Others ===== 
- 
-  * From a stargate anchored Mobile Warp Disruptors (Anchor bubbles) must be centered at least 200 km away from the gate but not more than 500 km. Once you are more than 1000 km away from the gate the anchor bubble rules end. Multiple bubbles can be evenly spaced, but not embedded. Once that has stopped somebody you are encouraged to use a cloaked Dictor / HIC to keep somebody (dictor) bubbled. All distances here are measured from center of bubble and rule would not be intended to cover citadels near the gate. Do not leave bubbles unattended. This rule is effective for all FRT sov systems, and the traffic barebones in sov systems of other Coalition members. 
-  * The bubble on ''Obe'' stargate in ''P3EN-E'' system can be deployed next to the gate. 
-  * Please do not run more than 5 ratting characters in a single system. 
-  * When disputes happen between different language speakers, you may ask the corporation and alliance directors for communication assistance.  
-  * The Coalition Directors will take the published rules as the basis for management and reserve the right of final interpretation. 
  
  • Last modified: 2022/10/31 00:32
  • by Maria_Taylor