open All Channels
seplocked Warfare & Tactics
blankseplocked Anatomy of a kill in w-space
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Daneel Trevize
Posted - 2010.09.21 08:25:00 - [1]

TL;DR: Usual tactics for killing a t3 with a covert ops in wormholes, where the first they know about it is the thing 5km away locking them.

N.B. I dualboxed the covops and Curse, corpie was in new Cynabal, our home is nicknamed SNA (it's a den of Vipers Wink)

Cov ops pilot goes in c3. Within the 30 seconds session timer (and I believe it's really all about not running out of the ~60seconds autocloak), dscan with: only ships & probe filter; ships & pos filter; drones/wrecks/cans filter, (all clear Rolling Eyes), rightclick orbit WH at 30km with fingers poisted on Fnumbers for MWD then cloak, basically hit together if >2km from WH, small pause between if you know you need to burn away to get the cloak on. Now BM the WH, give the Jnumber to the guys, know the static and effects, warp to celestials off of dscan once you're far enough not to reapproach/cross the hole while aligning. Hear back about activity.

Find POS on dscan, 3 haulers, 3 cap ships Neutral . Find POS planet, moon, note hauler not at POS. Smile Find hauler's nearest celestial on d, see hauler result become a bubble. Shocked Ok so he's moved on and left that but there's probably a WH that way.
3 piloted haulers, 3 empty cap ships in FF. BM tower, warp at 70km(<100km so you can view pilots, check guns/tanks & direction), move out to 150mk+ to do this if not already, or warp out if you dare leave grid to possibly save movement time. 2 haulers approached to POS mods, other 1 just flat from a warp/log in. That's ok, active pilot just bubbled a WH, could be planning for anoms. 30second Systemscan while waiting on grid with POS shows 1 anom within 4AU, no probes used.

A little time passes, decide to go to the planet off dscan and drop probes. Covops only jumped into c3 once combats were loaded, so just get max number launched (7 for me) asap while approaching POS planet, mwd-cloak-warp (ensure cloaked before warping back onto pos dscan), drag probes deep off any dscan from any possibly celestial, hit scan to actually move them there.

With eyes on POS, move probes at max 64AU range, get sig and anom count, only that 1 anom from before, only 5 sigs, not certain which is our size10 K162 back to SNA yet, easy to mix it up with the size 10 U210 static lowsec. Note ship sigs in exploration, and with careful dscan at 32AU, get the obvious large cap ship sigs and smaller hauler ones. Eliminate the caps for now. Smile

Manage to probe down SNA WH as it's off dscan from POS (just put 1 probe at 0.5au on the sig, scan, see the obvious result). Also get a different WH, leave POS grid to find it's the static lowsec, view info on it asap to see it's brand new yet to start cycle. ugh OK less good, the guy just bubbled something else and maybe didn't know it wasn't the static (don't know if U210s are also dynamic from c3s, could be 2 in here). Or they feel safe with that bubble on an incoming hole and know the old eol lowsec can't let in people via the new one until they scan it. ugh

Back to POS, hauler's moved down to ship hanger, good, still active, could well be ready to do that anom.
Wreathe becomes Loki, we have a winnner Twisted Evil , ensure probes are all well off dscan from anywhere again, but don't recall them. Didn't get a chance to view t3 to see subsystem choices and tank/guns.
Loki warps off. Not in the anomoly. Chase t3 out to a planet, then a moon, end up with him on dscan in space in front but nothing else there. It could be the old EOL lowsec, definately not where that fresh bubble was. Consider combat probing him while he seems to be sitting there, can't really be on the old EOL static but maybe hasn't noticed it's gone. Bring probes to 32AU, get ship sigs, eliminate all of these except the new one. Cool


Daneel Trevize
Posted - 2010.09.21 08:25:00 - [2]

Edited by: Daneel Trevize on 21/09/2010 08:32:53
His core probes appearing on dscan now, then he cloaks. Well we have the static, no need to race him just follow his probes so he doesn't hop out a different wh without hopefully seeing him flash on dscan (incase he hops out without recalling probes). If he does a grav/ladar/mag/radar site well we can get him in 1 or 2 scans with some more prior descanning and the collected intel.

SNA and low near each other, watch probes move frequently near centre of system, finally out by these WHs, ensure covops is on low WH grid but about 10-15km off (not decloaked or in likely range of being decloaked by him landing, but near enough to burn to and jump), and that backup in SNA is attentive to WH activation and of the usual plan to jump 1+ through asap and then approach hole to cover both sides should he go into SNA first. Idea
Probes narrow right down over both holes, then disappear. Probably recalled as he did the centre (currently off of dscan) already.
Loki appears by low, right next to covops. Shocked Don't decloak, let him jump, get others to jump in to c3 and not move ('hold cloak', use this time to remember to BM this side of the WH), our WH's about 1AU away so definately on dscan and we don't want to scare him into not coming back tonight. Loki's jumped into low, decloak covops turn on sensor booster activate scrambler and prep to lock a target, get others to warp to covops.
Protip: warp to such a person at 0, you need to cover the WH radius just like a gate/station, being at 0km can still put you 5-10km off them if they spawn the other side. Wink
Protip2: Next time, call for people to drop drones ASAP to block cloaking/aid decloaking. Embarassed

WH activates, Loki sees ships, waits session timer, realises polarity timer means they have to warp away, can't jump back, came in from lowsec too soon (within 4mins). Loki tries insta mwdcloaks Surprised, covops (I think) remembers to hit approach and MWD while fighting with Ctrl+click on overview to get lock off. Miss the lock Mad, he's cloaked, call for ships to move to decloak, drones, etc.
Get lucky decloak, shout, lock-approach-point-burn at Loki. Surprised Twisted Evil Get Curse in on the action.
Ensure covops is getting back within 5km jump range of WH once heavier tackle is certain. Jump covops out at last minute before shields shot off. Laughing
Kill Loki, loot, find covops unharrassed in lowsec as was almost certain to be the case, call gf in WH local, return home to SNA, post
to find value of loot, put BMs in can, log off. YARRRR!!

Daneel Trevize
Posted - 2010.09.21 08:26:00 - [3]

Edited by: Daneel Trevize on 21/09/2010 08:30:41
So, forum-goers, I ask you, how to improve or counter this approach?

Taggart Transdimensional
Virtue of Selfishness
Posted - 2010.09.21 09:10:00 - [4]

Good god, less emoticons please.

Printer Jam
Whine One One
Posted - 2010.09.21 09:45:00 - [5]

pretty standard stuff imo. congratulations you killed a loki.

keeping probes out of dscan range is a neat trick i haven't used. ill make note of it for next time.

Phrank Phish
Black Viper Nomads
Posted - 2010.09.21 11:27:00 - [6]

Originally by: Kushan
less emoticons please.

he edited the damn thing to put more in. you should hear him on vent, its disturbing.

if your looking for a counter to this then be advised that not everyone uses probes to hunt, so keeping scanner open and watching for decloaking / probes closing in wont allways help. allways treat combats as a last resort imo.

Daneel Trevize
Posted - 2010.09.21 11:56:00 - [7]

Edited by: Daneel Trevize on 21/09/2010 11:57:44
Thanks, Corpie. Razz

Yeah the best things I can come up with is keeping a probe out at all times in your own w-space and getting all new sigs to 100% before you consider jumping out any of them. The waiting in lowsec for 4 mins is probably just going to give hostiles time to scan the WH you used if they didn't have it already, and you'll still be facing 1+ decloaked on either side as soon as you jump back.

Yes this loki's nothing special, killed 4bils worth of t3s these past 5 days. But it seemed a good use of most tricks that some newer guys could learn from.

Just wondering if anyone else has any tips they'd like to share?

Silchius Ruin
Black Viper Nomads
Posted - 2010.09.22 14:58:00 - [8]

It's true people, sometimes we let him out of his box.
Me thinx we should have left him in this time, saying that though he tends to throw faeces when couped up for too long.

Mr Kidd
Posted - 2010.09.22 15:59:00 - [9]

Originally by: Daneel Trevize
Edited by: Daneel Trevize on 21/09/2010 08:30:41
So, forum-goers, I ask you, how to improve or counter this approach?

Grammar...use it!


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only