Tag Archives: Keepstar

More Titans Die at the Final X47L-Q Keepstar Timer

But not as many as before.

If the battle report I cooked up sufficiently reflects reality, a total of 20 titans were lost, down from the 56 destroyed last fight, with the split being 1 lost from attackers and 19 of the defenders titans being destroyed, along with the Keepstar itself.  The battle report shows 2 attacking titans lost, but zKillboard doesn’t show an Avatar being lost by Wotan Oden, so something still needs to catch up.  So it might be 21 titans down, with 2 lost by the attackers.

This, as I mentioned yesterday, all kicked off before I was even thinking about lunch at the office, but I brought my iPad along to stick in the corner of my desk to keep an eye on the battle.

Over in front of my phone, which never rings…

I do have to say that INN knew what data incoming views wanted to know with their overlay.  They had a counter for titans, supers, and specials destroyed, another for the local count, a count down clock for the timer itself and, once the fight started, a display showing the percentage of hull hit points left on the Keepstar.

Aside from the kill counter being a bit confusing… I assumed it was counting attacker and defenders blown up, but it was counting how many ships the attackers and defenders had blown up… that was all I needed running silently at the office.

Anyway, due to the above confusion about the counter I was wondering how the defenders lost a titan before the counter even finished.

Almost fifteen minutes left to go and already a titan down

But it was the defenders who manager to kill a GSF Erebus that was likely bumped, ended up exposed and blown up.

Then the fight actually kicked off and the counter began a lopsided swing towards the attackers.  Later on I heard that one of the things learned from the first fight was positioning.  To deal with the titans on the Keepstar, able to safely tether up quickly after a doomsday kill, Asher positioned our titans at the extreme edge of doomsday range.  That meant of the defenders, who were all over the Keepstar, only some of them would be in range to take a shot.  Unable to bring all weapons to bear on every target they were denied kills.

The attackers, both larger in numbers and grouped up in a tighter ball, had no similar issue and quickly started dispatching vulnerable defending titans one after another.

And then the DDoS attacks started, hitting Imperium coms, forcing the attackers to use text channels to coordinate targets as well as the EVE Online login server.

The usual “Well, of course X did this…” accusations flew, as always from people who have no special insight into the issue, but this attack didn’t help either side.  It imperiled the ability of the attackers to blow up the Keepstar and effectively ended their titan kill streak, while the defenders were unable to bring in additional titans they had staged nearby.  Leadership of both coalitions were unhappy with this state of affairs.

CCP Falcon got on the INN stream to talk about the situation.  The stream itself was dropped from the fight several times.

Back live with CCP Falcon speaking

CCP Falcon gave more information about the state of the servers as well as speaking about why the client end crashes on its own during such big fight, the latter often related to the client trying to allocate more memory than it can access.  This is something that won’t happen nearly as often once a 64-bit client is available, something Falcon said we ought to have within a year. (Until then this post on Reddit can help you avoid that sort of crash.)

All of which happened while I was still at my desk at work.

When I finally headed out the Keepstar was still up, but it was destroyed in the half hour it took me to get home.

On arriving home I logged in my alt, pre-positioned in X47L-Q in a cloaky ship, and warped on grid to see what I could see.  The Keepstar was gone, but the attacking titan fleet still appeared to all be on grid in the bubbles meant to keep them from warping off if they disconnected.

A mighty mass of titans

A directional scan I did of the area showed 466 titans, 322 force auxiliaries, and 191 super carriers.

A closer look at that titan blob shows the smaller capitals mixed in with them.

Zoomed in some on the blob

The area around where the Keepstar was located was still clearly staked out with its own array of bubbles.

Around where the Keepstar was

While there appear to be still some ships there, including several titans, those are all ghosts, either safely logged off or destroyed, but still showing up in space and on overviews due to some sort of server malfunction under the stress of load.  You could not target them, though that didn’t keep every new person who showed up from thinking they could get on one last titan kill.

That titan is a mirage

The wrecks though, they were still there and some enterprising pilots were off to try and harvest some of the loot on field.

An Initiative Mercenaries Rorqual looking to loot

While the battle was over there was still clean up to be done.  A fresh Baltec fleet was called in 6RCQ-V to help cover the returning capitals as well as collect up stragglers and those disconnected earlier in order to get everybody home.  We were bridged to the mid-point Fortizar, where titans were already beginning to collect.

A lot of ships hanging off that Fort

That Fortizar, and another not too far off, was the scene of a heavy interdictor massacre.  A fleet of HICs, as they are called, was sent in to delay the incoming fleets and ended up being slaughtered.

