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.

2012-06-28

Chaos plexing

I think we have discovered a new way to plex.

It started when I wanted to try out a new fit for a battleship intended to be one part of a BS/Logi pair. I just wanted something to shoot, and since we have this things called anomalies in our C4, and the sleeper-things in those anomalies are known to put up a fight I thought I could just use that to try the ship, it's guns and the whole BS/Logi thing out.

I only needed a Basilisk. And of course poor foxxy got the task to keep my ass alive, who else? Her voice dripped with doubt when I explained that I "just wanted to shoot some sleepers, keep me alive pls, hang on, here we go, take squad warp".

- What friggin squad? it's just you and me!

Well, we became three before we stated because Alex, one of our new members joined in a Drake.

The battleship was a Tempest, that's not a bad plexer per se, but the fit might be a bit sub-optimal for pve. The most interesting thing to see was if the pest could keep the Basi alive with just a single large T2 shield transport.

Normally we are very organized, call targets, do not kill triggers before we want a new spawn, have twice the repping power needed, kill sleepers in a optimized order etc, etc.. Now I just warped in and started shooting, letting foxxy and Alex tend to themselves.

We spawned new waves before we where done with the old, we got out of range of each other, we ran out of cap, we put both the Basilisk and the Tempest in armor. It was total chaos! I had more fun then ever :) Tempest, Basilisk, Drake - what a gypsy, rag-tag fleet for a C4!

I think we learned a lot. At least we got a lot of things confirmed that we already knew theoretically.

  • The difference between sig-radius and speed matters hugely for the amount of dmg you take My Tempest probably took full damage from the sleepers, and the Basilisk had to run 3 of it's RR to keep me alive, while the Basilisk could be kept alive with one single RR. This is especially true since we are running a unbuffered Basilisk-fit, to a large degree relying on small sig and high speed.
  • The Basilisk only got into trouble if it got webbed. As long as it could keep its speed up, we had no problem keeping it alive. With this setup, you better kill the webbers quickly.
  • To do that effectively, three flights of light drones assisted to the Drake really helped. It's a super effective way not to lose out on dps. The Tempest don't have time to lock frigs, and the Logi don't want to bother directing drones. Assisting them to a fast locker is the way to go.
  • A flight of medium logi drones from the BS is not to be underestimated. Put on the Basilisk, they really work well.

This is really not news to any of us. What was surprising was how fun it was trying to beat sleepers with very few pilots and without throwing ISK and 'proper' ships at the problem. I wonder what the cheapest fleet that could do a C4 in under 20 min would look like?

And what's cool with this BS/Logi-thing is that it feels like when you have that, you could add almost any ship and it would work great.
  • Drake, to assist drones to and to add some dps - great!
  • Cloaky Tengu to help kill small stuff and patrol keeping us informed and safe - perfect!
  • Loki or Rapier to web a and paint small stuff so the Tempest can hit it better - nice!
  • RR-Tengu complementing RR of the Basilisk/BS and adding some dmg - super!
  • Slepnier to roam around killing cruisers and battleships or working as heavy tackler - groovy!

2012-06-27

Chained Reactions II

...messing with Chained Reactions, part two. (read part one here).

While chatting to foxxy, I warp to the POCO expecting to see some kind of bashing fleet assembling on it to finish the 5M of HP that it got left in armor and structure.

Well, there is someone shooting it.. Sort of.. A Daredevil !? Not exactly my first choice, but what do I know? Anyhow, since I'm there scouting in a Raiper with Ashi, I offer foxxy to come and kill the pesky frig. With my webs and some quick pointing I figured we could catch it if she warped strait to the POCO... While we talk about what to bring they start warping in some more conventional bashers to the site. A Raven, Drake and a Domi. I try and talk foxxy into going balls out in pure dps and see how many we could kill..

The idea would be foxxy in a Oracle from range and me pointing close up in a blaster Dominix. That would be close to 2k dps and fun as hell as long as it lasted.... Being her usual girlish hesitant self (I know, I know, you don't do pvp foxxy, just messing with ya!) by the time she found her way into the airlock of the Oracle, Chained Reactions had added a Tempest to the bash... Well, two against five might be a bit too much of a suicide for me to get a refund on the corp ships.. And foxxy needs to go to bed anyhow. Well, well..

After foxxy logged, I linger with Ashi keeping eyes on the fleet. Then suddenly, they all warp off! What the..? Everybody except the daredevil and the drake warps back to their POS, apparently going into deep hibernation, no ship-switches, no probes on scan, no orbiting, nothing, no activity.

The Drake is happily bashing away though.. What about I just warp that Domi in and go at it? See what they do? Hell, why not? It's only a BS. Said and done, I keep eyes on the POS with Ashi and do the 3 warps from Natalie to the POCO in the C2 with Tashi in a blaster Domi.

Since I assume that as soon as I land the daredevil will point me and the whole fleet will be warping back (can only hope they trickle in, and don't land at the same time) I point the Drake and pop warriors to give the daredevil something to think about.

Maybe the drones will drive him off, or even kill him.

Here we go! Point on the drake! If you warp to zero on a POCO you might bounce off a bit, and for a while i fear that my clumsy Domi will bounce out of range from the Drake, but it stopps at 10km. I approach and let the blasters rip. yihaaa! Take that, stupid drake.

But what do the daredevil do? It warps out!! Leaving its buddy drake to the mercy of my Neutron blasters. What a douchebag. hey, come back here! Your friend is having some shield-problems!

With the devil gone, I switch to Ogres and put everything on the Drake. It turns out its a full mindslot, passive tanked T2 fit... Don't matter, it goes down in a matter of 15-20 seconds. Pop!

http://tl-eve.com/kb/index.php/kill_detail/5895/

Convinced there are a fleet scrambling or even in warp by now, I get my drones back and head back to Natalie.

Switching to Ashi to check what's happening at the POS I see what they are up to. And that's... Absolutely nothing! Still no reaction. Ok. But, but.. You guys was bashing a POCO just 10 min ago, and now I just killed a Drake. What's up?

Ah... They obviously think that was just the first ship in our gank-fleet, and when we only managed to get one kill we opted not to warp the rest of the fleet in...

Hmmm, I wonder if I can play on that? Let's say I warp the Domi back and start bashing the POCO? Wouldn't that look like bait? Would they dare to come and kill me? I was pretty sure they had not found the 15 man strong LOST fleet yet, simply because there was none

This could be fun! I place Ashi on grid with the POS whe they all where hanging and headed back with Tashi. Warp to the POCO, lock it up (half armor), and start bashing away.

Time passes. No reaction. More time passes, still no reaction. Ok, so they don't dare to attack a lone Domi because it's obviously a trap, but should you not pop probes, get into bombers, cloaky T3s, frigs that can GTFO? Anything? Nope. While POS is still watching the rerun of the Eurovision Song Contest (Sweden rules!)

Wth! Don't tell me I have to finish this POCO for you? I don't have ammo for that! And where do I send the invoice? I'm starting to think the bad rep Chained reactions have, is actually deserved.

Well, nothing happens and I actually do trip back to Natalie to stock up on ammo. Void this time, enough wasting faction ammo on structures! 40 minutes after I warped in the first time, the POCO is no more.

http://tl-eve.com/kb/index.php/kill_detail/5900/

I shake my head and head for home. Then, all of a sudden a Hound pops up on scan, it's Jasmintar, the CEO, and one of the victims from the gassing accident a few hours ago. He is back from empire with a new clone (hehe) to check out what's happening with that POCO they where supposed to kill..

Nothing of interest happens after this, they find (?) the WH to Gloria, and start to close it with BS. I have both Ashi and Tashi out in Gloria by now. I'm trying to come up with a plan where I can kill one of them. They crit the WH and I warp Tashi to the WH. They now have two BS and broadsword (to close a crit WH).

I'm jumping back in through the crit WH with Ashi to have probes in their system if I was to have a chance to close the WH on them, trapping one of the closing BS out in Gloria leaving Tashi on the inside point blank range with the other closer and Jasmintar in a broadsword. BS + HIC vs. Superdominix. I take that anytime :)

Sadly they don't jump anything out, instead both of the BS warp off the WH and soon after the broadsword decloak on the inside and warp off too. All three log within a minute, leaving a crit WH and a surprised r-natter.

Ok, I guess that's it for tonight.

I head home to a goodnights sleep.

2012-06-26

Chained Reactions I

Oh man, this might be a long one... You better get some coffee!

It's the tale of the danger of AFK'ing while gassing, how big systems can be a chance to getting away with fun shenanigans, how to do solo kills while there are a whole enemy fleet doing nothing, the love for the blaster and the POCO bash that turned ninja.

It all started out when Tashi made his usual after work scouting trip of our "pipe". Today it was Natalie - Gloria - C2a - C5a. Natalie being our home and Gloria our static C2. The idea to name systems like this is a ancient KAIRS tradition. They are strange like that :)

In the C2a I found interesting things... A HUGE system so the WH to Glo was out of scan range from their main POSes. Living in here was a corp from the notorious Chained Reactions (known from the blockbuster "Hammerfall" staring Talocan and LOST) and another corp from an alliance called StoneGuard.

As usual I checked the corps out (using Dotlan) this time I found that CHAIN and StoneGuard together with a -A- dude, had lost tree tengus in this very system just a few days ago. OK, they are not invading each other then, good to know.

However, they are cleaning up some previous occupants mess, a POCO from another alliance was in reinforced and due to come out in 5h. Things coming out or REO almost always is a chance to get a fight. Have you spent a few hours shooting something just to get it into REO, you usually want to finish the job.

OK, mental note of REO coming out later that night.

So, what's more then? This time I had only made empty tabs of the systems in sigtracker, NOT scanning the systems out fully, only trying to quickly find the WH as discreet as possible. We had the routes but not complete list of sigs. I found the POSes (always do, I find that it's terribly conviniant to be able to quickly check what ships aren't at a POS by just warping to it) but few ships was active.

Later when I returned to the C2a to see it there was any action, I saw some traffic of what looked like gassers (ferox, canes, ittys) going to somewhere in the system and then disappearing of d-scan. At this time I had not yet pinned the C5a, so I thought this was my chance to do so with the lot of them gassing in (I assumed) the next door system.

Ok, drop probes, quickly pin the C5 and then warp strait there, jump in and....
A pulsar! I got visions of losing my Proteus to a noob in a passive drake with T1 guns... Must remember not to fight stuff in here.

The C5 had a empty russian POS and no plexes whatsoever. But more interestingly, it had a whole fleet of gassers happily sucking the riches of some cloud somewhere in the center of the system. After a bit of warping around I realized they where actually in two different sites.

Hmm, should I risk dropping combats? I decided to do something new, as I knew approximately where they where, I was to warp out of d-scan from them and then drop normal probes and quickly pin the Ladars. Scanning for their gas might be easier than scanning for them. Sisters core is also much less threathening than combats.

After I pinned the Ladars, and warped to a 100, I found that the fleet had gone (possibly they saw my probes) but in the second site a single -A- dude in a cane was sitting still, apparently AFK. Or baiting? Did they see my probes, warped back home to switch into 5 cloakies and now they where just waiting around that cane for me to decloak and try and kill him? Paranoia is the worst enemy of your bravery.

This guys was like 5 or 6 in total, no way they run and hide just for some probes? In fact, I was so sure of a bait I was not to risk the Proteus (pulsar, remember?), instead I was to get a warpin on the AFK/bait cane, go back to Natalie and get that groovy little shield 1k dps Thorax that Magger brought in the other day. Warping strait back and hoping the gasser was still there. If I trigger a trap, I would get a fight and just needed to buy a new ship for Magger.

But before I could get close enough, he warped out. Darn!

By now, Dana and Talaq had joined fleet and was heading towards the C5 in cloaky Tengus. Suited me fine, since I wanted to get info about any potential gank fleet waiting on the C5 hole in C2. But no such fleet existed. instead, two of the gassing canes returned to one of the sites and I could get a nice 200km spot for us all to warp from. Primary points was delegated and we all warped. Decloaking mid warp enables you to lock as soon as you land, bleeding of the decloak timer during warp.

The Canes went down pretty slow, but with decent shield resists as they had and the bonus to shield amount from the pulsar, we had a few HP to chew through...

http://tl-eve.com/kb/index.php/kill_detail/5866/ and
http://tl-eve.com/kb/index.php/kill_detail/5864/

Normally, you never get the Pods, but this guys was, well, not there. AFK gasses ftw! The pods stayed on grid and we could pop them too... One of the guys was the CEO of the Chained Reactions corp, and boosted a pretty nice set of implants worth half a billion.

http://tl-eve.com/kb/index.php/kill_detail/5865/ and
http://tl-eve.com/kb/index.php/kill_detail/5863/

The drop was around 40M and at least it covered the cost of ammo wasted on theese bears

We all went back home to the loving arms of Natalie and most logged for the night. But not Tashi... Oh nooo.. The POCO! The POCO was about to come out of reinforced, and while waiting for that I got some housekeeping chores done, bringing the loot to empire to sell. Paying my teammates. Getting that Capital Armor repair skills I needed. Etc..

Just when I was back in the C2 to see what kind of fleet they where brining to kill the POCO, foxxy logged on. I had wished to have at least three pilots on to go and fight the POCO fleet, but what can you do? (KAIRS was too sleepy and too far away to come and join, it was Friday after all).

To be continued...

2012-06-22

Trying our BS/logi setup part II - the anticlimax.

Another night, another fight. One of this days we are going to start something right, I know it!

Tashi took a spin in our very short pipe Glo - C2a. In C2a, I saw Drake x 3, Onyx, Brutix, Tengu on scan. Can you say "camp" any louder than that? The C2 had a static HS as well as a static C3, so I just assumed this guys was either from C3 or camping the HS.

A few minutes after I jumped in and recloaked in my Proteus, the Brutix warped to the Gloria WH and jumped in to check it out.

After some pretty unnecessary discussions about how to refit a BS Talaq never flown before, we settled for sticking to what we used before. Dominix/Guardian/Proteus. At this time Selene had joined in his Pilgrim (also armor, so we actually had a nice little fleet there).

After having camped the Gloria WH with the Onyx for a minute or two they warped that back and stayed with only the Brutix. From Gloria a Tengu jumped in to drop probes.

I had Foxxy and Talaq warp the Guardian/Dominix to the C2a WH, so they where hanging at the other side. I told them that I was going to decloak my Proteus, to see what I could do to the Brutix and then if they got me low into armor, jump to the Guardian and BS and see if they would follow. If they then jumped back, we could follow with all three ships, and they would be on a timer.

Sitrep:
Them: Brutix and Cloaky Tengu on one side together with our still cloaked Proteus and Pilgrim. A Onyx and up to three Drakes in system.
Us: Dominix/Guardian pair on the other side of the WH. Big chance that the Tengu where their only scout, and if so, they might not know what we just warped to the WH. We might got really lucky there...

I decloak and point, web and start hitting the Brutix. He is shield-buffer, and doing quite a bit of dmg. The Tengu immediately decloakes to help his Brutix buddy kill this Proteus that had suddenly appeared.

Selene asks if he can decloak and go after the Tengu, and for some reason I stray from the original plan to keep him on their side, cloaked, as an surprise and eyes on the WH if Tashi needed to save the proteus by jumping into the loving, repping arms of foxxys guardian and talaqs Dominix. I say go for it, and Selene runs after the Tengu.

Why it was a good idea to show them the Recon, and to split the small dmg we had between the Brutix and Tengu, I don't know, it's simply a brainfart on my part.

By now the Onyx, a Drake and a Manticore have joined them, and since they are doing nice dmg, the Proteus is forced to jump to be repped. who would follow? None, of course! Instead they turn their attention to the Pilgrim which is no match for the Tengu/Drake/Manticore. While trying to get a tackle on the Tengu, Selene have come 30km from the WH, and before we realize he can't jump he is going down.

We decide to call it a gf, and warp back to Natalie, our home system.

We did a lot of things both right and wrong in this encounter.

What went right
  • Getting a fleet together that cohesive (Domi, Guardian, Proteus, Pilgrim have to be considered a pretty strong little group)
  • Getting Dps and neuts on both sides of the WH with the enemy in between (but not knowing they are) is as good start can be asked for
  • All pilots had previous experience in their respective ships, three of them as part of the same setup before

What went wrong
  • Showing our hand with the cloaky neuts that early was a big mistake. Cloakies should be decloaked as a nasty surprise mid-fight, not paraded as easy kills in the first seconds of a fight.
  • Having a Proteus hitting a blaster boat and a neuter trying to get tackle on a Tengu is just wrong. Failing to set the neuts on the Brutix, focusing fire, neuts and tracking disruption is just stupid.
  • Not being super-clear about the plans with the logi; where we going to jump that in when needed so the Proteus and Pilgrim could be safe attacking twice their numbers and three times their dps? Or was the idea that we could jump if we needed?
  • Instead of getting a timer on the Proteus by jumping that (hoping they would follow) and back we probably should have made the opposite - kept the Prot/Pilgrim on their side and jumped BS/Guardian into their camp.
  • if we had done that, they would had been forced to fight us all at once, and if (when!) they been forced to jump back, the Proteus could have jumped with them and pointed.
  • With a stronger fleet, and the surprise on our side, we should def. been more aggressive engaging them on their side.

2012-06-21

...into the darkness


One goes step by step, step by step into the darkness. The movement itself is the only truth.

Jimmacamus Diem quoting "The Magician" an ancient movie from distant Earth.

It's beautiful. And fitting for wormholes.




This is what we do.


















2012-06-20

It's not fair

Sometimes you manage to mess with somebody's operations so successfully you almost feel bad for them. Almost.

Ok, I admit it. I care for carebears. They are just trying and do their thing, right?

This time I had scouted out a C4 with two indy POS'es and a ton of expensive ships floating around: Carriers, Rorqual, Bhaalgorn (a bit strange in a Pulsar, but hey).

I figured that if I stayed I could harass this guys some. It was obvious that they rarely left their system, mostly doing their own grav and ladar-sites.

Anyhow. I log on my cloaky Proteus in their system, and since I already have scanned out all their sites I can just warp in on them doing their thing. Today they had a brand new Vital (one of the better ones) ladar site that they apparently wanted to suck on some.

I warped in at range and found a Cane sitting away from the gas. Just hanging there. I could see that he was not gassing-fit, but had some proper guns on there. Was he bait?

Then it hit me, he is just waiting for the sleepers! The site is so new they have not spawned yet.

After the sleepers spawned, I let him play with them for a while, and then I joined.

After killing the Cane, I killed the remaining sleepers and looted them. Gotta pay for the ammo somehow, right?

Next day, 5 min before downtime I found them sucking on the same very site. Half of the gas was gone, so now they worked on the second part.

Just a few minutes after I warped in, watching them, the cloud popped, and they where done. Both gassers warped out. But since they had the gas in two cans they needed to get that home to base somehow, I expected them to come back in haulers.

I warped in to one of the cans, still cloaked.

One of them came back, and by Murphys law, it was the guy from yesterday. He warped in to the first can, picked up the gas and since it was in warping-distance from the second, he initiated the short warp down to the second can, and cloaky lil me...

I decloaked in his mid-warp to let the lock-delay bleed away, and had a point on him half a second after he landed. He must have seen me all the way in warp, not able to do a thing about it.

Sometimes, Eve is just not fair.

2012-06-19

Battleship/Logi-pairs - part I

We have started to experiment with running a single logi (Basilisk/Guardian) in pair with a battleship that's setup especially to care for that logi.

That sounds way more complicated than it is - we simply slap a energy transfer on the BS and make sure we have some way of repairing the logi, if needed. It can be a RR on the BS, but it can also be a set of heavy logi drones - since the logi need to stay close to the BS for energy-bouncing reasons anyway, both RR and drones should be working.

Why a cap-bouncing logistics then? Why not a Scimi or a Oneiros and you would not have those problems.

Yes, true, but;
  • we tend to have more Guardian pilots then Oneiros ones
  • when joining alliance fleets, Guardians is the most wanted
  • we have much experience with Basilisks, the number of hours our pilots spent flying Basis is pretty high
  • the ability to redirect cap in fleet is hard to not get excited about, for example, if you have that capability, you can fit your neuters in a whole different way
  • if (when) a fleet grows, we rather have 2 Guardians/Basilisks then two Oneiros/Scimitars, or one of each. Adding a second logi without the need for somebody to switch ships is a very nice feature
  • even without logistics, such a battleship is a good compliment to any lone cloaky Tengu or Proteus that complains over not being able to break the tank of some plexing Nighthawk :)

To be honest, this have more to do with how to create a cool fleet with extremely few pilots (2-4) then what would actually be the optimal to bring. With just 3 guys, having 3 standard gank-fit BCs would most probably be the best and easiest.

But what's the fun in that?

I rather want us to start thinking in terms of "the ship I bring add some kind of synergy to the fleet" instead of "how to optimally way to fit this ship for a one vs one".

When we grow and our fleets gets bigger we will reap the benefits of this thinking, I'm sure.

2012-06-17

Recruitment headaches

R-NAT is recruiting.

It's a bloody hassle. How you conduct recruitment for WH-corps is a whole skill in its own right. You need to have a system; you don't want to spend too much time on each recruit because your recruiters only have so much time. On the other hand you don't want get all the scum in.

You know.. Thieves, inactive alts, folks only interested in making ISK, spies, etc..

It don't exactly help that our alliance are starting to get big either, now we also need to start filtering for spies... Sigh.

What I learnt from SPLU about recruits was that you could never really say in advance who was going to work out great and who would not. You needed to fly with them for a bit to really be able to answer the question if they where going to be part of the team or not.

Here's the question: Do you spend a lot of time per recruit doing extensive background checks, interviews etc, or do you get as many in as possible and set up a filtering system that works after they joined, making sure all the unwanted are kicked?

