Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:rules:pve:ratting [2024/11/14 00:55] – Arrowspeeed_Bounty | en:rules:pve:ratting [2025/12/01 18:07] (current) – Arrowspeeed_Bounty | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Ratting ====== | ====== Ratting ====== | ||
| - | **<color #ed1c24> Capital Ratting Rules:\\ | + | === Fraternity |
| - | - Carriers -- Ratting is not recommended but allowed at your own risk. No saves or SRP\\ | + | == PVE Ratting Rules == |
| - | - Dreads -- Ratting is very dangerous | + | |
| - | - 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:// | + | |
| - | </ | + | |
| - | [[https:// | + | |
| - | [[https:// | + | |
| - | ===== 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" | ||
| + | * 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/ | ||
| + | * 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: | ||
| - | - For ratting activities in the Fraternity sovereignty area, please keep yourself within the [[https://bit.ly/wc-pvemap|permitted PVE area]]. | + | Communication Examples |
| - | | + | * Effective Communication |
| - | - Do not attack alliance members or other entities with a Positive standing | + | * Noraus: AOE +1, rock haven priority. |
| - | | + | * 1 (Copy/Acknowledged). |
| - | | + | * 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 | + | |
| - | - 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:// | + | * Result: |
| - | - Possible penalties for infractions include: warning, docking ban, fine, kill-on-sight status (in extreme | + | |
| - | + | * Scenario: A Haven is open locally, but an AOE pilot deliberately competes for other anomalies (e.g., a Hub) while " | |
| - | ===== Site Calling ===== | + | * Tang: Noraus, you aren't running |
| + | * Noraus: No. | ||
| + | * Action: In such cases, | ||
| - | - You must call the site in the dedicated ratting channel | + | 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" |
| - | | + | |
| - | | + | |
| - | - Before you start calling sites in a new solar system, declare your ship type first in the ratting channel | + | |
| - | - 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. | + | |
| - | ===== 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.// [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' | ||
| - | - 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, | ||
| - | - The priorities: | ||
| - | * Super, AOE fleet, marauder, carriers, ishtar, vexor have priority over other ship types. | ||
| - | * Any Sanctum or Regular Haven (not a gate haven) site anywhere in Fraternity space has these priorities: | ||
| - | * And any Gate Haven or Forsaken Rally Point or Forsaken Hub site has these priorities: | ||
| - | * These priorities only apply to systems with ratting shub upgrades, systems with ore shub upgrades apply first come first serve (calling sites still required). | ||
| - | - 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. | ||
| - | - Scannable DED sites | ||
| - | * Trading of sites is not allowed | ||
| - | * Ownership is based on first-come-first-serve basis. //This means that you must occupy the site with a suitable and active ratting ship.// | ||
| - | * If you leave for any reason, the ownership will be revoked automatically. | ||
| - | * 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 '' | ||
| - | * 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. | ||