We moved on to X47L-Q where we picked up some subcaps that had been wandering around.  Then we were sent out to blow up wrecks, including the wreck of the Keepstar, in order to leave nothing of value on the battlefield.  Also on the list of things to blow up were friendly ships apparently adrift and not responding.  The only kill mail I was on for the battle was an allied Archon.  Again, we were not leaving anything behind, including free kills.

Then we headed back to the Tosche Station Fortizar and got a bridge back to the mid-point where we had to wait for 25 minutes due to jump fatigue.  While CCP cut back on those timers, jumping four times during a short period still leaves you with some down time.  So we got to sit and watch out bridging titan change the SKINs on his Ragnarok.

Maybe the prettiest

When the time finally came we jump we were out and able to dock up.  That was the end of the battle, with the current battle report numbers indicating that it cost the defenders about two trillion ISK.

Battle report not guaranteed 100% finished or accurate

The battle report has about 100 individuals from various third party groups, but their losses do not add up to much so I left them on the Imperium side of the chart.  Naturally, with this big of a fight the DOTLAN stats show X47L-Q as the most violent null sec system in the last 24 hours.

DOTLAN says…

Pure Blind got the top four spots.  The next two systems are on the way to X47, so are likely people getting blown up coming or going, while the final slot is our mid-point system where all those HICs died.

So that was that, the latest battle in the war of the Keepstars.  The war is not over.  There are certainly more citadels to assail, including the Circle of Two Keepstar in DW-T2I.  I don’t think the Imperium will be satisfied or think about turning for home until at least that has been destroyed.

Others who covered the battle:

Keepstar Down in Kinakka

In something of a replay of the Keepstar kill in Aeschee I wrote about yesterday, the Imperium and various locals formed up again earlier today to kill another Keepstar in low sec space.

This time around the Keepstar in question belonged to Waffles, the former low sec arm of Pandemic Legion.  While SniggeWaffe, the main corp that made up Waffles, was folded into Pandemic Legion late last year, Waffles still exists and holds some assets, including the late Keepstar in Kinakka.

Closing soon…

As with the Shadow Cartel Keepstar, there was a big form up for the kill, with at least seven fleets headed out to low sec, leaving time dilation effects in their wake as they traveled.

Even before we left it sounded like there would be no defenders.  As we metered fleets into the system, the titans landed and started firing, stopping the repair timer and beginning to eat away at the structure.

Titans framed between the uprights firing

I was in Kendarr’s fleet in the logi wing again.  It was the fourth subcap fleet to be pinged out, as the first three filled up before I had even logged in.  I didn’t get to spend a lot of time watching the Keepstar however as we went off to go camp the gate to the high sec system Onnamon.  That kept the faster locking combat ships in our fleet busy, knocking out about 40 kills.

We did get warped on to the Keepstar grid for a chance to get on the kill mail.

More fleets on grid

Unfortunately Kendarr would only warp us in at 100km off the Keepstar for our tag.  While I brought along a sentry drone so I would be able to drop it and take a long shot at the Keepstar, I needed to be inside of 60km to make that happen.  So I missed out on another Keepstar kill mail.  But nearly 2,000 other people made it on.  While somebody was gunning the Keepstar, no fleets came to support it.  Still, Kinakka topped the low sec charts for kills.

Kills happening in Kinakka

And so another structure on the periphery of the fight was destroyed.  The main front in Fade continues to be a grapple over i-hubs.  To get at Circle of Two we need to take those down to remove the cyno jammers so we can go after their Keepstar again.  That will be a while coming.

A Keepstar Goes Down in Aeschee

The War of the Keepstars carried on last night as the Imperium formed up in their forward base in Cloud Ring and went to… um… Aeschee… in the Essence region… to kill a Keepstar owned by Shadow Cartel, a 500 pilot low sec alliance.

That seemed odd.  Not that I think we need a reason to shoot a Keepstar.  If an alliance puts up a structure and cannot defend it, then it gets blown up.  But we are in a war here and Essence didn’t seem like a front line region in the conflict.

Shadow Cartel’s Keepstar minding its own business

However, it was explained that Shadow Cartel is a long time ally of Pandemic Legion and NCDot, not to mention one of our foes in the Casino War, so they were going to lose their citadel for being with our enemies then and now.  And if PL and NCDot didn’t form up to help defend their ally, well there was a lesson to be seen in that.  Plus, who isn’t going to go along for a Keepstar kill?

