Tag Archives: UALX-3

The Imperium Rebuffed at UALX-3

Apparently we ran out of Eagles.  Or that was the word by the time I was able to get logged in and join one of the reinforcement fleets.  I had an Eagle.  It was the ship I brought out on the first move op.

Heading eastward through an Ansiblex

But it was too late by then.  By the time I was in a fleet and up on voice coms we were being told to stand down, that we had been thwarted in our first major battle of the brewing war.

All of this was around the ihub in the system UALX-3… another system with some history, where another big fight took place… located in Tenerifis, where we were just a few weeks back.  The Imperium had reinforced the ihub and the timer came out yesterday afternoon my time.  PAPI decided to contest this and a tug of war over control of the system broke out, running for several hours.  The joys of Fozzie Sov.

Northwest Tenerifis – June 24, 2022

The system is not too far in from Catch, where we are staged currently, and would make a good forward base if we could grab it and hold it.  However, we failed to do that.  The battle report, which covers all of the systems in the constellation, because that is how the sovereignty contest system works, with nodes appearing constellation wide to fight over, showed very even numbers

Anyway, the header from the battle report:

Battle Report Header

1,400 pilots counted in the tally, divided between the two sides,  though those who don’t get on a kill mail somehow, which often means logi, don’t end up on the main report.  Still, a significant number of ships on the field, with 1,604 ships destroyed, which means there was significant numbers re-shipping and returning to the fight after they were blown up.

All told, just shy of 209 billion ISK was destroyed in the fight.  We’re not into World War Bee top ten battles territory yet… not even close… but for the opening of a conflict it is not insignificant.

The Imperium lost both the objective and the ISK was and had to pull its forces back to its staging system to regroup.  This failure means a reassessment of the plan of attack no doubt, along with a call for more supplies and more pilots to move to the staging Keepstar in Catch.  Move ops are carrying on and contracts are going up on the market to supply the war effort.

We will see how the next strike fares.

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: