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/08/05 01:56] – [Ratting] Super rule page name was changed from "crab" to "rules for supers" Eingang_Vulpineen:rules:pve:ratting [2025/12/01 18:07] (current) – Arrowspeeed_Bounty
Line 1: Line 1:
 ====== Ratting ======  ====== Ratting ====== 
  
-**<color #ed1c24> Capital Ratting Rules:\\ +=== Fraternity and Winter Coalition Communal Space === 
-- Carriers -- Ratting is not recommended but allowed at your own risk. No saves or SRP\\ +== PVE Ratting Rules ==
-- Dreads -- Ratting is very dangerous and not recommended but allowed at your own risk. No saves or SRP\\ +
-- Supers --  Super ratting is allowed at your own risk within 6 light years of 4-HW. No saves or SRP. Supers must also follow these rules if they are ratting: https://wiki.winterco.org/en/rules/other/rules_for_supers.   +
-</color>**\\ +
-[[https://docs.google.com/document/d/1uNiGPkstFMRP1I-HiotVy7P4LHaV-BsnRD262so5xds/edit?usp=sharing|Ratting Rules in Spanish]] (Google Doc by Caramon) +
-[[https://docs.google.com/document/d/10teqe9vEcq-lZG4uj8Dw8bC29eFPeBO9DTFNSNBfvl0/edit#heading=h.wk4mn6nqvnfx|Ratting Rules in Russian]] (Google Doc by Inos Anzomi)+
  
-===== 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 Fraternity sovereignty area, please keep yourself within the [[https://bit.ly/wc-pvemap|permitted PVE area]].  +Communication Examples  
-    - Capitals are exclusively allowed to bait with proper reinforcements in ''4-HWWF''. Other capital 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 in game and the relevant Mumble Standing Channel are mandatory to join when ratting (read MOTD in fleet). If you are tackled, ask for help in Mumble and provide accurate information. +    * 1 (Copy/Acknowledged). 
-  - Do not AFK in supercapitals while tethering. Please dock or safe-log if you leave.  +  * Not-Effective Communication 
-  - If a Rorq deploys a CONCORD Rogue Analysis Beacon (CRAB), it must be in an asteroid belt with ores and the Rorq must be fitted with PANIC module.  +    * Tang: AOE +1, rock haven priority. 
-  - Traffic lights are used to determine if certain ships may undock for PVE. Traffic lights do not influence ship priorities for sites. +    * Noraus: I am in an Ishtar, and I refuse to yield. 
-  - Please see Supers rules here   https://wiki.winterco.org/en/rules/other/rules_for_supers. +    * Result: The Ishtar warps into the AOE fleet and is destroyed. No SRP will be provided for this incident. 
-  - Possible penalties for infractions include: warning, docking ban, fine, kill-on-sight status (in extreme cases), membership removal, and blacklisting. +  * 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. 
-===== Site Calling =====+    * 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 ratting channel (if available) before warping to sites in sovereignty space. Use the trailing 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 someone calling out corrections unusually frequently. +  * Dispute Resolution: If losses occur due to a dispute and private negotiation fails, please contact an Alliance Diplo for arbitration.
-  - BBefore you start calling sites in a new solar system, declare your ship type first in the ratting channel (i.e. Ishtar +1, AoE +1). After completion of ratting activities in the system, report ship type in ratting channel (i.e. Ishtar -1, AoE -1). +
-  - When a player with a higher priority ship starts calling sites, the other players should cease calling new sites of that type immediately. You are still allowed to finish the current site before you switch.  If you are the higher prioity ship, you should continue to call sites. (This avoids confusion when you leave or if others enter after you have announced your priority status in local.)  +
-  - A single member is prohibited from running more than 5 sites simultaneously in the same system for ratting  +
-  - Even if a ship has priority, members must still follow sites calling procedures.  Exeption for AOE ships, see next rule.  +
-  - AOE site calling  +
-    - If more than one AOE says +AOE, they can optionally open private chat and, //by mutual agreement//, text each other the site number. +
-    - If someone asks if AOE is active, AOE must respond within 3 minutes or whoever asks can take a site. +
-    - If a ship with lower priority calls a rock haven, AOE should make a reminder and lower ship should not take this site. //The lower ship should be aware that trying to take the site will risk friendly fire from unstoppable smartbombs/vortons.//  +
-    - In this case, AOE is responsible to stop smartbombs/vortons in time to avoid friendly kills.  +
-    - The rule can only be used after effective communication with full understanding. If any of AOE pilots refuse, call sites normally in ratting channel. +
-    - After reaching this agreement. They must send a remainder in ratting channel. AOE pilots should be responsible for any friendly fire accidents. +
-    - No arguements between AOE pilots are allowed.+
  
-===== Ownerships ===== 
  
-  - If you leave the site for any reason, the ownership is automatically released. Other players are free to occupy the site from this 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.// [more detail: The first appropriate ship to enter a plex, anomaly, mining/gas site, or other cosmic signature has the right to run it or kill rats only so long as that pilot is present in that appropriate ship. For gas sites, it’s per cloud, not for the whole anomaly. “Appropriate” means that the ship is fitted and reasonable for completing that kind of PvE content. That is, you can’t “reserve” a PvE site by putting some other ship/pilot into it and then coming back later to run it with a different ship or pilot.]// 
-  - 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.  
-  - Ship priorities: Priorities vary by type of site. Please read these rules carefully, especially regarding the distinction between ship priorities for the two types of Havens (regular/rock Havens) and (gate/gas Haven). All ships must call sites. (Exception for AOE ships, see rule 9 in site calling section.)  
-    - Definitions: AoE Fleet: A fleet of 3 or more characters, consisting of any mix of smartbombing ships, Stormbringers, and Thunderchildren. Smartbombing: At least 2 characters in smartbombing battleships (i.e. Machariel, Praxis) 
-    - Sanctum and Regular ("Gas") Haven (no rock in it) anywhere in Fraternity play space with ratting shub upgrades. In order of highest priority to lowest: 
-      - Supercarrier 
-      - AOE fleet. Carrier, Smartbombing 
-      - Maurauder  
-      - Ishtar, Battleship 
-      - Vexor, Myrmidon 
-      - Any other ratting ship 
-    - Gate ("Rock") Haven, Forsaken Rally Point, Forsaken Hub anywhere in Fraternity play space with ratting shub upgrades. In order of highest priority to lowest: 
-      - AOE fleet, smartbombing 
-      - Supercarrier 
-      - Carrier 
-      - Marauder 
-      - Ishtar, Battleship 
-      - Vexor, Myrmidon 
-      - Any other ratting ship 
-    - Other ratting sites 
-      * No ship priorities apply. 
-      * First to enter the site with a suitable and active ratting ship owns the site. 
- 
-==== Officers, Capital Rats and other Faction Rats ==== 
- 
-  * No ship priorities apply. Site calling is still required. First come, first served. 
-  * Cruiser and above is a suitable ratting ship. Frigates and Destroyers are not allowed.  
-  * If you are out of the 300km range of the NPC, the ownership is automatically released. 
- 
-==== Scannable DED sites ==== 
- 
-  * No ship priorities apply. First to enter the site with a suitable and active ratting ship owns the site. 
-  * If you leave for any reason, the ownership is automatically released. 
-  * Trading of sites is not allowed. 
-  * If unsure whether a scannable site is taken, please politely communicate in local or ratting channel to establish ownership. 
- 
-===== 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: 2025/08/05 01:56
  • by Eingang_Vulpine