I was in for it and flew an interceptor over from our staging in Pure Blind to our own Keepstar in 6RCQ-V in Cloud Ring to join up with one of the fleets.  I bought a Megathron so I could join up with the Baltec doctrine fleet I knew would be called.  I felt like flying a DPS ship for once, and I have a nice SKIN for it.

Quafe… so refreshing

When the ping went our for the Baltec fleet forming under Cainun I was in it quick, which was good because it filled up fast.  Unfortunately it filled up with Megathrons, so Cainun first asked people to swap to logi, then started kicking battleships from the fleet in order to make room for logi.  We were going up against an armed Keepstar.

So I bought an Oneiros off alliance contracts and swapped to that.  I would go back to being a space priest for another fight.  Meanwhile, on coms we were asked/told to keep the banter down and be quiet as all fleets would be sharing the same voice coms so Asher could direct us all.  A lot of people would be on the same channel.

With not a lot of time between the form up and the Keepstar’s timer, we were undocked and waiting on a titan to be bridged out.

Waiting on a titan for the bridge, our Keepstar in the background

We could see capital ships undocking and jumping out to the first stop on the trip to Aeschee.  I knew a lot of ships were on the move.  But it wasn’t until we bridged out and landed at the first citadel stop that I started to appreciate how much firepower was on the way.

That Astrahus needs Traffic Control

That is the sort of scene that makes you wonder if an Astrahus should have enough power to tether all of those ships.  And, of course, the titans dwarf everything else.  The capital fleet near the back seems small while you can barely see the subcaps jumping in close to the citadel.

Having done the easy part, the slog to the destination began.  Low sec space tends to also be low utilization, so the nodes running them often start to stagger when a big fleet moves through, and we were several big fleets attempting to gate through the region.  Time dilation quickly kicked in as we went from system to system, easily dropping to 10% when too many people went through a gate at once.

Fortunately it wasn’t too many gates until the next waypoint, but the time went slowly and I started to wonder if we would make it in time.  I was watching Jebi on EVELog Twitch, one of my favorite New Eden streamers and his timer was counting down as we lumbered from gate to gate.

We arrived at another citadel where our titan friend bridged us ahead.  The subcaps were first in the system on a friendly Astrahus on grid with the Keepstar.

On the Astrahus looking at the target

Of course, it wasn’t subcaps only for long.  Soon the titans started jumping in, landing on the Astrahus.

Something, something, titans will never be common…

The titan blob blotted out the citadel, and we were not bridging everybody in yet.  Asher was trying to meter the incoming traffic to keep from revving the tidi meter to 10% by piling everybody on.

When the timer finally ran down we still had people out of the system, but the titans had aligned to the Keepstar already and warped to it to start shooting at it.

Opening salvos

The titan guns were enough to stop the timer and hit the damage cap with room to spare.  It was suggest that titans ungroup their guns and fire using just a single weapon, since most of the damage was wasted anyway.

Of course some people, seeing the shooting start, panicked, fearing that they wouldn’t get on the kill mail.  Like fans at a concert for The Who, seeing this warm up got them to surge forward before their time.  A couple of force auxiliaries warped ahead into the titan ball, only to be targeted right away by the Keepstar.

That meant the subcaps got the call to move forward so we could use our logi wing to try and save the errant faxes.  The first one died before we could get reps on it, but a later one was save.  But now we were in range as bombs headed our way.  We spread out to orbit Cainun as best we could inside the super ball, where movement was constricted.

My Oneiros in the middle of titans

There was a lot of reps to be handed out at that point.  Bomb damage was hitting a lot of people, so I was busy for a stretch.

The handling and rationing of firepower had kept tidi down in system, keeping the shoot to its expected 30 minutes, so eventually the Keepstar wore down to the point that Asher started having groups warp in to tag the Keepstar with their weapons so they would get on the kill mail.

The subcaps turn came and we warped in, landing just 7km or so off the structure.  We were set to apply our minor damage.  I had brought a combat drone for just this reason… I chose the Oneiros because its drone bay can hold a selection of repair drones and still leave room for that whore drone to get on kills… and tried to target the Keepstar.

However, like a lot of people, my client was misbehaving.  With about 1,800 ships on grid, the client was near its memory cap and things were not always working right.  For me this manifested itself in my not being able to target anything.  Everything, including the Keepstar, came back with an error about needing to be within 129km when I was quite clearly much closer than that.

This IS close than 129km

No tinkering with this would fix it and I didn’t want to dump the client and restart at that point.  The kill was very close and I wanted to at least get a screen shot of it as it started to brew up.

The Keepstar starts to go…

