Category Archives: Wormholes
So this will be fun.
There’s 40-50 hostile Tech 3’s with support in warp to our position. Our fleet? A dozen sentry neuting Geddons and a mix of Guardians, a few Command Ships and some scattered misc. Total numbers for us? 40.
The wormhole is not ours. The tower we’re attacking is alien to us. The fleet we’re in? It’s full of people we’ve never flown with. Our target callers? ST and myself. What’s at stake? A good fight. The primary aim is to bait out the hostile fleet to judge a response on a secondary fleet for the next day to finish the tower. We’ve done that. Objective achieved.
The next objective is to survive.
But perhaps I start us in a bit late, for much has occurred prior. Let’s step back and take a deep breath.
The day begins well. Mick found a Proteus uncloaked in our C4a static and… shot it. It never shot back. This is followed by a small fleet materializing, so we form a counter fleet. After some scanning and probing, their fleet warps out the safespot we located – meaning we merely nail a Prophecy.
A few minutes later, myself and Mick get an EVE-Mail.
It’s from an NPC character and links to a Twitch TV stream of… the fleet we just tried to kill. It’s a feed of their buzzard from inside our home wormhole. They have all of us watchlisted and handily available on their screen. I test the delay on the stream by logging my alt back in and, lo and behold, their stream has no delay. Awesome.
We put it to the side for now, for something IMPORTANT has arisen. Our public channel is flaring and it’s Elroy Skimms looking for a chat. More specifically, he’s looking for assistance. His alliance is seiging a C2 Russian corp and the locals have batphoned in every Russian within 100 jumps. 40 Tech 3s have been confirmed entering the wormhole. The tower exits reinforced in an hour.
“We don’t plan to win” Elroy says, “we plan to get them to show their full force before we bring in our own allies tomorrows and are looking for volunteers to die with us”. Way to rally the troops, Elroy, but WHEN shall assist you.
Myself, Mick and ST grab our ships and make haste through high-sec to their location. On the way we acquire some extra pilots; House2Twist, Xenos and some mixed RvB pilots heed our call. Whilst 6 of the 10 or so RvB are in frigates, any help beats no help.
The alliance we’re assisting is Ocularis Inferno. They have about 20-25 pilots in the wormhole with various Armageddons and Guardians and are awaiting our fleet. A comms mishap means the primary mumble server is out and we swap to Teamspeak with no further issues.
The volunteer fleet is assembled in kspace and the Ocularis fleet in wspace, time to link up. We fleetwarp to the wormhole, jump in, and warp to the staging tower. ST is assigned as primary target caller, with myself as secondary.
The enemy have a couple of Logi out repping the tower but not much else. No time for a drink or a nap, it’s time to start. Leaving the safety of the forcefield behind, it’s out into hell we go. “To those about to die, we salute you” is the only comment in teamspeak as we enter warp.
Landing on an Osprey nails us a single kill but the remaining ships are back into their shields with no issues. The Battleships drop sentries and start shooting the tower.
A minute passes. Two.
“Watchlist spike” — “Multiple T3s incoming via wormhole. Ten. Twenty. Guardians. Falcons. Incoming” — “Estimate 50 ships”
The Russians have arrived. Sentry drones are recalled. Heavies and mediums are deployed in their stead. Capchain is ready. Comms are quiet, for once. The fleet awaits with bated breath.
My overview lights up as a dozen or so targets land 10km off our side, lead by a Loki, We engage the Loki as the overview continues to fill, taking it out quickly.
Enemy logi lands, as does a mass of T3s. Neuts and damps go onto the enemy logi, but jams and ecm drones go onto ours. The fight spirals into chaos as our battleships buckle under the enemy DPS, our 4 Logi thrown into disarray by the jams. Not to be deterred, our dps combines onto a Legion. I train my lasers on two hostile Falcons, but both warp in low structure. A third evades my fire and disrupts our Guardian chain yet again, losing us a couple more battleships. In retaliation, an Ishtar goes down next. Take that.
With our Geddons falling fast, our pressure on the hostile Guardians is greatly reduced and enemy repairs are getting hard to counter. ST does a great job swapping targets as he can, but our DPS is too little for the fleet we face. Nevertheless, a Proteus goes down followed by a Hurricane.
Unfortunately, we’re now in a heap of trouble.
We say thanks to our hosts and the other volunteers and limp back to our home wormhole chain.
Back in the chain, Firefly is trying to kill the Twitch streamer. The guy is still broadcasting. We know he’s in a cloaked buzzard 75km from our wormhle, but all our orbiting doesn’t decloak him. He’s also still active, manually evading us. Surely he’s figured out we’re watching his public stream?
We finally grab a pair of Interceptors and go for him. As we orbit the wormhole and play a game of “hot-cold”, he finally makes a fatal error. He warps to a bookmark called “c4”. There’s only one C4 wormhole, so we follow. We miss the distance, but I land 30km away according to his stream. Finally, he realises his folly and disables his stream.
Not before warping to the Sun at 100km. I land and decloak him easily.
Finally, a Fleet Hurricane appears on scan whilst we scout the chain some 30 minutes later. It’s the same guys as the Prophecy/Proteus/buzzard we’ve killed today.
He’s at the same goddamn safespot.
A massive thanks to those in Ocularis Inferno and the other volunteers who joined us. As always, my corpmates did extremely well and a thanks to them for the various kills throughout the night. I am also sad to report the Twitch stream now needs a password to access…
I’m also glad to report our recruitment drive is a success with several new recruits and many more trying to get in. We need a new recruit tower….
So in the absence of much else going on, here’s a small report from when we engaged Kill It With Fire the other day.
A C5 wormhole has opened into our wormhole, spewing some scouts from an unknown Corp into our home. Fortunately our resident elite frigate pilot Barrak is on the case. Turns out a Kill It With Fire Dramiel is buzzing about the wormhole so Barrak engages it in kind, netting a 260mill ISK Dramiel kill.
Kill do not appear happy with this arrangement and show up with a few ships on the wormhole – a couple T3s and some Battlecruisers. We know they’ll have backup and we don’t really want their fleet jumping us later so we drop our own fleet with an Archon in tow onto the wormhole, engaging them on the far side.
As expected, a couple of Guardians, some HACs and more T3s show up to engage. I throw my Absolution and Scorpion into the fight. Jamming out one Guardian, we quickly dispatch the other. The Archon has forgotten to lock my Absolution so I am forced to have him retreat in structure as I get primaried. We get a Proteus to low armour but he evades us by jumping and managing to evade on our side of the wormhole. My scorpion, still in the fight, is now scycling jams randomly on the remaining Guardian before swapping to two Oracles which have shown up. The remaining hostile ships start retreating whilst we hold onto the Deimos and remaining Guardian.
Bonus shot; My poor Absolution;
Welcome to Part 3 of my wormhole guide. This is probably going to be the longest one yet. Buckle up.
The skills shown in this guide will benefit you outside of wormhole space. Scanning & Direction Scan are key tools to normal EVE play – particularly for those who hunt others. Anomalies exist in all areas of space, but Wormhole Anomalies contain Sleepers, who practically deserve a guide of their own.
We’ll be covering Anomalies, the basics of Scanning and how to use D-Scan for hunting.
Anomalies are the source of a lot of people’s fun in w-space. Kill sleepers in them for ISK or kill players in them for explosions. There’s not much to them. Anomalies always show on a system scan, probes or no. This means any player can find them with ease. Anomalies in w-space are straight up sleeper sites. No hacking or mining, just waves of Sleepers. The difficulty depends on the class of wormhole – C1 anomalies are easy. C6 anomalies are really hard. There isn’t anything special about anomalies, but there are things to bear in mind.
- You do not get bounty or an ISK reward for anomalies. The ISK comes from the loot and salvage (which is worth billions in the higher end sites). You still need to get this loot out of w-space to sell it!
- Anomalies despawn either 3 days after being warped to for the first time, or after completion. Any uncompleted sleeper waves will respawn at next downtime.
- Anomaly (and site) spawns are random. You may find 5 more in your home wormhole one morning or none at all.
- Warping capital ships in in C5 and C6 sites cause additional Sleeper Battleships to spawn, massively increasing the risk but also the reward. Up to 4 extra waves spawn – one for the first 2 Carriers and one for the first 2 Dreadnaughts. These waves will kill capitals that are unprepared. These waves fully respawn at downtime if the site remains uncompleted.
- Sleeper AI will switch targets, It will neut. It will scram and web. It is dangerous.
- Sleepers will remote rep on occasion. Watch out for this!
This website lists all the anomaly (and site) types at the bottom of the page – good for examining what each site contains in terms of sleepers.
In w-space, there are technically 6 types of sites. We have Combat Anomalies and Ore sites which do not require probes. We then have Data, Relic, Gas and Unknown signatures.
- Combat Anomalies – The main anomalies for fighting sleepers. A few waves and a fair bit of salvage/loot
- Ore Sites (previously Gravimetric Sites) – Anomalies which contain large asteroid belts – sleepers may spawn in them, but usually in relatively small numbers
- Data Sites (previously Radar Sites) – Signatures with a fair number of sleepers and hacking sites – you need a Data Analyzer to hack the sites which can reveal more loot in addition to the sleeper loot
- Relic Sites (previously Magnetometric Sites) – Same as Data sites, just requires a Relic Analyzer instead.
- Gas Sites (previously Ladar Sites) – Sites with gas clouds, requiring a Gas Harvester module to “mine” them. Some sleeper spawns.
- Wormhole – It’s a wormhole. Duh.
Each site varies in terms of ore/hacking/sleepers depending on the class of wormhole and the actual site type. Again, this site is a good guide.
Scanning is the act of using Scan Probes to locate a target. The target can be a ship, NPC site, structure or drone. In addition, there’s two types of NPC sites – “Anomalies” and “Sites”. The main difference here is that Anomalies do not need scan probes to find. More on the differences between these later.
To access the scanning tool, you need to click this button on your display.
Alternatively, “Alt-D” is the default key combination. You should see something like this.
If you never train probe skills or launch probes, this will be all you ever see. The system scanner automatically shows all probably sites a 0% strength as well as all the anomalies in system, Remember I mentioned you don’t need probes to see anomalies? Any ship, with or without probes, can see a list which could look like this:
Any ship can get these results, so that’s important to bear in mind. As you can see, you can toggle off these 100% hits with “show anomalies” above the result window.
In order to scan anything else (such as a wormhole), we need scan probes. There’s two types of scan probes, with several types of probe launcher.
Core Probes – Can only be used to find Anomalies & Sites. Can scan between a distance of 0.25 AU and 32 AU. Can be fit in any Probe Launcher.
Combat Probes – Can be used to find Anomalies, Sites, Ships, Drones and Structures. Can scan between 0.50 AU and 64 AU. Needs an Expanded Probe Launcher.
In addition, there are “Sister” variants of each probe type. More expensive, the Sister variants provide a bigger scan bonus.
Core Probe Launcher – Needing 15 CPU, this launcher can only hold Core Probes.
Expanded Probe Launcher – Needing 220 CPU, this launcher can hold all types.
In addition, there are both Tech 2 and Sister variants of both launchers, providing a scan bonus.
To actually use probes, we need to train the relevant skills.
- 5% reduction to scan probe scan time per level
- Reduces maximum scan deviation by 5% per level.
- 5% increase to scan probe strength per level.
- Astrometric Acquisition — 5% reduction to scan probe scan time per level.
- Astrometric Pinpointing — Reduces maximum scan deviation by 5% per level.
- Astrometric Rangefinding — 5% increase to scan probe strength per level.
Finally, there are ships which confer bonuses to scanning (and have the high CPU to fit the Expanded Launcher).
There are Tech 1 Frigates which give a basic 5% bonus per frigate level to Scan Strength and there are Tech 2 Frigates which give 10% bonus to Scan Strength, as well as allowing you to fit the Covert Ops Cloak, allowing you to warp cloaked. There’s also Tech 3 Cruisers that can fit Scan Probe Launchers if they have the relevant subsystems.
Probing – launching probes and basic formations
Now, onto probing, Every ship can launch up to 8 probes at once. Simply clicking the probe launcher in space will launch all 8 into the default formation which looks like this.
These are the probes in the default system-wide configuration the game gives us. The bubbles are each probe and the central box with arrows lets us move them around.
This probe formation is good to do a system wide scan for ships or structures, but useless for pinpointing the actual signatures. Probes need at least 3 overlapping signals to get a 3d position of the target. The more the better. None of the probes overlap, meaning there is no way for us to get a good hit on the target. The larger the probe scan range, the less accurate the results. As such, probing is a case of locating a target then narrowing it down scan by scan. Let’s give it a try.
As I said, this formation is useless so I swap to the other default formation.
Okay, much better. All the probes now overlap. Now we can move the probes where we want to start our first scan. Remember untill you actually hit scan, the probes never move. They’re still around my ship!
The central box lets us move all 8 probes. Clicking and dragging the arrows moves it round the system as we desire. To resize the probes, we can click and drag on the edge of any probe’s bubble. The game will automatically move the other bubbles to compensate, keeping all the probes in the correct formation. That means that within this default formation, all the probes will stay overlapping regardless of how big or small I make the scan sizes!
To move the system map, left click to rotate your view and right click to pan. Zoom with mouse wheel. Double click on a probe in the list to center on it.
Probing the signatures
Okay, we have the probes where we want. Hitting scan moves the probes and starts the actual scan process. We need 100% on a target to warp to it. You want a general scan first to get the rough locations of signatures. Let’s give it a try!
That is a fair few signatures! Most are within 3 probes so we get a red dot as to the rough location. The circle is a signature within 2 probe ranges, so we can only get a 2d representation on where it is! However we still do not know what the signatures are – we must get a 25% hit to determine the signature type – Gas, Relic, Wormhole or Data.
We have one at 16.9% so let’s go for that. Clicking the signature result shows only it on the in-game map. Re-center your probes on the signature and reduce them a size before your next scan. The second scan gives us;
Ah, interesting. The other signatures are going berserk as we move away from them but the signature we want is now above 25%. We can see it is a Gas Site. If we were not interested in Gas sites, we could ignore it and move on. We want to find it though, so we best continue. It has also moved slightly as our results get more accurate. Move probes again and drop a size.
Better, but still not 100%. Best try again! Move probes, drop a size.
Bingo. We have it to 100%, revealing the exact site and letting us warp to it. We can now also bookmark it by right-clicking the result if we want to warp in later. If we want to keep scanning, we can right-click it to “ignore” it, and go back to step 1.
So to recap;
- Launch probes
- Setup initial formation. Beginners should absolutely use the second default formation! Heck, it works fine for advanced users too!
- Do initial scan. Pick a signature to focus on. Move probes closer to the signature and drop down a probe size.
- Scan again. Move closer to the signature and drop down a probe size
- Repeat till signature is found
These are the basics of moving probes. Time for some more advance tips;
- Holding shift brings up the move box for each individual probes, letting you maneuver probes into whatever formation you desire.
- Every site type has a “Sig Size” – the higher the size, the easier it is to scan. Sites go from 2.25 to 10.
- Wormhole Statics have a set size. Use this to get a good idea of the type of wormhole you are scanning – you can view these on the many wormhole websites like http://wormhol.es
- Inbound wormholes are always size 10 – the highest of all site sizes.
I am more than happy to answer specific queries about probing. Feel free to ask me.
Directional scan is a wormholer’s best friend. It can tell you if you’re being hunted. It can tell you where your prey is. It tells you where a POS is, what the defenses are and if it’s even online.
The D-Scan is in the probe window at the top, and looks like this.
It’s empty, but we have not scanned yet. There’s 4 important sections we need to know about first.
- The “Use Active Overview Settings” box adjusts your result window to show only what your overview would show. If this box is ticked, and you have your overview to filter out planets, then planets do not appear when scanning. Easy.
- Tracking – if you are not in the system map (i.e. you can see your ship) then your camera will pan in the direction of whatever you’ve selected in-game. This means if you click a station, your view will center on the station from your ship. This leads onto the next point
- Angle. From 5° to 360°. Basically only show what is in a certain angle of your camera. So if you have 360°, it will show everything within 360°. If you have 90°, it will show you everything within 90° of your camera direction. This means if you have a distant station selected and tracking (AKA it’s in the center of your view) and you set your d-scan to 5° it will pretty much just tell you what’s at or near the station. See how this can be useful?
- Range – the range of the scan in Kilometers. Range is limited to 2,147,483,647 km, or about 14.35 AU. Ties in well with the angle to determine threats.
We can scan roughly every 4-5 seconds. The scans are instant. The opportunities are endless. We can do a full range 360° scan to determine if there are towers in a wormhole, or ships in an anomaly. D-Scan can pick up probes too so you can even see if someone is scanning nearby. You can set your angle to 5° and point it at a planet to determine if there’s a Tower at a moon there. You can then warp to the planet and start point 5° at moons to find the tower. See why I love it?
Using d-scan is all practice. One thing to bear in mind is that you can d-scan from the system map. It still goes off where your camera is pointing in relation to your ship. So if you probe down a 100% signature in system map, like we did earlier…
The site is directly in front of me in the system map. It’s also within 14.35AU so if I use a 5° scan I can see exactly what is in that site. Nothing, so no ships, wrecks or probes. D-Scan will never show NPCs or NPC structures.
Pointing at a planet gives different results.
This time I’m 5° on a planet without overview filters on, so it shows me all the moons and planets in line with my scan. If there was a Tower there, I’d see the tower, all the tower modules and even if there was a Forcefield (which indicates the tower is online). As a direct result I would also see any decloaked ships at the tower. Useful, no?
So how does this help us hunt? Well I’ve already explained a few ways. It can tell us what decloaked ships are nearby, where the towers are and if they are in a site. But what if I want to d-scan before probing a site? Easy.
You can probe and d-scan at the same time. Say you’ve spotted a Tengu on d-scan when you jumped into a wormhole. You have determined he is in empty space using d-scan – you have him at 30° away from any planets or moons.
Using the knowledge of where he is on the system map (or roughly) you now have a good place to use your first probe scan. Further narrowing down using d-scan first means there’s less chance of having to probe multiple times, meaning a better chance of catching the git!
That’s all there is to it. The rest is practice and logical deduction. Ships + Wrecks mean they’re killing NPCs, for example. As always cloaked ships do NOT show on d-scan. Keep your wits about you.
So that’s it for now. I may add (and adjust) bits of this post so keep an eye out. If you have any suggestions as to extra bits to add, or you spot some incorrect information since this post was 50% done when it all got changed in Odyssey, please let me know in a comment or EVE-Mail me at tgl3.
Part 4 will include Combat, active hunting, Sieging and offensive rolling of wormholes. Basically what we’ve covered already, but the PvP aspects of it.
Back to the wormholing stuff. As luck would have it, it got a bit interesting again.
A lowsec inbound to home gives us nothing to shoot, so it’s down the chain we go! The C4 static leads to another C4, a C1 and a C3. Ooh. C1 is halved and leads to highsec. The C3 also has a highsec static. What about C4b? I jump in and spy a very odd sight on d-scan. A lot of wrecks, mostly cruiser and below. They’re all named pretty similar as well so it looks like a mass self-destruct in progress. This usually only happens in the event of a siege. I decide against launching probes in case of a hostile fleet watching the wormhole further and instead begin the task of pinning the wrecks down.
Surprise surprise, they’re at a POS.
As expected, it’s a siege.. of sorts. There’s no other ships on scan and these guys are reinforced. So they must be losing, right? Well it turns out that the wormhole belonged to SONS OF RAVANA and the corp in the tower had shot their POS not 12 hours before and appeared to have booted them out the wormhole. So why would the winner of the wormhole be self destructing and have a reinforced tower? It’s a curiosity to be sure.
But curiosity killed the cat so I am content to watch them for now, waiting for something shiny to warp to C4a where we have a HIC and cloaky Tengu waiting.
We wait some more.
A Falcon warps to 4a but is beyond our ability to catch so we stay cloaked. We wait even more.
Eventually we get bored and Mick goes off to scout the Lowsec in home, where he discovers a Raven Navy Issue, Raven and Augoror in an anomaly. Good joke Mick, now come back and camp so we can wait even more. But no, Mick is actually serious and we have a serious case of the dumb in the lowsec.
So we did what was natural and dropped a logi supported Bhaalgorn with support on them. They died with little help from us. All 3 fits were terrible but they apparently had the spare ISK to put 100mil bounty on Mick. I asked them for some for me since I dropped below a Billion ISK bounty but never got a reply. Sad.
Moving on, we returned home to find that a Drake had just left C4b and was running down the chain. A Typhoon and Hulk were right behind him, so we launched every ship we had into C4a to try to catch them. We missed the Drake and Typhoon but nabbed the Hulk and pod easily. They made no further movement from C4b all night.
So I went off to play DnD. Win win!
Settle down kids. It’s time for a story.
One of intrigue and mystery. Of explosions and loot. Of loss and heartbreak.
Sadly for myself, the intrigue is wondering how I couldn’t cloak. The mystery is where the opposing fleet came from. The explosions were my ship, the loot is my modules, the loss is my Offensive Subsystem skill and the heartbreak is losing my first ever T3 Cruiser.
So onto the story.
The evening began as usual. As luck would have it an inbound Class 5 wormhole connects us to our sister Class 4 wormhole, though Penny and co have long logged for the day. I make note to steal some modules (or corpses) from it, but Firefly has discovered quite the wormhole chain through our static C4. Whilst boring in of itself, C4a leads us to a C2 which contains no less than 5 connecting wormholes. A highsec, C2, C5, C2b and C3 litter the space of what must have previously been a quiet system. Of bigger note is the Brutix sat on that C5.
Firefly can’t exactly tackle the Brutix in a Cheetah so I launch my Proteus to see what I can catch. A glance at the Brutix’s killboard reveals a dabble or two in wormhole space so as usual I have reservations about this move. ST and Firefly follow me in an Astarte and Sacrilege to provide backup. It’s not long before I arrive on the C5 wormhole to find… nothing. So I jump.
The other side is clear but it’s also a Cataclysmic wormhole, meaning my local reps are greatly reduced but remote repairs are greatly increased instead. Not a good place for my active-tank Proteus to fight in, so I cloak up and watch the wormhole. On the other side, Fire and ST have seen an Omen Navy issue and Exequoror Navy issue land on the wormhole and have engaged.
Within seconds, they report their d-scan lighting up.
The battle commences on the far side and they push a badly damaged Omen Navy through to me. I engage it easily, but an Exequror has followed through and its’ repairs outmatch my DPS massively. Fire and ST are badly damaged too so we try to pull out. ST and Fire jump to the C5 with me but, obviously, their fleet followed and my Proteus is already half armour. We jump back to the C2.
ST is easily caught as we decloak. I’m 6,500 metres from any ship or wormhole. I can move and re-cloak!
“You cannot cloak as you are within 2000m of Combat Drone”
“You cannot cloak as you are targeted by someone”
Overheat MWD and Reps. Burn back to wormhole. MWD won’t cycle. Scrammed off wormhole. Webbed. Neuted. Jammed.