That is, should the funnel be wide at the entry (anyone can join) or at the exit (restrictive accepting applications, but low risk you 'fail' the trial period).

R-NAT is pretty well setup for the latter, to get tons of prospects into the corp, have a strict trial period and only keep the best. We have very little in terms of expensive ships, so there is almost nothing worth stealing. On top of this, you don't really get access to anything as a prospect anyhow.

We don't do recruitment like that though. We spend a lot of time on each recruit, doing API and background checks, talking, and letting them wait in pub, etc..

This might filter away some bad apples, but it also puts a lot of strain on the recruiters, and it's bound to also stop some pilots that would actually develop just fine if given a chance.

Pros and cons for switching to a "wide funnel entry" approach (pros first):

  • You would get a lot more applicants, making the number of pilots listed rise quickly
  • The time spent per prospect would be much lower, making initial recruitment more effective
  • A wider range of pilots would be able to test us out, preconceived notions would not stop good recruits
  • You could argue that trying to value someone before they got to show what they can do as a prospect in corp is a impossible task

There's a fair bit of cons too:

  • There would have to be a very strict trial system, during which a prospect would be evaluated.
  • There would be no problem putting a spy in the corp
  • We would have to be ready to kick a lot of prospects that's inactive or just don't feel right.
  • Thieves would be common thing, ships would be stolen from other recruits, making it hard to trust and promote anyone that was prospect when a theft occurs.