The explosion hit.  It is a good thing that there is no splash damage from a Keepstar explosion, as I was very close in by that point.  The big explosion cycles through and a wreck remained on grid where the Keepstar had been.

The wreck as the explosion subsides

The kill was recorded, and while I did not get on the kill mail nearly 1,500 of my close and personal fleet mates managed to at least tag it.  Of course, you couldn’t even get to the kill mail for a while as everybody was hitting zKillboard at the same time, bringing it to its knees.

My client was about done for as well.  It had pretty much stopped responding, so as we aligned back to the Astrahus I was pointed and moving in my own direction.  I killed the client and logged back in.  There was still room in fleet fortunately, a bit of attrition having worn us down from the 256 people listed when we left Cloud Ring.  I was alone when I logged back in, but was able to warp to Cainun and get on the titan that would start us on our trip back to 6RCQ-V.

Thus began the tidi bound flight home.  Still, Asher gave us an estimated time for the operation before we departed which was pretty accurate.  We formed up at 23:00 UTC and he said that if all went well we would be back on our Keepstar at around 02:00 UTC.  We beat that time, but not by a lot.

The ride home was slow, but the lack of anticipation made it much more relaxing.  We jumped and aligned and waded through the tidi as the various fleets tried to stagger their movements along the way.  We sat for a bit at the final waypoint with some of the capital on an Astrahus, waiting for our turn to bridge back home.

Waiting for the word to go

Then it was “bridge up, go go go!” and we were back in sight of our Keepstar, ready to dock up and call it a night.

So, as I always say, the war goes on.  A lot more ops are planned for today and tonight.  There is still grinding to be done in Fade.  And tomorrow there is a final timer for another hostile Keepstar in the north.  I am not sure if that is going to be a fight or if we’re in the mode where we wear down the enemy by setting final timers for which they have to form, only to have us not show up.  But if the ping goes out and I have the time, I’ll show up.  And if not, well, there is always the Alliance Tournament on Twitch.

Other coverage of this event:

Friday Bullet Points from New Eden

Time for a Friday catch-up post, this time focused on EVE Online.. with a few items I won’t roll together a post for yet feel I should mention.

  • Pandemic Legion Escapes!

The bubble camp in failed to hold back an organized breakout in UALX-3.

The location of the camp

After several days of feeding TEST and the Legacy Coalition dreadnoughts and subcaps, the fleet trapped by the initial Keepstar fight in UALX-3 finally got its act together.  A subcap force cleared the area early on the 25th, allowing most of the capital force to log in and jump out, denying TEST further easy kills.  The full story, complete with video, is up over at INN.

Of course, over on Reddit, where TEST and Brave had been smugging hard in /r/eve, the tables turned as the formerly trapped returned the favor with a savage mocking of their own, made all the worse by the /r/eve moderators being on strike and only removing TOS violating posts, as opposed to their usual effort to trim back repeats and low effort bad posting.

  • More Keepstars In Peril

The war continues.  While the Legacy Coalition was sitting at their camp to try and keep the northern fleet from being a fleet in being, the Imperium moved back north and resumed its grind against the foes up there.  One Keepstar went down without a fight last night (more on that in another post) and one is set for its final timer later today tomorrow.

  • New Referral Program

This has been in place since early in the month, but I thought I would mention it here.  I stuck it in the position where you put the weakest item on your list, which is to say neither first nor last.

Earlier this month CCP announced an updated/changed/new referral/recruitment program, the details of which are here.  Structured like an event for The Agency, you can accrue better rewards by recruiting more people to the game, including special ship SKINs.

Are you recruited or have you been recruited?

All of this hit with the usual damp squib effect for which CCP can be famous.  The forum thread about it accrued a long series of “fix my thing!’ posts and other complaints about the game, not one of them new.  The video released to push recruiting also had its detractors.  It certainly didn’t feature much of the game, with the whole thing feeling more like a Farmer’s Insurance ad.

The old recruitment links have been migrated to the new system, though I am not sure that will help me.  I’ve had a recruitment link up at the bottom of the side bar over on EVE Online Pictures for more than five years, have had people click it and tell me they have subscribed, and have never received any reward or notification.  So my own reaction to the program was cool as well.

  • Alliance Tournament Starts Tomorrow

The annual Alliance Tournament kicks off tomorrow, speaking of things to which my reaction has always been a bit chilly.

Episode XVI – EVE NT Takes Over

I tend to be a purist about EVE Online.  In my world view, everything that affects the game happens within the game on the single server which we all share.  So an e-sports event, with a set of arbitrary rules, which only certain elites can join in on, that takes place outside of the game, and which rewards the winners with PLEX and special ships that come back into the game, is contrary to the spirit of the game in my view.

