2012-07-31

Three bad options

You always have options, but sometimes you only get to choose between bad ones.

Since we have a static C2, we can normally assume (almost) that empire is just 20 min scanning away. And often it's reached through a convenient highsec exit. Normally that is...

That day, I logged on pretty late, I was supposed to show up for a operation in a C6 in just one hour, and even if I was confident the FC for said operation would provide me with a target-system in empire to head for, I was running late. I needed to get out of Natalie (our home C4 /static C2) to pick up the ship I was going to use in Amarr.

Usually I don't care so much for the k-space static in our C2, but this time I just needed to get to Amarr.

For that, that day we had the worst possible static C2 you could imagine: static C5/Nullsec. For finding empire, that system would have been a obvious re-roll, but since I was alone in corp-chat, that would have taken some time.

I first checked the nullsec, sometimes it's really close to where you want to go, so with a little luck it would only be like 15-20 jumps from Amarr. Nope, no such luck, Omist, as far out into null you could possible get, some 53 jumps to empire. Sigh.

Ok, let's check the C5 then. Most C5s have other C5s as statics, so the C5 chains are almost as notorious as the C4 ones. I did not get my hope up for this and I had no time scanning out some endless C5 chain just to get out into Empire.

The C5 had a static C5. Double-sigh. I could at lest check is second C5, but the whole system was infested with Verge of collapse pilots, and they where using their static pretty much. I had definitely no time getting camped in.