For a big funnel approach to work, I think you need to set up very clear rules about what's unacceptable from prospects. If the requirements to become a prospect are low, the trial must be hard. Hard and clear.

I'm not really responsible for recruitment in R-NAT, but since we are a small corp it affects everybody. Therefore, the way we do it is of concern to me indirectly.

In fact, recruitment for small corps that want to grow is a issue for every pilot in that corporation.

 

2012-06-16

Bait plexing is best plexing!

Sometimes it's fun to read stuff like old after action reports to notice how you (hopefully!) evolved as a corp and team.

Not long after we taken over R-NAT and moved into the system, we discovered, sort of by accident, the joys of what we now simply call "bait-plexing".

Bait plexing is R-NATs team-version of the classical bait-drake "plexing" in some C2. It is simply us setting up a fleet that would be a bit extra hard to take if you wanted to gank it. It's pvp ships that are kiling sleepers in wait for something real to shoot at. Sometimes we have additional ships standing by, sometimes we just keep a bit extra watch. If anyone jumps a fleet like this they might kill us alright, but it will be a fight, not a gank, and that's often enough. No matter the outcome we get a fight, and that's the only thing that matters.

Since it was early decided that we would basically fit for pvp no matter what we was doing, we quickly ended up doing plexing in cheap drakes with points etc.. This is from a AAR posted after such a fleet got ganked. You can say this is the birth of our ideas of bait-plexing.