Also, EVE Online is difficult to watch on a stream if you want to get a good sense of what is really happening and the volunteer commentators… can vary in quality.  Not everybody can be Elise Randolph or Jin’taan’s tie.

But some of the kids seem to like it and certain groups pretty much fold up shop to concentrate on it every year.  I am surprised there is a war on currently, as I have no doubt key people are fully invested in it.

Anyway, the first rounds of the Alliance Tournament start tomorrow.  There is a detailed Dev Blog up about the event, with links out to all the information you need.  There is also a site setup where you can see all of the pending matches and make your own predictions, and INN has a post up with the prize ships and a last minute rule change.  The matches themselves will be streamed on the CCP Twitch channel throughout the weekend.

While CCP is providing the prizes as usual, this year also marks the handing over of the running of the Alliance Tournament to the staff at EVE NT, who will be streaming the event from their studio.

Addendum: Four teams are out of the event, so four other teams get a pass in the first round.

A Keepstar Lives in Tenerifis

If at first you don’t succeed…

Last night saw the second Keepstar deployed in UALX-3 in the Tenerifis region come online successfully.

Home for Executive Dino

The circumstances of the past few days allowed this to conclude successfully.  The big fight over the first attempt to anchor a Keepstar in UALX-3 led to the node crashing after the Keepstar had been destroyed but before the attackers could extract themselves from the system, leaving many pilots trapped, logged off on the grid where the fight took place.  This area was covered by anchored bubbles by TEST who have been camping the area since the system came back up.

A field of bubbles waiting for people to log back in

With a fleet trapped and camped in the system and TEST able to anchor a cyno jammer to prevent reinforcements, the stage was set for the second Keepstar to online successfully.

I did not get to hang around and watch the Keepstar come online, but I was there earlier in the day to join in the camp and to watch the Fortizar that was anchored on the edge of the bubbled area come online.

Just before it started to anchor

You can see a large covering force around the Fortizar, with the bubbles nearby and the Keepstar, still a few hours from anchoring, in the background.

Once anchored, the Fortizar was a handy location for carriers to sit as they sent fighters out into the bubble camped area.

Meanwhile, as the camp dragged on, it seems that the FCs of the trapped fleet started telling members logged off but stuck in the bubbles to petition to have their ships moved by a GM under the theory that they were trapped.  I guess given a wide enough definition of the word they were trapped, but not in the way that CCP intended when it comes to asking for GM help, so CCP felt the need to issue a news bulletin on the topic.

UALX-3 Fleet Fights – Misfiling of “Stuck” Tickets

Over the course of the last twelve hours, we’ve been made aware of instructions being broadcast by the leaders of several alliances to file “Stuck” support tickets in order to have their capitals, supercarriers and titans moved out of the system of “UALX-3” by the GM Team.

This comes after a node death occured at around 09:00 UTC on July 19th, during a large scale engagement over an anchoring Keepstar, which resulted in the attacking forces being sieged in the system.

Our policies are clear when dealing with large-scale player engagements, and the GM Team will not intervene and move capitals, supercarriers or titans for pilots involved in these kinds of fleet fights, as per our Reimbursement Policy:

“Any losses of any kind resulting from a large-scale player engagement are not covered by this reimbursement policy.”

Furthermore, it is not possible for us under any circumstance to move ships sporting their own Jump Drive. This is clarified in our “Inaccessible Assets And Returning Players” article:

“Ships sporting their own jump drive are assumed to be capable of jumping themselves out quickly without the usage of a gate and no exception or move will be granted to these ships.”

Please be aware that the GM Team will not grant relocation of ships involved in large-scale player engagements, and that attempts at co-oridinated mass filing support tickets in order to avoid the destruction of ships involved in engagements of this nature may be considered abuse of the support ticket system.

Pandemic Legion an its allies aren’t going to get CCP to move them out, so the camp continues.  According to zKillboard it looks like there was an attempt to break out some dreadnoughts early this morning, leading to a series of kills,

But the camp won’t last forever.  People will either try to break out and either succeed or get blown up, or hunker down and wait the long wait until the locals get tired of deploying bubbles and sitting around waiting for people to log in.  Given that there are some titans yet to be accounted for, the camp may go on for a while.

Keepstar and Fortizar watching the bubble camp

And, of course, the next question is, “What now?”  Will deploying this Keepstar and trapping some of the attacking capital fleet blunt the attacks on TEST and its allies in the south?  Will the Imperium, which showed up in force for these Keepstars, stay in the south, return to Delve, or move back to the northern front once more to assail Circle of Two and Guardians of the Galaxy?