So, with 45 min to go, my options was;
  1. Do the 50+ jumps to Amarr (can't use AP since it was through nullsec)
  2. Scan myself out through what might be a almost endless C5-chain, starting in AQUILAs home system
  3. Reroll our static and hope for a better one.
Not exactly the best options. But living in w-space, you need to play the hand that's been given, so I went for the exit. It was the only one I was sure I would make it in time. The other two options could potentially drag out enormously. I had to be very lucky to scan my way out from that C5, and rolling a new C2 would take time. And more scanning. And with my luck, I could just as well get a new C2 with static C5/null.

I almost made it in time, Amarr ended up another 20 jumps from the target system, so I arrived 15 min late.

Could have been worse.

2012-07-23

Ishtar pwnage

You know the Ishtar I was talking about in a previous post?

Ash alliance (no connection :) decided they wanted to evict AAA from a C6 and invited some other alliances to the party.

I brought the Ishtar to put my ISK where my mouth is.

We had some dreads, so there was no need to fight ECM and the single POS was pretty badly defended, so there was little use for close up dmg, incapping POS-defences. We did kill some POCOs thou - they have to do as a indication.

POCO 1
POCO 2
POCO 3

I guess the system was way to insignificant for AAA to even try to defend, so we did not see much action. If we had, I guess I would have been better of in a Proteus, Loki or Legion, but I'm confident the Ishtar would have had performed reasonably well even at WH-fighting.

If flown properly of course.

The tower.

Nuff' said.


2012-07-22

Invaders must die!

This is a story of a small POS.

It is, or rather was, totally without strategical value for R-NAT and Transmission Lost, and without any chance for juicy loot if you kill it.  Still, we spent almost 24h and 1B in ship-losses to see the explosion.

Crazy? Maybe. Fun? For sure!

It all started when we found a small, newly setup tower (no mods, shields at 53%) in Gloria, our static C2. I jumped out to highsec and at that exact time a hoarder landed on the WH. It obviously did not jump in since I was flying a Tengu and he saw me...

Now, this hoarder was from the same corp, some Potentially Irresponsible of the Northen Strike alliance, that had that small POS we found. Could it be this guy is the one that setting that POS up? After some quick investigations, it stood clear this was most likely some kind of stage-pos to take the system since there already where POSes belonging to other corps in that system.

This can't be! it's an invasion! Surly not any of our business, but hey, what do we care? Invaders must die!

We only had a few pilots on, but still decided that we should kill this tower, maybe it did not even have stront, and if so, it would be a quick affair.

We swiftly critted the HS, and started to work on the other WHs in the system. There was a lot of wormholes to handle, except from the static C3 and HS, we had our incomming C4, a C2 and Nullsec.

All except our home system got critted or closed to make it a bit safer for us to bash the POS. Remember that we only had like three or four guys online and could not keep system control the normal way.

While Magger and I  was critting the C3 WH, a covops suddenly appeared, but I failed to get info on it. Knowing where scouts come from by pairing them (by corp-belonging) to some POS that's been scouted earlier is very important. When you run ops with few pilots like we did here, you need to do a threat assessment on every corp who's scouts you see.

It was this I had in mind when I later decided to check that, now crit, C3 out. I figured, that if we had seen a scout at that WH, the inhabitants was worth checking out a bit closer.

I jumped into a thrasher, it's light so it would not close the critical static but still got the means to ruin any frigpilots day.

Well, I manage to close the WH with a bloody destroyer! What are the chances? Just my luck... Now we have to scan out and crit the new C3 - exactly what I wanted to avoid.

But no my friends, I was not stuck, the Thrasher have 8 high slots but only 7 gun-mounts, so I obviously have probes. And seriously, I think I'm going to start kicking people from corp that manage to get stuck with ships having utility highs and still don't fit a probe launcher.

Anyhow, I ask the guys still left in Gloria (our static C2, remember?) to find the new C3 while I start to make my what back. It looks like even if the WH-god of critical mass pulled my leg on that one,  I'm totally bro with the scanning-god, because first scan gives me a hit on what shows to be the static, an lowsec empire-exit. I'm out in 5 min, heading back towards Glorias HS. It's 17 jumps, 15 of those through lowsec - could have been worse.

In fact, it is worse. Back in Gloria one of our pilots in a cloaky T3, with the scaning subsystem, manages to be out-scanned by Magger, that's camping a bubbeled HS in a Dominix! There was some excuses made about our sigtracker not working and whatnot, but since this dude have not been even trying to help out in any of the scanning, his trial period is coming to an abrupt end. If you can't be trusted to do even basic scanning, then you are of little use to a WH-corp.

After securing the system and using only a few ships, we got the POS to 25% shields, but unfortunately it was stronted, we would have to wait 13h before it would get out of reinforced. We now had the choice of just going back and forgetting about the whole thing, or making arrangements and coming back to finish the tower off when it was ripe.

R-NAT decide to stay and see this through, this POS was going down! We checked who could be on when at the time for REO-exit, said good night and logged off.

In the morning, still T minus many hours, I log on and scout the system out. The sigs needs to be rescanned after downtime, so I do that. The highsec was new and needed critting, so we did that. Before this I had also sent a corp mail updating everybody on the situation and what plans we had. I remember that I explicitly said "one hour before it comes out of reinforced we will close the HS and crit the new one" knowing that you do not want to do operations with a old wormhole in system. When the time came, we broke this rule, and boy did we paid for it.

Finally, at the time for POS to come out of REO, we are getting set to kill it off. At this point we have 4 pilots on, the HS is critted and bubbled (should be safe, eh?) and we still have the connection to Natalie (our home system), even if it is pretty end of life by now. We also have a new incomming C5 in Natalie which we are currently checking out.

Suddenly our scout at the crit, bubbled HS calls that a neut Drake just jumped in and was burning out of the bubble. And because of I operate in a "when in doubt, go for it" mode, I call everybody to the HS. And of course the Drake is not alone, when are they ever?

We already have a Domi in the bubble, and I land a few seconds later with a Mega, right on top of the Drake. It goes down in a jiffy, like all drakes should, but now his friends are pouring in through that "secured" wormhole.

We obviously managed to lose almost everything we brought, and since I did not gave order to GTFO of the bubble, we end up in empire as well ;(

R-NAT - then unknown third party: 0 - 6

After the loss, we regrouped in Natalie and try to figure out who hit us and what gone wrong. The guys that found us was Enneagram Rocks, and describe themselves as a "highsec industrial corporation" - we are sceptical that that is still valid :) Anyhow, good job on that one!

After they leave we decide to still try to kill the POS. At this point we have a single Naga hitting it, just to make sure the shields don't recharge too much. I'm trying to get some more dps from Natalie, and like it was pre-ordered, Jimma logs on and comes to help out. But oh, no! The Natalie-Gloria WH is gone! We have no longer a convenient direct connection.

After a new Gloria opens up, we are pretty focused to just get Jimma and whoever else that want to come over. Jimma jumps into the new Gloria to discover a large mining-op going on, he reports several Hulks and a Orca not at a POS. They seems to know what they are doing thou, because as soon as Jimma jumped in, they pull back their minerals and ship into pvp ships.

They have a static HS that we want to use. To make our exit from Natalie safer (not having to worry about camps on the HS or scared miners trying to reroll wormholes) I convo one of the guys, explains who we are and what we want, and asks if we can just take a few ships to HS through their system. It's ok by them as long as we don't open their static C4.

Thanx for your co-operation, Jack Macca! Sometimes diplomacy is the easiest and quickest way to get things done.

While all this taking place back home in Natalie, I have Ashi on the WH to our target system in a Tengu, covering for Tashima that's alone bashing the pos, waiting for more dps.

It is then I realise that this highsec is actually just one jump from trade-hub, and that I could throw a torp Raven together real quick. It would do wonders against the small POS. I do so, just fitting the absolute basics, launchers, and dmg mods! I have no intension to ever shoot anything else except the POS with this thing, and it's going to be sold as soon as the POS is down.

We keep bashing the POS with what have become a Raven, Naga and a Drake. We don't have the HS bubbled, but it is on it's way to become crit, well beyond half mass after I used the Raven to reduce it.

This is when the POS owners show up! Earlier I have seen their scout check the HS out, so we know they at least know where it is. We don't know how many of their alliance that are actually in on this.

For a long time they only have one in local, but eventually they muster a Harbinger, a Mega and a Rifter.

They jump in and after some WH games I end up with Ashis really poorly fitted raven on the inside and the others out. I'm not to worried because the WH is not crit and I can always jump out, right?

All three jumps in and the WH is gone! I must have missed when it went crit, or they managed to close it with what they had. In any case, the Mega does quick work of the Raven.

R-NAT - Potentially Irresposonsible: 0 - 1

The status was now Drake with probes, Naga and pod on the inside together with their Mega, Harb and Rifter. Thats a fight we dont want, so we log the Naga off, and give Jimma in the scanning Drake the task of finding the new HS. As they put probes out at the same time, it becomes a race for the new highsec.

Jimma does a great job of onlining the rusty old probe launcher on his Drake and ejecting some T1 probes, beating the enemy Cheeta to pinning the new HS.

I  get my pod out, and goes to Jita to fit a new Raven and rush back towards the new HS. The control of the system are now back in the "invaders" hands, and we need to get it back.

By now, DethSilver have joined us with some DPS in the form of a Tornado and a scout in a quickly thrown together blackbird.

When we are ready, we log the ships in the system back on (Drake and Naga), fleet up and jump the ships we have in highsec in. A small fight at the WH follows, but we are quickly forcing the invaders to jump out. Hence, WH control is back where it belongs, in our hands!

Raven, Naga, Drake, Tornado and Blackbird vs Mega, Harb and Rifter is no contest, but we don't know what more they have coming so we decide to roll the highsec once again.

And from there on, we have enough DPS to kill the tower before they managed to get back and challenge us. Almost exactly five hours after coming out of reinforced, the small, 60M POS finally exploded.

During this, R-NAT never had more than three or four pilots on at the same time, and Potentially Irresposnible did not manage to bring any reinforcements from their alliance. Neither did we try to bring in a TL fleet to put the POS out of it's misery.

This stayed a battle over a strategically unimportant POS, fought by very few pilots, none of who lived in the system. This might potentially the smallest and least significant POS-kill/defence in the history of w-space! Well.. Maybe not, I'm sure there are quite a few Dominix and Geddon pilots out there that afk-soloed some small, undefended POSes.

A big thanks to everybody that at some point passed through this story, you're all important threads in the tapestry we call EVE.

2012-07-21

Close call

Sometimes you get away with things you thought you could not.

A few weeks ago, we had this incoming (or K162 as you pros call it) C5 to our home system. I had just logged on and as usual I jumped in to check it out. I quickly found it was a pretty active place. In fact, so active they outnumbered us by a factor of four. At least.

Nothing to do more than to check out what the inhabitants was going to do. They obviously knew about the WH, because they quickly got a small camp on it, including a bubble and interceptor that jumped through into our home and orbited the WH there.

None of theese things bothered me in my cloaky Loki at the time. That interceptor might be a problem if I was in need of running their camp, but I was not, so why bother?

Well, they started to jump a Orca through, so I soon had to decide if I wanted to get back home before they closed it or not. I was watching the WH from 150km away, and we had eyes on the other side, so I could at any time just warp to the WH and jump through.

If it was not for that interceptor...

Finally my scout on the home side announced:

"captor is gone. And they jumped the orca through! If you want to go for it do so now!"

"ok. Coming home" I replied as I initiated the short warp to the WH.

"wait! Wormhole is crit! They might close it when it jumps back!"

Oh, no, I'm not going to make it! As I decloak right in the middle of the gang and try to jump through I hear what I feared on TS: "too late, WH gone"

Shit! I quickly initiate warp to a celestial and by pure luck, and maybe because the campers was to startled to manage to lock me up, I get away!

Phew, that's a tad to close for comfort.

I drop probes, scan out a WH that happens to be a Highsec, warp there only to discover that the inhabitants moved their HIC and and camp there. But because it's a highsec and I'm interdiction nullified, I can warp strait to the WH and be home before supper anyway.

It was less then 30 min since I logged on, and I got into an adventure from the first minute.

2012-07-20

Ishtar: The forgotten one

Every time I want to go to a POS bash, I'm always in doubts about what ship to bring.

Thing is, I want to be useful. In the end, useful at a bash means bringing dps, you can't really get enough. The more dps the quicker and safer it will be. But I know from experience that there is a whole bunch of other kind of useful that needs to be carried out on a POS-bash. And I'm of course only talking about w-space here.

Basically, there are five tasks that needs to be done to kill a POS in w-space.
  1. Incapping mods (without dreads, this needs to be done first)
  2. Reinforcing the tower (that is, shooting it until shields are at 25%)
  3. Keeping wormhole/system control (knowing, at all times about the status of WHs)
  4. Guarding/fighting defenders (in trying to keep system-control, fighting over WHs can be expected)
  5. Killing the tower after it comes out of REO.

If you join a eviction/POS bash, you are going to be told to help doing one or several of this things. The wormhole/system control is something thats need to be upheld throughout the whole operation.

Now, unless you fly some specialist ship, like a heavy interdictor, a dedicated scout/scanner or logistics, you will either need a "POS-bashing ship" or a "pvp ship". A pos-basher is something with as high dps as possible @ 30km and enough tank for logis to keep you alive while incapping mods and the POS are still shooting at you. A pvp ship is something you are comfortable flying and fighting any eventual defenders with.

It's hard to combine theese two without compromising too much. Most people end up bringing a BS or Tier 3 BC for dps, and a second ship for pvp. Others borrow ships already in the target system.

In any case, having the right people in the right ships is a big part of how efficient the OP is going to be.

I often don't want the hassle of bringing several ships, but I still like to feel that I can contribute, no matter which of the above mentioned tasks I'm doing.

If I was to write a specification for the ship I would want, it would be something like this;
  • Not overly expensive, around 2-300M max.
  • Armor-based
  • Able to do at least 600dps @ 30km, and if possible much more at close range
  • Be AFK'able, ie, don't need constant reloading
  • Have reasonably low ammo/charge use, so you don't need to restock all the time
  • Have some tackle for WH guard duty
  • Have a good enough tank to have a chance of surviving close range fighting on WHs (high EHP)
  • Have a good enough tank to survive POS-defenses with logi-support (low sig res, high resists)
  • Have a probe launcher, preferably online
  • Have a way of dealing with small ships
  • Have a AB for reducing incoming dmg (especially good against mid/large POS guns)
  • Have a MWD for burning through bubbles (plenty of those at POS-bashes)
  • Have a cloak (for bio-breaks and comfy scanning)
  • Have a high scan-resolution for quick tackling

Wanted, but not directly needed;
  • Interdiction nullified
  • Cloaky warp
  • Remote ECCM (for helping guardians out while fighting POS ECM)
  • Remote sensor booster (for giving fast tacklers instalock on pods etc..)
  • Be ECM resilient (either with high sensor strength or with dps that's not dependant on locks)
  • Be a fast traveler (sometimes it's a race in empire to get to a new entry, getting into warp quickly is not totally unimportant)
  • Able to taking chances in lowsec (Fast align, cloak and/or MWD)
  • Able to enter C1 systems

It don't necessarily need to be doing all of this at the same time, some reconfiguration might be OK. Refitting is quick, having to grab another ship half across the universe is not.

Obviously there are no ship that fully satisfies all that I listed, not even if you are allowed to refit it for different jobs.

But I think the above spec is comming close to describing an Ishtar. That ship is terribly hard to fit if you want it to do everything at the same time, but if you allow refitting, it's incredibly versatile. Thanks to it's drones (AFK'able, lock independant) and the new drone dmg module, the dps output with sentries (+30km range) is pretty good.

It's also capable of hitting big things close range with blasters and heavy drones (quickly incapping POS mods), as well as having some tackle (guard duty) and hunting small ships with warriors.

It have a high-slot left over for a probe launcher, and in most configurations it should be possible to have it online (keeping track of new sigs, finding new statics etc..).

In fact, you could easily find three different fits for the Ishtar, making it preform very nicely in all the roles "incapping", "reinforcing" and "guarding/fighting". The ship almost equals a strategic cruiser in versatility, at least in it's offensive roles. The tank is of course, still just a T2 one, and depending on how heavy you go with dmg mods, it might be the weakest part.

I'm not going to go into specific fits. Dending on how you balance tank and dps, an Ishtar can do 650dps @ 35km while having decent buffer and great resists. If there no longer is any need to tank incoming dmg it can go full dmg and do over 1000dps close range for quick incapping of pos mods.

While in fighting-mode, it can be quite tanky, still do great dmg and tackle. Or it can fit a few projected ECCM to help guardians against ECM. Unlike laser-boats, most of it's own dps will not be lowered by it getting jammed.

Also, being a cruiser, it will never have any difficulties getting anywhere, traveling to, or through, C1s is not a problem. Doing many jumps in empire should be quick, a few lowsec-jumps doable.

I think the Ishtar is often overlooked. If you are going on a w-space POS bash, and happen to have good drone skills, have a look at it. You just might find it to be the most useful single ship you can bring.

And usefulness was what I was aiming for.

2012-07-18

Unlucky noobs

Lately it have happened quite a few times that we stumbled on noobs jumping in from HS. It have usually ended pretty badly for them. Sometimes they have lost their ship and got podded before their first minute in w-space have come to an end.

Imagine a 3 week old toon that decided she wanted to try and find some gravsites to mine and since she could not find any in highsec, she was going to try w-space. Now imagine the worst of luck when the first WH she happening to jump into is our static C2, where, also by pure chance, one of our cloaky proteus just made his way back from empire. 

- guys, there is a frig sitting at the HS.
- doing what?
- nothing.

At the time I was in our home system, just one system away. Since I know it's usually really hard to kill things at highsec wormholes, I quickly jumped into my new favourite ship, a dual sensor boosted arty-trasher.  Maybe I could alpha this.

Well, Djavo got the kill before by just uncloaking the Proteus, waiting out half a century of decloak timer and then simply pointing and shooting the poor noob. 

The ship exploded as I landed, so all I could do was go for the pod. 

We ended up chatting quite a bit to Breezzy (as this particular noob most likely wants to be called). She sent us a mail telling us that apparently some mistakes was made on her part and asking for advice on how to better herself. 

That kind of mail is the opposite of the usual "what the hell did you do that for? I have done nothing to you"-tear-mails you occasionally get. 

It was a nice change. 

2012-07-16

How we adapt

In R-NAT we try to fit our ships to be as much use for the small fleets we do as possible, and we try and learn from mistakes and experiences. EFT is nice and all, but it will not tell you if to go for a ECCM or a web on the BS you are fitting. Neither will it tell you what to do with that last high-slot.

This is an good example of how it works;

Last night we had another chance to tussle with Chained Reactions a bit.

After finding their system (a C2 with static Null/C5) from our static we scouted it out to see if there was any activity.

Nat > Gloria > CHAIN home

Activity there was, but very little. A lone Covetor was mining in the middle of the system. Well, theses guys are not exactly known for their vigilance, there's a big chance combat probes would work.

I'm flying a Rapier, so I quickly warped out of d-scan range, dropped probes, found the Covetor, warped there, called in Jimma in a ceptor to get a quick lock and possibly even catch the pod.

We both lands at the same time, and maybe, just maybe I'm a little to eager with the decloak while in warp, because after I have a scram on the Covetor, it warps away. Darn.

How many stabs can you fit on that thing? Well, 2 lowslots... so I guess we would have needed Jimmas point on there to keep him around. Or a faction scram. I guess that's why you fit them. Oh, well..

After this, a lot of their guys start loggin on and getting into battleships. We are starting to suspect they are going to close the incoming WH to Gloria, our static, the way we came.

We are two pilots ready but they have at least 4 - 5, with at least three battleships for closing. How should we do this to get a chance to kill some of them? We also got Danaja coming in from HS a few jumps out in a cloaky Tengu.

Three guys. Hmm.

Jimma have recently finished training for a Guardian, so he is pretty eager to try that out. He asks if we should do "the BS/Logi-thing".

Would that stand a chance against 3 closing battleships if we caught them jumping back into their system on a timer? If we got to the WH from Gloria when they jumped in, we could follow them back into their system and possibly get a point on the other side.

We would need eyes on the inside to time it though. We assume they have cloaky eyes on the outside of the WH, so we can't just warp there and wait for the closers to jump into us, they would simply not show.

In addition this will most likely become a cat and mouse game around a critical WH at some point, and I do not want to be stuck with a BS and a Guardian on the wrong side of a closed WH.

Danaja in the Tengu is the solution, I give order that he should jump into CHAINs system and keep eyes on the WH soon to be closed.

A Tengu is a nice addition to our dps, and he got probes to scan us out when the WH collapses, but it's not exactly the ultimate third ship to go with our BS/Guardian.

  • It's shield, so it would not benefit from the Guardian at all. If it gets close to armor, it would have to disengage.
  • It's tackle is a bit slow due to the decloak-timer, nothing serious, but it's not optimal, their BS will try and warp away as soon as they jump back. He would have to decloak to be ready for them when they return.
  • With the BS as the only tackle, and no webs, we might lose them simply because they pull range. A BS w/o a sensor-booster is definitively not the best tackler

A quick armor-tackler with webs and a bit of dps would be perfect. If we where flying T3s I guess that would have been a Legion, but for our current wallet, that's an AF.

I know Dana fly Enyos, but I don't want to lose the probes and eyes in their system, so I end up asking for his cloaky Tengu anyway.

We end up missing them because of the slow lock of the BS and Dana not being ready and/or decloaked on the right side when they jumped back, just as feared.

After they jumped back into their system they simply warped of. We missed our chance.

Now, what if our AFs had carried a off-lined probe launcher in that last high-slot? Then we would probably have had both point and web on one of the closers as well as a tiny bit more dps (from a ship that could stay on grid). In addition, we could have taken much more chances with the WH.

If you don't have a prober, a crit WH is just a risk to get your whole fleet stuck, with a prober (even a off-lined one) a critical WH suddenly becomes a chance to get the opposing fleet stuck with nowhere to go.

Not that a our Tengu could not have tackled, but a probe-launcher (on a fast armor tackler) would have changed the whole game for us. Since this failed engagement, there is a corp rule that AFs should always have a probe-launcher. That makes them the perfect complement for a BS/Logi duo when a cloaky tackle for one reason or another is not optimal.

This way we adjust our fit little by little, based on real situations. If we could not do something due to lack of a specific function or module in fleet then that specific module gets much higher priority and fits without it are reconsidered.

2012-07-13

The mighty Rattler

Normally I don't give the PVE part of w-space life much thought as of late. We did that when we lived with a static C6, and even if our way of making ISK was more focused on farming our static with quite large fleets doing single escalations than quad-escalating our home-syste like most larger w-space corps do now, I feel we know how to do that.

But it's different in our C4 and everyone needs ISK so lately I have played around with a solo-setup for doing C4 sites in our home system. And one that do not involve Tengus.

This is more a fun thing to do than anything else. As sad as it is, the Tengu is most likely the best plexer sub C5s, and R-NAT have a pretty good setup for doing C4s with three of them, so I wanted to come up with a alternative for doing it with just one, or possibly two ships.

That way, I could solo some sites when nobody else was around. We are a pretty small corp after all, and it's not always we have the pilots around for a Tengu-fleet.

My first try was to pair two BS and have them cap-bounce and RR each other. The idea was to generate enough cap with the bouncing that you would not have to bother about the neuts and be able to run a RR. There is a known Vargur-fit for this, but since I can only fly Vargur with one of my alts, I thought you could try it with any combo of battleships that would fit the basic requirements: high resists and enough utility high-slots to fit a cap transfer and a shield transfer. Or two...

For this to be a working duo, at least one of the ships needed a probe launcher. Plexing "blind" for new WHs is out of the question, and two battleships is easy to gank. I had no urge to lose PVE ships.

Marauders are interesting because of this, they have three high-slots left over, where the faction BS only have one or two. With a Marauder, you can have a bounce, a RR and still have room for a probe launcher. You always have the Dominix, but since I also wanted to be able to use this battleships as a replacement for the third Tengu in our normal plexing-fleets, it needed to be shield-based.

So, Vargur, Nightmare, Rattlesnake and Golem was selected as viable to build this upon. I think all those ships have potential to be great C4 plexers if you want an alternative to the ubiquitous Tengu.

Or, they would be, if it was not for the fact that you need to either throw more ISK at resists then I was willing to do, OR have two RR on each ship, leaving no room for a probe launcher.

The solution to that would be to involve a third pilot/alt, stick him into a booster and put the probe launcher on that, you would have almost twice the tank, and a scout to put on any WH you wanted to put ears on.

This would probably work, but are requiring three pilots and the initial goal was to solo or dual-box the sites. If you have three pilots you can just as well go with a Tengu-setup, and what fun is that? Thus, back to the drawing board.

The Rattler had gotten my attention. I had flown it before, but then doing C6s with logistics, and that was before the drone dmg mods...

The second try was to see if you could passive-tank a Rattlesnake enough to solo the sites with that, relying on sentries and a few cruise-missile launchers.

Well, you can, but you run into a few problems if you try;

  1. Since you need to stuff practically all of your lows with shield power relays, those nifty drone-dmg mods can't be used. This makes the, potetially awesome, drone dmg a lot less impressive.
  2. Doing a passive fit seriously impacts your cap recharge, and on top of that the sleepers neut. You need to come up with something totally passive, since you will be running more or less dry after contact with the first neuting sleeper BS. This is not a problem for your dmg obviously, since neither missiles nor drones need cap, but you might want to run active things like a TP or even a web to kill frigs quicker. I'm not talking about "a little low on cap" here, I'm talking totally frigging dry. Not-able-to-warp-between-sites-due-to-low-cap kind of dry. It's just no fun
  3. As a single ship in a site, they sleepers will go for your drones, and that will be a real pita. You could try to get them to shoot your amazing tank instead of your poor sentries by fitting some ECM, but chances are you will not have cap to run it...
All in all, it's doable, but it's not the easy ISK I was looking for. It takes ages and not having cap to run the tiniest candy is meh.

Ok, so pure soloing is off the table. Then as a third try, what about keeping the Rattler but fitting it for resists instead of passive tank, using the lows for drone dmg mods, the highs for cap bounce and shield-transfers and dual-box a Basilisk?

When you don't need to use more then one low (dmg control) and maybe 3 mid-slots for tank, you get a lot more options when it comes to dmg and utility-mods. And as a bonus, the double cap-transfer from the Basilisk makes your cap problems and neuting just a bad memory.

In my highs I put two shield transporters (to keep the basi alive), a single cap transfer (for bouncing the basi), a pair of drone range mods and the all important probe launcher.

Mids was tank (3 slots), a Targetpainter, two drone tracking links (>100km optimal with Bouncers and ~50km with Gardes) and a ECM. The ECM was to pull agro from my drones, but with all the RR going on I'm not sure it's even needed. After 4 plexes done, the sleepers have not even targeted my drones even once.

In low I put 3 drone dmg mods and a dmg control.

In most C4s, the sleepers will spawn either 80km or 50km away depending on which wave it is. They come to orbit at 20ish or 65km. Frigs rush in and orbit closer then 10km.

I ended up using 3 sets of drones; warriors for frigs, bouncers for the spawns that's more then 70km off, and Gardes for high dps "close range" (20-60km) cruisers and BS. With good skills and two tracking links, the sentries absolutely slaughters cruisers, and using the warriors against frigs the limiting factor will be lock time, they more or less instapop.

The tactic was to warp both ships in, orbit the Rattler close with the Basilisk, putting both cap transfers and two or three of the RR on it constantly, then switch back to the rattler establishing cap bounce and running everything from there. The basi needed little or no taking care of, I put a rep on it permanently and that is normally enough unless it gets both argo and becomes webbed, then it might need a second RR.

In the basilisk I used a full set of Hobgobblins, assisting the Rattlesnake. I then could use the painter to direct those drones to smaller stuff i wanted dead, like frigs. That part worked out really well, the 100dps you get from the hobgobs really makes killing frigs much faster, almost to the point where you don't have to use the rattlers warriors.

Unfortunately the drone control range comes from the owning ship and not the assisted one, so I could not send the Basilisks drones further then the normal drone range for that pilot/ship.

I have only done 4 sites with this setup, but it works very nice. In our magnetar C4, I complete them in somewhere between 12 and 15 minutes, which is quick enough for it to not get boring and makes a decent ISK/hour ratio.

There are obviously some work to be done pre-plexing closing and/or critting WHs and scanning down the system, but after that just scanning for new sigs now and then makes it reasonably safe.