Its all about this gank/fight.

Last night we set out to clear some sleeper sites in our home, Natalie. We decided to go with the drakes and two basilisks this time.

Ashi, Deth, Qumar and Jimma ended up in drakes and Magger took one Basilisk. Qumar dual boxed the other Basilisk.

We warp to the first site, the sleepers melt (thank you magnetar!) and everything is fine. Then someone asks if we are scanning for new sigs... Since the corp-fit for the drake includes a probe launcher, I could pop a probe and do a quick scan of the system. And sure enough, there was a unknown sig!

I had hardly time to start pinning it down before the first ships, two canes, landed on us. Well, "there you go" I thought, knowing the feeling all to well when you are about to lose a lot of expensive ships... But this was different, this was not some 10 billion ISK fleet with faction gear coming out its ass. Now the stakes was much smaller, and we where actually pvp-fit.

A second after the canes had landed, a Scorpion, a Tengu and a Abaddon follows. I know that Qumar (which is the FC) are dual boxing, so I start calling targets.

-Scorp is primary! Get your drones on him before he jams you!

The scorpion melts quickly. In an attempt to get rid of some of their dps, I call the two Canes as soon as I see the Scorp go poof. They dies reasonably fast too, but now Magger is in trouble! They correctly realized that they could not stay in the site together with both us AND the sleepers (who have a real nack for scramming the one that wants to get out and switching to the one thats in structure) so they started with our logis, primary was Magger.

For one reason or another, Maggers Basilisk can't take the onslaught, so it goes pop. without a partner a Basilisk is just scrap-metal waiting to happen, so Qumar loses his basi shortly thereafter.

However, while the opposing fleet have been trying to kill our logis, we have made short work of them, killing their Scorp, the two canes and got halfway through the Tengu. After getting rid of our support, they turned the remaining guns on Jimmas Drake, and managed to kill it before we got both the Tengu and the Abaddon killed.

When their last ship, the Abaddon, vaporizes we have lost two logis and a drake... I order a warp out, but find myself in the focus of some sleeper-love. Some very unwanted sleeper love. They have me scrammed and I'm going into structure and pops. Drake number two lost.

All in all it was a good fight and we had fun. In fact this guys was game for some more and we kept trading some blows and ships with them after we killed their gank-fleet in the site. But I leave that for somebody else to tell about.

So, is there anything we can learn from this? Sure, here are just some;
I'm rusty about general, age-old SPLU wisdom in general, starting to plex with unknown sigs in system is asking for it... On the other hand provided it us with a awesome fight, so maybe is "blind plexing" what we always should do :)
dual boxing was necessary this time to get going at all, but I don't like it and it's not working in pvp. I thought I heard Qumar say something about not being 100% sure he had all reps on Magger when he died, and I'm not saying duel boxing was the cause for that, but it most likely had an impact.

I can only hope the Basilisks was moving... None of them had a AB, so they where not moving very fast. If they where orbiting close, that's another mistake. If you can keep them at range, you should do so. I can almost promise that things had been very different if the basilisks had been orbiting with AB at 30-40km range.

Missiles rock in a magnetar, you get all the dmg bonus, but don't have to worry about the tracking decrease.

Since this, we have refined both the Basilisk fit and the Drakes, so if this was to happen again I can almost guarantee a total victory for us. Especially since we started to understand how to fly them now.

2012-06-15

Times of trial and tribulation

This is some notes from a few days during which Exhale and TL tangled (again) in a C2 with a static C4/HS (again). This time it was SEXCOs home system, a.k.a Vega

For an alliance, when everything goes well and your only "problem" is how to integrate new corporations into the community and how to find the elusive and hard-to-define "good fight", it's all hunky dory.

It's when facing a real threat, or serious situation that the workings and mentality of the alliance-design gets tested.

Transmission Lost might have entered such a period last night.

Jun 14 12:58


After having podded TunaKross, a CEO in Exhale, one of the corporations in TL found themselves in the focus of an invasion-force.

SEXCO is very recent inhabitants of their new home, a C2 with static C4/HS, and probably totally random, Exhale found it through the C4. It was when they started to use the HS for some logistics that something went wrong, and Tuna ended up in a HIC bubble and got sent back to Empire.

We don't know if this was the igniting factor and Exhale just thought they could teach us a lesson by turning a accident into a invasion. It might have been planed, but judging on what ships they brought and how they behaved the first hours, it looked more like a spur of the moment kinda' thing.

Anyhow.

We quickly lost control over Vega and large number of POCOs plus a newly (and badly) setup medium tower got reinforced.

TL scrambled and focused on getting some people into the system, while watching what Exhale was going to do. We did not really know how serious they where, but when a large POS went up and ECM started anchoring we knew they was not just there to reinforce some POCO's.

"Shit just got real" as someone said.

Since the tower reinforced was only stronted for a few hours, it got popped 6h after Exhale first showed in Vega.

We had a a few guys popped while getting the new HS for the forces waiting in Empire. Many just headed towards Vega in what they was flying at that time, but we knew that getting scouts and scanners into Vega could show crucial.

We had a sizeable fleet up, but could not get to the new HS in time due to Exhales proficiency at rolling, and critting the static HS. They should be good at it, after all, it's what they suppose to be doing for a living.

We also noticed this was not Exhale working on their own, plenty pilots from Surely You're Joking [HAHA] alliance was spotted together with the Exhale camp. Obviously they wanted numbers on their side as well as time-zone coverage.

At one time they broadcasted the new high sec and said it was still fresh, saying they wanted a epic fight. By then, we counted 40+ at the WH with more in their POS. It was decided not to take a fight on their terms, and our fleet stood down.

June 15 01:22


I just got back from the battlefield.
Exhale dropped their WH-control and TL got a chance to retake it. We did not miss that opportunity.

At 17:30 the HS wormhole collapsed and at the same time the enemy fleet in the bubbled POS made their move.

TL managed to get on top of them and a fight ensued. TL killed seven ships, and lost two before Exhale withdraw back into the shields.

I think we can call it a win for TL.

After that fight a bit of cat and mouse game was had, but very little of interest happened. TL kept WH control. Exhale huddled in the POS.

A funny thing that expired much later was a K162 opening up and a scout from Surly You're Joking jumped in. It must have been a total fluke, because I don't think HAHA is that dedicated to help Exhale so they try and roll a C2 :)

In any case, we had that WH scanned down and warped to before the scout jumped in, so good job to our scanners on that one. The scout was quickly dispatched.

June 15 10:27


It's 30 min before downtime. The reinforced Exhale POS will be coming out a few hours after DT.

TL have had wormhole control since our fight and nothing really interesting have happened. Vega have been in a iron grip since the fight at Exhales staging POS. Our iron grip.

The way the alliance have come together and working towards a common goal is a beautiful thing. We have Exhale to thank for that. I doubt that was their intention when they started to mess with Vega.

In fact, this is sort of showing chinks in the armour of Exhale. Not the armour of their ships of course, they are often flawless. But in the organisation. Why would Exhale mess with one of TLs C2 wormholes just to get a good fight?

Its not like we have not given them quite good fights as of late. I'm thinking of the slaughter of TLs POS-bash fleet a few weeks ago.

If it's all over that podding of Tuna, I fail to see how messing up our POCOs and killing a medium tower would be a proper response or in any way worth it.

June 15 12:37

45 minutes before Exhale's staging POS comes out of reinforced. Fleet getting ready, doing last checks on ammo and ships. No signs of any enemies. No tries to escape.

June 15 16:42

It looks like Exhale missed the target a bit with this one. God knows what their plan was in the first place. Getting a good fight? Do they really have so little work that they need to go and train on us?

Anyway, when their POS came out of reinforced TL forces split up between WH control and POS bashers. If Exhale was to try and do a logonski and try to either fight or run, it would be now.

Nothing.

POS goes pop. FC screams at the dude that shoot the wrong thing, incapped ECM gets killed, you know, the normal stuff.

TL is going to keep wormhole control over Vega for yet some time, but for now it looks like we are in the clear.





2012-06-13

Rolling with the big boys

Transmission Lost was flexing some capital muscle a few days ago.

It started when we received a interesting alliance-mail from one of our glorious leaders telling us vividly to get ready, and to bring our best. Dreads, to be precise.

Somehow the alliance had got wind of a few POSes in lowsec that was supposed to come out of reinforced in less than 10h and that we had reason to believe there would be sieged Dreads at site to finish them off.

If we would be able to scramble and get a fleet together at that time, we could possibly drop something on them and get a few capital kills to impress the girls at the club with. Or something.

Capital warfare is not something that the old parts of TL have done so much, especially not in lowsec. The normal triage carrier as the backbone of a fleet in C5/C6 w-space, for sure, but a whole fleet of dreads with a support-fleet and carriers to support those? Nope, that felt quite new. New and exciting!

I must say that the fleet gathered at the rally-system was quite impressive. And so was the organisation of it all. When you have to deal with both a sub-cap and multiple systems with capitals, everything can easily become confused mess. This was flawless.

Just after downtime, we formed up and got ready. Would they come and finish the towers? When would they come? And most importantly what would they bring?

After a long wait, it became obvious that it was going to be a no-show. But since we had all this firepower gathered and a impressive looking support-fleet, we decided that it was not to be wasted. There was a tower close by, owned by a corp we did not care for, so we simply used what we had to reinforce it. More as a statement than anything else.

I think this was the first time we have super-caps in a TL fleet. Even if some of our friends in AHARM are trying their best to design a mechanic around supers that would make it possible for CCP to let them into w-space, so they could be played with by the big boys, w-space corps usually have little experience with supers. For natural reasons.

 

2012-06-11

Trying our hardest to get into trouble

An end-of-life incoming WH in our home system. And it's C4 pulsar. With plenty of plexes in it... To bad we found it so late.

Now we only have two pilots on, and I have been wanting to try and see if just two of our RR-Tengus can run a C4 if they get some help from a booster (Vulture /w T2 links). Hmmm.. I wonder just how long that WH have before it pops?

Ah, f*ck the risk of having to scan ourselves out from and endless chain of C4s! I quickly slap on a probe launcher on the Vulture and fleet up with Danaja - let's go plexing!

Turns out that we had no problems whatsoever to run a site. The effect from the pulsar helps ofc, but mostly it's the godly bonuses you get from the T2 links that really make a difference.

If we got back before the WH died of old age? Sure thing! The god of sudden and unexpected WH-death was most likely visiting his mother-in-law, because the WH was still there, even if we spent over 20 minutes shooting sleepers, blatantly ignoring the EOL warning.

You can either run a few L4 missions in highsec almost without risk, or you can risk having to spend an hour scanning with a unbonused ship just to discover you need to make 40j to get back home for the same ISK.

If you are like me, that's a easy choice.