Then there is the propaganda war on Reddit, which has reached a high water mark of smug from the defenders.  Some examples:

Addendum: Meanwhile CCP Falcon has taken the time to lay down some facts on Reddit about some controversial aspects or misunderstandings about battle and subsequent stranding of capitals in UALX-3 in order to set the record straight on what CCP will and will not do.

A Keepstar Dies in Tenerifis and Another Appears

A pattern is starting to emerge in the current null sec war.  Keepstar fights are becoming a regular thing.  We might end up calling this the Keepstar War.

The latest round unfolded on Wednesday night/Thursday morning in the system UALX-3 in the Tenerifis region, close to the boarder with Catch.  TEST had dropped a Keepstar in the system the night before, a deliberate challenge to Pandemic Legion and its allies attacking from the southeast.

The attackers could not let the Keepstar online.  Killing a Keepstar as it anchors is a one shot deal, if they could manage it.  If they let it anchor and be fueled up, the attackers would have to go through the three rounds of shield, armor, and structure fights in order to dispatch it.  So there was a good deal of incentive to take care of business immediately and a fight ensued.

It was a huge fight, with ~4,000 people participating and hundreds of ships being destroyed as Pandemic Legion and its allies piled into the system.  The Imperium, now blue to TEST and the Legacy Coalition, showed up in force to help defend the Keepstar and things escalated into capitals and super capitals.

A screen shot from the fight

I was not at the fight, so that screen shot comes from Xsubdude’s Imgur gallery of pictures from the fight.  Definitely worth a look.

According to a Reddit live blog of the fight, which will give you a timeline, the losses were a follows:

PANDEMIC LEGION &EASTERN ALLIES LOSSES:

  • 9 titans
  • 18 dreads
  • 74 Force Auxiliaries
  • 628 subcaps
  • 729 ships total
  • 1.09T isk lost

IMPERIUM/LEGACY LOSSES:

  • 4 titans
  • 339 dreads
  • 613 subcaps
  • 956 ships total
  • 1.45T isk lost (figure includes Keepstar loss @ .3T isk)
  • 1.15T isk lost in ships alone

The large number of dreadnoughts represent TEST dread bombing the attacking titans and their support repeatedly.

There are battle reports circulating, though so many parties were involved in the fight it is hard to tell if everybody is lined up correctly.  It mostly matches the stats above, though since fighters get counted on battle reports, the total kills are higher.  I had to fix two parties at that link and I am sure it still isn’t wrong somewhere.  But I grabbed screen shots of the stats from DOTLAN the next morning and the 24 hour stat shows that UALX-3 and the Tenerifis region were high on the list of destruction.

Taken about five hours after the fight

The fight was set to carry on until down time, with both sides locked together and more forces poised to jump in, but the node crashed.  However, but that point the Keepstar was already dead, so the attackers had won both the objective and the ISK war.

So what do you do after you lose a Keepstar, lose the ISK war, and the node dies so you can’t even keep killing enemy titans?

Well, step one is to anchor bubbles all over the last known location of the hostiles so if they start logging in again you can pick them off.  The node crash left them all on the field so you might as well try to grab them.

A field of bubbles waiting for people to log back in

And, of course, you need a lot of watchers to grab anybody who logs back in.

All those blues are hungry for guests

And, of course, you bubble up the gates and generally try to keep a lid on the system so you have a good chance of blowing up anybody foolish enough to log back in alone after the fight.  The combined effort seems to have been effective in picking off people trying to log back in to escape, though that has been limited to subcaps.  Nobody has sacrificed a titan that way yet.

Finally, I guess if you’re Progodlegend, you drop another Keepstar right where you lost the old one.

Another Keepstar coming up!

The Keepstar War continues!  Even CCP seemed surprised.

And for good measure, you drop a Fortizar as well right next to where the bubble farm is.

Fortizar coming online

The Keepstar is set to come out at 02:00 EVE Online time, which will be 7pm in the evening for me.  We have other plans for the evening, so I am going to miss at least the open rounds of this next event.  But I have a stealth bomber in a safe spot in the system should I get home in time to look in on the fun.

Pandemic Legion and their allies already have a capital and super capital force on grid, so it will be easy for them to join in I suppose.  However, the defenders know right where they are, so can position themselves accordingly, and preparations are already under way for this next event, as well as for any break out attempt by the attackers.  There is even a rumor of a cyno jammer going up in the system, because after Keepstars it is cyno jammers as a possible theme for this war.

