Differences

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

--- en:rules:pve:ratting [2022/07/31 15:18] – created user11262
+++ en:rules:pve:ratting [2026/05/15 01:50] (current) – Arrowspeeed_Bounty
@@ Line 1: / Line 1: @@
-FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)//
+====== Ratting ======
-====== Rattings ======
+=== Fraternity and Winter Coalition Communal Space ===
+== PVE Ratting Rules ==
-**<color #ed1c24>NB: Supercapital ratting is BANNED across all areas.</color>**
+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.
+  * 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.
-===== Basic Rules =====
+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.
-  - For ratting activities in the sovereignty area, please keep yourself within the [[start##range_of_pve_activities|Range of PvE Activities]].
+PVE SRP (Ship Replacement Program)
-  - 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.
+  * AOE Liability: Casualties caused by AOE fleets are considered "no fault" (no liability) unless the action was intentional or malicious. No compensation is required.
-  - The Standing Fleet and the Mumble Standing Channel are mandatory to join when ratting. Yell loudly and provide accurate information if being caught.
+  * Violation Liability: Any losses resulting from rule violations must be SRP (paid for) by the offending pilot, barring special circumstances.
-  - Do not AFK in super capitals while tethering. Please dock or safe-logoff if you leave.
+  * 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 ==
-    * 安等 -0.5 ~ -1.0 的星系
-      * 避难、圣坛（大小避难、大小圣坛）：大航 = 小航 = 无畏 = 掠夺 > 常规 = 炸鱼队
+Escalations
-      * 其他异常空间：先报点先得
+  * Check details before accepting an escalation.
-    * 安等 -0.1 ~ -0.4 的星系
+  * 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
-  - 小行星带刷无畏、Boss、官员（统称 Boss）
+  * No trolling/politics in the escalation trade channel
-      * 遵循刷怪船先到先得扛得住原则。即，需要使用合理的刷怪船，第一个入场，在 Boss 面前站得住直至击杀（或喊人前来击杀）Boss，则获得该 Boss 的残骸。中途如果离场或者被 Boss 击毁，则其他人有权通过入场的方式获得 Boss 所有权。
+  * 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
-===== Ownership of Anomalies =====
+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
+  * From a stargate anchored Mobile Warp Disruptors 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.
+  * These gates are exceptions.
+    * ls-jep <> udvw-o
+    * h-5gui <> mr4-my
+    * p3en-3 <> obe
+For these, you  have the right to anchor any size bubble on either side of the gate at 5km,
++ All anchor bubbles are required to be attended and can be shot down if not (with screenshot).
++ If a cta is pinged, all bubbles must be taken down, and all strat ops reserve the right to kill any bubble in their path by order of the FC.
++ SRP is owed for ships lost in unattended bubbles and non-military situations (e.g. ratting).  There will be some case-by-case  judgement calls that will need to be evaluated for specific situations.  For example, a situation where there are roaming enemies en-mass -- that would be considered a military situation.
-  - 刷完一个异常空间以后才可以在报点频道报点，获得下一个异常空间的所有权，需要提前朝向的旗舰可以在合理时间内提前报点。
-  - 无论是来敌还是主动放弃异常空间，离开则视为放弃该异常空间的所有权，其他刷怪舰船可通过报点获得该异常空间所有权。离开后若无其他人占据，请继续刷完该异常空间，禁止重新报点。
-  - 未刷怪行为的舰船在异常空间挂机占位会被强制移除所有权，包括各种原因导致的下线或者AFK等。联盟会依据实际报点与刷怪情况予以考虑，妥善处理由此产生的纠纷，
-  - 报点获得异常空间所有权后，其中包含的残骸垃圾、远征以及任何附加价值物品都属于刷怪舰船。
-  - 打捞异常空间里的残骸垃圾，必须在报点频道内征得刷怪舰船的同意。
-  - 禁止在未报点的异常空间内提前放置移动牵引装置（MTU）。未征得同意放置MTU的，刷怪舰船可以在保留截图证据后，将该MTU击毁。
-===== Site Calling =====
-  - 刷怪角色报该角色刷的异常空间，多开刷怪的不能用一个角色报其他角色刷怪的点。
-  - 如果报错点，及时在报点频道说明，再重新报点。如遇挑点刷怪（经常报点又说不刷的），请及时向联盟管理反馈。
-  - 刷怪舰船开始生产前，应当再报点频道应打出：大航+1、小航+1、常规+1等，向本星系其他刷怪船说明自己舰船类型。
-  - 同星系有对某一异常空间优先的舰船开始生产时，其他舰船禁止获得该类异常空间。若此时低优先级舰船正在生产，刷完当前异常空间后立即更换异常空间类型。高优先级舰船开始报点后，后续低优先级舰船报点获得的同类异常空间均无效。
-===== Others =====
-  * 公共星系锚定星门泡泡用于反收割的，需在门后200km以上锚定。不得锚定在星门后200km以内，不得锚定在星门前，不得锚定在星门0米，不得锚定在500km以外。锚定规则的目的是使友军可以反向加速直接起跳星门。必须有人值守。
-  * P3EN的Obe星门可以铆钉贴门泡泡。
-  * 如果你有很多开常规号且集中放置，会特殊处理，按实际情况裁量，参考数目：同星系多开五个及以上常规生产。
-  * ESS储备属于星系主权（TCU）所属联盟成员所有，FRT成员仅允许开启FRT主权星系的储备赏金池。
-  * 联盟会以公布的规则作为管理的依据，但保留最终解释权。