Wormhole tactical considerations
From Agony Unleashed
Original text by Ged Hawkins.
This document summarizes tactical considerations of wormholes and wormhole space (W-space). It does not cover PvE content.
Contents
TL;DR Summary
- wormholes have a 5 km jump range
- after jumping, you have a standard 10 second session change timer and a 1 minute jump cloak
- there is a separate 5 minute jump timer for EACH direction of traversing a wormhole
- there are NO weapons timers for wormholes
- you ALWAYS emerge from wormholes within jump range, between 1km and 5km
- you MAY (~30% of the time) emerge from a wormhole too close to allow activation of a cloaking module
- there is DELAYED LOCAL in W-space; character names do not show up unless they talk in Local
Glossary and definitions
- K-space: "known" space, includes highsec, lowsec, and standard 0.0 space
- W-space: "wormhole" space, reachable by wormholes; systems named J######
- all W-space is effectively nullsec, with no CONCORD intervention or security status hits for aggression
- wormhole: analogous to stargates in K-space, wormholes connect systems which may be in either K-space or W-space or both
Delayed local
- unlike in K-space, players in-system do NOT appear in the Local player list, unless they say something in local channel
- obviously, this is helpful to surprise targets, especially when used in conjunction with cloaking ships
Wormholes
- do not appear on the overview unless you are on-grid with them
- are found by using scanner probes
- wormholes are found under scan probe group "Cosmic Signatures" of type "Unknown"
- in K-space, "Unknowns" can be either combat exploration sites or wormholes
- in W-space, ALL "Unknowns" are wormholes
Wormhole jump characteristics
- must be within 5000 meters to traverse a wormhole
- traversing a wormhole initiates a standard 10 second session change timer
- on arrival, you have a standard "jump cloak" that lasts 60 seconds, significantly longer than the session change timer
- on arrival, you will always(1) appear within jump-back range of the wormhole
- ~30% of the time, you appear <2,000 meters, so too close to activate a cloaking module
- (1) in only ONE time out of 100 jumps, the ship appeared at >5,000 meters, outside of jump-back range; not sure if that was a bug
- there are NO weapons timers for wormholes; you do NOT need to "de-aggress" before being able to traverse a wormhole
Wormhole jump timer
- wormholes have a 5 minute jump timer
- there is a SEPARATE jump timer for EACH one-way trip across a given wormhole
- if you try to traverse a wormhole before the 5 minute timer elapses, you'll get the message ""A recent transit through this wormhole has polarized your secondary coils, making it unsafe to re-enter right now. The polarity charge should dissipate within # seconds."
- Example 1:
- you jump across a wormhole from system A to B at time T1, then after the 30 second session timer, you can immediately jump back from B to A
- however, you will NOT be able to jump from A to B again until time T1 + 5 minutes
- Example 2:
- you jump across a wormhole from system A to B, hang out in B for half an hour (thereby clearing the A to B jump timer), then jump back from B to A at time T2
- you can immediately jump from A to B again (after the 10 second session change timer)
- but, you will NOT be able to jump form B to A again until time T2 + 5 minutes
Cloaking
- you can not traverse a wormhole cloaked, either from a "jump cloak" or from a module
- wormholes will decloak you, or prevent you from cloaking, within 2000 m
Locator agents and Intel
- level 3 and 4 locator agents are able to report back the J###### system that players are located in
- because of delayed Local and the inability to see who else is in-system with you, this can be a useful tool if you were able to catch the enemy's name
- for the same reason, it is a VERY good idea to make sure that your name is NOT part of your ship name
- DOTLAN can report jumps / NPC kills / player + podkills of W-space systems, e.g. http://evemaps.dotlan.net/system/J170717
Wormhole Designations / Mass Limits / Time Limits
- W-space systems ALWAYS have at least one wormhole exit
- K-space systems may or may not have any wormholes
- There are three stages or states in a wormhole's life, which you can get with a 'show info' on the wormhole:
- Not Yet Disrupted (aka Pristine)
- Disrupted But Not Critically (aka Intermediate)
- Critical.
- There is a fourth relevant status, which may be displayed below the stage information: "reaching the end of its natural lifetime". This means the wormhole will collapse of old age within two hours or less.
You can tell the state of the wormhole you are about to enter by right-clicking and selecting "Show Info". A pristine wormhole has not yet had 60% of its allotted mass pass through it. An Intermediate wormhole has between 40% and 10% of its allotted mass left. A Critical wormhole has less than 10% of its allotted mass left.
- when on-grid with a wormhole, you can see the wormhole "name" on Overview, which is a letter and 3 numbers: X###
- when a wormhole is FIRST probed out and warped to, you will see a X### name, from which you can determine some information, including:
- what type of system the destination will be: i.e., Class 1 (Unknown) to Class 6 (Deadly Unknown) W-space; or highsec, lowsec, or nullsec K-space
- maximum amount of mass that can traverse the wormhole
- cumulative mass limit before the wormhole will collapse
- total lifetime before the wormhole will collapse
- from the OTHER side of the wormhole, the name will ALWAYS be "K162", which does not specify any further information
- however, you can "Get info" on a "K162" wormhole to get some vague information about type of destination, mass status, timer status
- so, if you probe down a wormhole and see that it's called "K162", you KNOW that it's already been probed out by somebody from the OTHER side
- on my testing, the mass limits are NOT simply "mass of ship + mass of online modules" -- a fresh wormhole collapsed before the predicted # of jumps; there also appears to be a "random factor" applied to the cumulative mass limits (possibly up to ~10%), as testing with two "fresh" wormholes of the same type, reported required different numbers of jumps of identical ships to collapse
- RUMOR has it that traversing a wormhole with an activated MWD increases the amount of "mass" used up by the traversal; I have not confirmed this
- MWD or Ab increasing mass of the ship is definently not an rumor. It can be seen on their info page, in fitting window when active, and it's frenquently exploited by fitting 100mn ABs to cruisers to use as WH closing ships. AB and MWD of same size increase the mass by same ammount. Also, if mass is concern, armor plates can be offlined as they have significant mass.
- It is not possible to cyno or clonejump to or from WH systems. It's impossibel to claim sov, and no connection can handle supercap, so there are no supercaps in WHs. Some connections to hi-class WHs can handle capitals, but those never spawn to hisec. It's always possible to build capital inside WH system.
| Wormhole Name | Class | Mass Allowed (kg) | Quota (kg) | Lifetime |
|---|---|---|---|---|
| A641 | High sec | 1,000,000,000 | 2,000,000,000 | 16h |
| A982 | Class 6 Deadly | 300,000,000 | 3,000,000,000 | 24h |
| B041 | Class 6 Deadly | 300,000,000 | 5,000,000,000 | 48h |
| B274 | High sec | 300,000,000 | 2,000,000,000 | 24h |
| B449 | High sec | 1,000,000,000 | 2,000,000,000 | 16h |
| B520 | High sec | 300,000,000 | 5,000,000,000 | 24h |
| C125 | Class 2 Unknown | 20,000,000 | 1,000,000,000 | 16h |
| C140 | Low sec | 1,350,000,000 | 3,000,000,000 | 24h |
| C247 | Class 3 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| C248 | Null sec | 1,800,000,000 | 5,000,000,000 | 24h |
| C391 | Low sec | 1,800,000,000 | 5,000,000,000 | 24h |
| D364 | Class 2 Unknown | 300,000,000 | 1,000,000,000 | 16h |
| D382 | Class 2 Unknown | 300,000,000 | 2,000,000,000 | 16h |
| D792 | High sec | 1,000,000,000 | 3,000,000,000 | 24h |
| D845 | High sec | 300,000,000 | 5,000,000,000 | 24h |
| E175 | Class 4 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| E545 | Null sec | 300,000,000 | 2,000,000,000 | 24h |
| G024 | Class 2 Unknown | 300,000,000 | 2,000,000,000 | 16h |
| H121 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| H296 | Class 5 Dangerous | 1,350,000,000 | 3,000,000,000 | 24h |
| H900 | Class 5 Dangerous | 300,000,000 | 3,000,000,000 | 24h |
| I182 | Class 2 Unknown | 300,000,000 | 2,000,000,000 | 16h |
| J224 | Low sec | 20,000,000 | 1,000,000,000 | 24h |
| K162 | n/a | |||
| K329 | Null sec | 1,800,000,000 | 5,000,000,000 | 24h |
| K346 | Null sec | 300,000,000 | 3,000,000,000 | 24h |
| L477 | Class 3 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| L614 | Class 5 Dangerous | 20,000,000 | 1,000,000,000 | 24h |
| M267 | Class 3 Dangerous | 300,000,000 | 1,000,000,000 | 16h |
| M555 | Class 5 Dangerous | 1,000,000,000 | 3,000,000,000 | 24h |
| M609 | Class 4 Dangerous | 20,000,000 | 1,000,000,000 | 16h |
| N062 | Class 5 Dangerous | 300,000,000 | 3,000,000,000 | 24h |
| N110 | High sec | 20,000,000 | 1,000,000,000 | 24h |
| N290 | Low sec | 1,800,000,000 | 5,000,000,000 | 24h |
| N432 | Class 5 Dangerous | 1,350,000,000 | 3,000,000,000 | 24h |
| N766 | Class 2 Unknown | 300,000,000 | 2,000,000,000 | 16h |
| N770 | Class 5 Dangerous | 300,000,000 | 3,000,000,000 | 24h |
| N944 | Low sec | 1,350,000,000 | 3,000,000,000 | 24h |
| N968 | Class 3 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| O128 | Class 4 Dangerous | 300,000,000 | 1,000,000,000 | 24h |
| O477 | Class 3 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| O883 | Class 3 Dangerous | 20,000,000 | 1,000,000,000 | 16h |
| P060 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| Q317 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| R051 | Low sec | 1,000,000,000 | 3,000,000,000 | 16h |
| R474 | Class 6 Deadly | 300,000,000 | 3,000,000,000 | 24h |
| R943 | Class 2 Unknown | 300,000,000 | 750,000,000 | 16h |
| S047 | High sec | 300,000,000 | 3,000,000,000 | 24h |
| S199 | Null sec | 1,350,000,000 | 3,000,000,000 | 24h |
| S804 | Class 6 Deadly | 20,000,000 | 1,000,000,000 | 24h |
| T405 | Class 4 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| U210 | Low sec | 300,000,000 | 300,000,000 | 24h |
| U319 | Class 6 Deadly | 1,800,000,000 | 50,000,000,000 | 48h |
| U574 | Class 6 Deadly | 300,000,000 | 3,000,000,000 | 24h |
| V283 | Null sec | 1,000,000,000 | 3,000,000,000 | 24h |
| V301 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| V753 | Class 6 Deadly | 1,350,000,000 | 3,000,000,000 | 24h |
| V911 | Class 5 Dangerous | 1,350,000,000 | 3,000,000,000 | 24h |
| W237 | Class 6 Deadly | 1,350,000,000 | 3,000,000,000 | 24h |
| X702 | Class 3 Dangerous | 300,000,000 | 1,000,000,000 | 24h |
| X877 | Class 4 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| Y683 | Class 4 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| Y790 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| Z060 | Null sec | 20,000,000 | 1,000,000,000 | 24h |
| Z142 | Null sec | 1,350,000,000 | 3,000,000,000 | 24h |
| Z457 | Class 4 Dangerous | 300,000,000 | 2,000,000,000 | 16h |
| Z647 | Class 1 Unknown | 20,000,000 | 500,000,000 | 16h |
| Z971 | Class 1 Unknown | 20,000,000 | 100,000,000 | 16h |
W-space system effects
- some W-space systems have effects on all ships within the system
- in systems with these effects, be careful engaging people who reside there -- in a heavily shield-favored system, your armor-tanked remote rep fleet might not do so well against the resident shield-tankers
Tactic: "Wormhole Pinning"
- The "basic" sleeper combat site is anomaly, which can be found with onboard scanner. Thus, it's possible to find people running anomalies without ever uncloaking or using probes, which gives really nice potential for suprise. Though all ships entering grid with sleepers can become targets of sleepers still left, so RR is recommended.
- ALWAYS have prober with you, in case the connection home collapses or is intentionally collapsed.
- RR fleets in WHs commonly field scorpions, to be prepared to face ECM.
- On hi-class WHs people are almost always using RR, and incoming DPS can be very high, meaning that well-timed ECM, ECM burst, or bomb, especially lockbreaker or void, can be really annoying to enemy.
- WH residents tend to have much more ships than you could bring in in WH due to mass limits hampering you. On the other hand, if you collapse the hole you came from, and camp it, reinforcements or podded pilots have no way of getting in, as enemy does not know where the entrance leads to.
- two of the major differences between wormholes and K-space stargates are:
- traversal of wormholes within jump-back range
- the 5 minute wormhole jump timer
- the first allows people to run away, if they don't like what they see on the other side, regardless of bubbles, webs, etc.
- the second offers a way to prevent people from running away
- one tactic: Target is in system A, apparently probing for wormholes. System A is connected to System B via a wormhole. Put a cloaked HIC on the A-side of the wormhole. Have the fleet, including a fast tackler, on the B-side of the wormhole; a bubble on the B-side helps too. As soon as the target probes down the wormhole and jumps across, the HIC on the A-side decloaks and puts the bubble up; a fast tackler should jump from B to A. On jumping over into System B, the target will generally try to just jump back into System A rather than try to run the camp, because they are already within jump range of the wormhole. Of course, they will jump right into the middle of a HIC bubble, with the fast tackler putting a more mobile point on him. And, since they've just jumped from A to B, they will be unable to use the wormhole for nearly 5 minutes, effectively pinning them to the wormhole. This tactic even has the potential to catch covops, because ~30% of the time, the covops will emerge <2,000 meters from the WH and be unable to cloak, making it much easier for the fast tackler to land a point (although a good covops will realize they're less then 2km from the wormhole, and make sure their initial move is directly away so that they can engage cloak and navigate out of the bubble).