Where it will all happen

In a few hours we will see what both sides have planned for their Friday nights.

Other coverage:

Imperium Ignorance Saves the CO2 Keepstar in DW-T2I

After laying down a Keepstar in Cloud Ring last week, the Imperium went straight to work on Circle of Two, reinforcing their Keepstar in DW-T2I the next day.  The Imperium staged in Cloud Ring meant that most of Fade was in capital range, if those capitals took the gate between the two regions.

Fade Map with Locations noted

With the Keepstar in DW-T2I reinforced, the next big even was set to be the armor timer.  To destroy a fueled citadel you have to go through three battles.  The first is the shield layer.  You can attack at any time and if you get the citadel’s shields down to zero, a timer comes up.  When that timer finally counts down the citadel goes into a 15 minute repair cycle.  You have to form up and shoot it again, this time shooting its armor layer down to zero.  By applying enough damage you can stop the repair cycle and get through the the final timer.  When that comes up you do the same thing again, only shooting away the structure.  If you succeed, the citadel blows up.  If you fail, you get to start all over again.

So it was the second round, the armor timer, that came up yesterday.  It was set to hit at a little after 19:00 EVE Online time, which is UTC.  However, because fleets had to move and get in position, the call to form up came a good four hours before then.

That was before I got out of bed here on the west coast.  I turned on my computer to find fleets already forming and heading out from Delve.  But that was okay.  I wasn’t interested in heading out with main fleet for the long drive there and back to visit CO2.  I hung around waiting for something to form up in Pure Blind.

And I was rewarded for waiting with a fleet ping from Dabigredboat.

Some might not consider that a reward.  Boat can be an acquired taste.  But he works hard, gets you in the action, and tells you what is going on.  Plus, he was handing out free ships.  We were going to head out in Tengus to snipe targets of opportunity and run down disconnects.  I was happy enough to be in a Tengu again that I bought the snappy new Ghostbird SKIN for it.

55 PLEX well spent to my mind

Meanwhile I already had an alt online in a stealth bomber in DW-T2I to watch what was happening with the Keepstar and the system in general.  CO2 had been busy.  Both of the gates into the system were heavily bubbled, so any fleet trying to gate in to contest the timer would have to get past that.

The P-33KR Gate

You can just barely see the Keepstar in the background of that screen shot, through the dense layer of bubbles laid about the gate.  The array of bubbles was big enough that if I pulled back to get them all in the screen shot, the gate and the small bubbles around it become difficult to see.

The same gate from a distance

Everything seemed to be coming together for a big fight.  While Boat was arranging a black ops bridge up to DW-T2I my alt sat and watched CO2’s allies start to show up.  Darkness and their coalition brought a Tempest Fleet Issue fleet.

Darkness in a ball

Ranger Regiment brought an Ishtar fleet.  NCDot brought a Machariel and a Cerberus fleet.  CO2 undocked a fleet of Megathrons.  And capitals began to form up about the Keepstar.

Boat got us a bridge into system and we went off to safe spots to cloak up and wait for something to do.

Tengus on the way

In system Boat was keeping us up to date about what was going on while also looking for something to shoot.  We went and tried to pick off some transports that were parked near the O-CNPR gate.  We didn’t get a kill, but we scared them off at least.

Then Boat said we were going to go try and shoot the cyno jammer in system.

This was the first of many times I would hear the words “cyno jammer” during the op.

Boat explained that the previous day and evening the Imperium spent time putting up POS towers on every free moon and reinforcing the towers that CO2 or anybody else had deployed in the region.  This was to keep a cyno jammers from being deployed.  A cyno is a beacon which lets ships with jump drives travel to it.  You need a cyno lit in a system in order to jump into it.

A cyno jammer, as you might imagine, blocks cynos from being lit.  The ones on a POS jam the whole system, and CO2 had one in DW-T2I.

(Cyno jammers do not block covert cynos, which only black ops capable ships may use, such as our Tengus, which is how we got into the system.)

So Boat warped us over to the POS with the cyno jammer and had us start shooting it.  Very shortly a Minokawa force auxiliary logged on just outside the POS, close to the cyno jammer, and started to repair it.  CO2 had prepared for an attack on the jammer and, later, more Minokawas were spotted on the POS.  The Minokawa was repairing faster than we could inflict damage, so Boat warped us off and we went to our safe spots again.

As we sat around I turned up the volume on the INN stream of the event and heard Boat talking about the situation.  There, and on our own coms later, he explained that somebody running the preparatory ops believed that cyno jammers would not function on reinforced POSes.

This turned out to be a fairly wide-spread belief.  Progodlegend, on the same stream, said that they had just done the reinforce thing to Fraternity recently.  However, it appears that Fraternity just didn’t try anchoring a cyno jammer on a reinforced POS, no doubt because they believed the same thing.

GigX however, knew better it seems.

If we had known some simple contingencies could have been put in place, like leaving behind some logged off dreadnoughts to knock out the cyno jammer quickly to let fleets start pilling in.  But we didn’t so we were stuck.

That left the only way in to the system for the converging Imperium fleets… with more capitals on the way than the defenders had ships on hand… with one way into the system; through the O-CNPR gate.  But, as I mentioned, that gate was heavily bubbled.

The O-CNPR Gate

And it wasn’t just heavily bubbled.  It was also heavily defended.  The direction scan of the vicinity of the gate showed the following:

O-CNPR Gate DScan

Yes, you cannot possible read that unless you click on it.  But among the things on the list were 425 battleships, 124 super carriers, 35 carriers, 683 fighters from the carriers and super carriers, 504 drones from various ships, and a titan.

That titan, just sitting in a bubble waiting to boson somebody

So while it was possible that the Imperium could have thrown everything through the gate and eventually muscled past the defenses, it was going to be a slog.  Defending on a bubbled gate like that is referred to as “water boarding,” because it is torture that the attackers cannot escape.  With more bubbles no doubt set to be deployed and inderdictors on the field, a hostile fleet could be kept writhing in that mess for hours.  Certainly they could be held in check until the repair cycle on the Keepstar finished up.

Instead everybody turned around and went home.

That was it.  GigX won the day and saved his Keepstar.

As far as I can tell the biggest fight in the whole event was a smart bombing drop by NCDot on an Imperium Jackdaw fleet.  They did kill a lot of ships, 64 according to the battle report.  However, they lost 20 of the black ops battleships they used, destroyed by their own fleet’s smart bombs, which left the cost of the operation at roughly ten times the ISK of the hostiles they destroyed.  Not a good trade.

Battle Report Header from the Black Ops Drop

That was fine for everybody else.  However those of us in Boat’s fleet were still in the system and he was on the INN stream talking about events as they unfolded.  However, the stream wrapped up pretty quickly once it was announced that the Imperium was not going to show up.

Boat did not forget about us, though he forgot about his titan in the super fleet for a bit and almost got left behind.  He got a black ops battleship in to send us all back to Pure Blind, staying behind to cover two people who had gone AFK long after some FCs would have left them to their fate.  I got one last look at the Keepstar before we bridged out.

Still 35 minutes left on the clock

I was glad again to not have schleped all the way up from Delve in a Baltec fleet only to have to turn around and go home again.  But that was still shorter than having a fight before the return trip, so a bunch of people got some of their day back.

The Mittani held the weekly Fireside Chat on coms where he explained what went wrong and how we were going to go back to doing things the old fashioned way, grinding and suppressing the region until CO2  retreats.

Not our most brilliant hour.  Reddit will be filled with comments about Goons being dumb and not knowing POS mechanics for a while.

I guess we know the answer

But everybody knows about that POS mechanic now for sure, so if if anybody else falls for it… well, more of the same on Reddit I suppose.

So the war goes on.  We still have a Keepstar of our own on the border of Fade and SIG and Squads are still roaming north from Pure Blind.  The fun is not over, but it may be a while before we pave our way to the Keepstar to do anything more than keep it reinforced.  I suspect we’ll keep reinforcing it to ensure that CO2 can’t pack it up and move away.

Meanwhile there was no saving the TEST Keepstar down in 4-GB14 in Immensea.  They couldn’t even use GigX’s cynojammer trick since hostiles had already grabbed the ihub for the system, and if you don’t own the ihub you can’t setup a cynojammer.  And so that Keepstar died.  It wasn’t their capital Keepstar, but losing one hurts no matter what.

And then there was the Provi Bloc Keepstar, anchored down in 9UY4-H, which went online successfully.  This event also involved a cyno jammer, that being the EVE Online word of the day.  Hostiles sacrificed dreads to incapacitate it, but Provi just finished it off and anchored a fresh one, leaving the attackers without an easy way in.  Even being able get the cyno jammer offline doesn’t mean you’re good to go.

[Update: Or maybe Provi repaired the jammer. I’ve heard both stories now.]

So it was quite a day for null sec Keepstars, with one successfully defended, one destroyed, and a new one online.  And we all know just a bit more about POS mechanics, just in time for them to go away at some point in the near future.

Others on this topic: