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.

2012-06-10

How to fail 4 times in 20 seconds

Today I killed our recruiter.

foxxytiger is a great girl to have on board in any corp, and I have had the pleasure to work with her since way back in the beginning of 2010. She's a bit reluctant pvp'er thou, and since she is often the only one around when I want to go and try something stupid, she often have to tag along and vitness my fails from the first row.

This time we had a scout telling us that there was a Dominix and a Oracle hanging on the highsec WH. Normally we don't mess with highsec WH games, it's usually pointless. But this time the ships in question was part of a small war going on in our static C2. We obviously had got involved and now it would be of use to us, if not to kill them, so at least to push them out into highsec.

Well, we quickly kicked the great and mighty war machine of Transmission Lost (now the largest w-space alliance) into gear. That is, me and foxxy jumped into some T1 ships :)

I got into a Mega, with the idea to just blast closest thing at the WH, forcing them to jump. foxxy have been fiddling around with a Oracle-fit lately, and since she got nasty laser-skills, we thought it was time to try it out for real.

Enter fail 1.

Our static was a wolf rayet, making the resists on my armor Mega 18% stronger, but at the same time makes the already skimpy "tank" on the Oracle 18% less resistant. With her BS skills and the bonus in the system we would have been much better of with a Geddon.

When we warped to the WH I expected to see the ships hugging the hole in the usual way, but when we landed they was actually 40km off! Fail intel on our part, and I had acted on it. Darn, darn, darn. Had I known they was not in jumping-distance we would obviously have gotten a warpin right ontop of them - fail number 2.

Ok, so we ended up with a Mega on the WH, the Domi 40km off and the Oracle somewhere around the same range. Foxxy had warped to range, so I don't know if she was in perfect optimal, way off or right on top of the enemy Oracle. Making good decisions in short time when you need to change the plan is a good mark of a pvp'er. I'm obviously not that, because I continued to make mistakes. Say hello to mr fail 3.

Instead of just gunning for the closest ship (prolly the Domi, it's hard to catch a Oracle in a Megathron) using the fact that they was not in jumping-range, I hesitated, staying t the WH. And if that was not enough, I for some reason called the Domi primary (assuming that that was the only thing we could get point on). The result was that while trying to chew through a BS tank with resist bonuses (wolf rayet) in a ship that was way out of optimal, their Oracle managed to get the mega down so much I had to jump.

In all fairness their dominix was in low armor too now, but as they turned their guns on foxxy she misjudged the time to get into warp and lost the Oracle. I don't think she was pointed at the time, so losing a ship that's free to warp is always a bit of a fail. Fail number 4 in this case.

Well well, we do this to learn and to have fun, next time she will have a much better feel for when to bail.

So what should we have done then?

Apart from failing to scout the situation correctly (ON the WH is not exactly the same as 40km off), if I had told foxxy to go for their Oracle at the same time as I burned to the Domi to get a point, we would most likely have ended up with a Domi-kill and possibly even a Oracle, if that pilot made same mistake as foxxy...

Same situation, two totally different outcomes, and all dependent on a bad call. Maybe this all comes naturally to everybody else, but for me, the number of stupid things I can pull off is just staggering. It bothers me that it's so bloody obvious things.

Maybe I'm never going to get good at this...

2012-06-09

Lucky exit, unlucky Iteron

I don't know what we have done to please the WH-gods, but we have had a several days with empire exits that's been just a few jumps from Jita.

Assuming one think closeness to Jita is a good thing... maybe it have nothing to do with the cov-ops we ritually sacrifice at the sun each Friday, because it's not really our empire exit, it's more our statics empire exit. Since we live in a C4 with a static C2, we always need to borrow someones system (and what more often than not is a sleepy little Indy corp) to find a way to Empire. Maybe it's the inhabitants in today's C2 that I need to thank for the exit the gods granted us with.

The C2 have a static lowsec, but it's still only 3j from Jita. Amazing.

So, we used the route to Jita and refueled a POS. Maybe I should say "acquired some materials to create some POS fuel". More exact would be to say we stole it. Better still, to say that we stalked some dudes in our the static C2, and when they tried to bring their stuff back from Jita, we removed the thinn wrapper that most people call an Itteron V around said fuel-parts and picked up what dropped.

100M in fuel parts, thank you.