Tag Archives: NCDot

Fortizar Defense Brawl in JE-D5U

Another trip up north, up the Eye of Terror and into Pure Blind.  I’ve been up north a few times to defend one structure or another and a fight has yet to show up for me.  Not that there haven’t been some fights lately, it just hasn’t seemed to happen when I’ve been on the op.

But last night things finally rolled my way.  There was yet another Fortizar to defend up in the north and the word was that PanFam and the locals were going to form for it.  Maybe the other side was emboldened by killing our Keepstar. (Unanchored, and in a freighter, but they still killed it in the end.)

Anyway, the call went out for the op, but Asher had pinged Reavers a bit before looking for some people to fly ECM burst interceptors.  I’ve done that before and not many people were X’ing up, so I figured I had best jump in to help there.  Also, the ships are handed out for free and during the battle you get to sit above it all and see the whole thing… not that the view helps me much, I still never get what is going on half the time even when I can see it.  I took an Ares from the offer and got ready.

Asher was set to lead the Sacrilege fleet, so he had a newer FC, Kappa Hutt lead us on to the field.  So the Sac fleet and a Baltec fleet set off for the north with our interceptors flying along, peeking ahead to scout, then letting the others catch up.

My Ares in with the battleships

As we made our way along the route we caught up with some bigger ships that had started out ahead and were also making their way to the fight.

Some dreads in the mix now

We zipped ahead though… there was a gate that had been seriously bubbled, but that doesn’t bother interdiction nullified interceptors… and arrived in JE-D5U up in Pure Blind ahead of most of our fleet, but there were already over 300 hostiles in the system according to local.  There was going to be a fight it seemed, and the timer was counting down.

Less than six minutes to go

As the other fleets arrived we set about bookmarking our perches over the potential battlefield.  The plan is generally that we sit cloaked on a perch while the FC scans down a potential target, often the FC of a hostile fleet who is usually out in front of the pack.  Then we get the word to uncloak, overheat our burst jammer, and align, at which point the FC warps everybody beside himself onto the target.  We land, started warping back to a bookmark, then set off our ECM burst.  If the warp was good we’ll be in the middle of some hostiles and break some of their target locks… this is especially good if we land in the logi… and be warping back before anybody has a chance to take a shot at us.  Done right you don’t even get any heat damage on your mid slots because the burst goes off as you’re going into warp, which shuts down the module.

So we got ourselves in place as the timer counted down and the fleets got into position.  A fight seemed guaranteed as there were quickly over a thousand people in the system, with TEST dropping in to third party on the event, and even some notable PanFam FCs on grid like Vince Draken and Headliner leading Muninn fleets.

Hostile Muninn fleets getting ready

The timer hit and the repair cycle started, which meant we had to defend the Fortizar for 30 minutes while it repaired, though that 30 minute timer could be paused or pushed back by hostile fire on the Fort.  It was on.

Fight around the fort begins

Kappa Hutt was having a bit of a problem getting a probe signature on a good target.  Time dilation and system responsiveness was really bad, with the tidi number well below 30% for most of the fight, and into the 10% for some stretches.  Still, he got something and we got ourselves ready to go.

Uncloaked on a perch above the fight

We were then thrown into the fray to set off our jammers.  I landed pretty well the first time and got off some jams.

In with the hostile logi even

Meanwhile, the forces on the fort broke tether and were shooting up the attackers as they ran past the structure.

A Baltec Megathron on the fort

We warped off and back to our perches where we waited for the next target.  The scanning interface was acting up for Kappa still and for a few runs SpyFly Catharsis found wrecks for us to warp to, which worked as well if we timed it right.

Once again into the mix

We were getting good warps and I don’t think I went in even once where I didn’t get at least break a few target locks on hostiles when I landed.

Along the way I got a pop up that a bounty had been collected on Nkosis when his Sacrilege went down.  I think I have mentioned him before, but he is a newer addition to the coalition who is so enthusiastic and positive about the game that he has become something of a celebrity in his own right in the Imperium.  But being a celeb means he gets razzed as well and at some point he got a bounty place on him, which he didn’t like and said so, at which point everybody started adding to his bounty total with an eye towards getting him to the number one spot.  He was into the top ten last I checked.  I, too, put a bounty on him, so now I get a notification every time he gets blown up when I am in game. (I used to put bounties on our FCs as that pop up was often the quickest way to find out the FC was down.)

We had a bit where we had gone so many times in a row that we didn’t have enough capacitor to make a run, the ECM module needing over 200 units of power to activate on top of the bit you need to get your warp in and out.  This was when the system was into the 10% tidi zone, which is the slowest the game will go and, if that isn’t enough, controls begin to lag and your commands may get ignored.  Waiting for cap to refill during that was excruciating.  Somebody suggested we wait for our weapons timer to go down and just warp to the fort to tether and fill up our capacitors, but at 10% tidi having just 15 seconds left on the time meant nearly a three minute wait.

Still, tidi hits everybody.  The targets were as slow as we were and were not going to get away.  Cap was restored and we were sent in again for more runs.

Aligned for another run

By the the tidi was starting to relax a little bit, or at least get up into the low 20s, and Kappa was able to get good probe locks on some likely targets, so we spent some time dropping on names I recognized.

Coming for Vince

Down around the fort, the repair timer vacillated between running down and being paused, but kept moving slowly towards the structure being repaired.  By the time we got past the worst tidi it stood at around ten minutes.  We kept on going.

Landing on the hostiles again

At about the eight minute mark on the timer it seemed like the battle had been decided.  The hostiles pulled some distance and “gf” for “good fight” started getting spammed in local by them.  Some “fofofo” appeared in local as well, which I am going to guess was from Asher’s sac fleet as he is the only FC I know who still does the “fofofo” for victory.

From that point tidi began to ease up and we were released to go loot the field if we wanted.  Being in interceptors would seem to give us an advantage, but Goons will plunder like no others.  I didn’t come up with anything.

Somebody dropped an MTU, which is always a target on a battlefield no matter which side drops it.  I zipped over and got in on that kill.

Not that I needed another kill mail.  Landing on fleets and setting off an ECM burst puts you on the kill mail of anybody you jammed should they get blown up after you’re there.  My kill board was well padded by the end of the battle, with 111 new entries, enough to get me momentarily onto the top ten for KarmaFleet.  (The last time I did that I was also doing ECM bursts.  It is a kill mail whore’s dream.)  Most of them were hostile ships, but there were not a few blue targets on the list and quite a few pods.  A few of us even got the final blow for pods that were self destructing when we hit them.

The timer ran down and the fort was safe.

Tethered off the save Fortizar

At that point we were done.  Kappa set us free to head home, which should have been a quick ride in some interceptors.

Back through gates towards Delve

There were some bubbled gates along the way, but an Ares just passed through bubbles.  I was feeling somewhat invulnerable flying home, which I should recognize by now as a sign of impending doom.

My usual travel Ares has a 1.83s align time, and the game lore is that if your align in under 2 seconds you cannot be caught unless you are extremely unlucky.  But this Ares, fit for ECM burst runs, had a 2.03s align time, which means 3 seconds by the way EVE Online calculates, which means it can be caught.  It isn’t likely, but somebody who is good in the right ship can get you.

And they got me in Cloud Ring with a camp that was primed and ready to catch anything possible.  Normally I am inclined to attribute losses to my own incompetence rather than claim my foe was really good, but I think this crew was actually pretty good at this.  I was toast and knew it almost instantly.  Kind of a sour point to end the evening and I always feel bad when I lose a hand out ship, but it happens.

As for the fight, it seemed to be lauded by both sides as a good fight.  Asher posted a salute to the attackers on Reddit and other related posts seemed to be similarly warm and fuzzy about a real fight going down, which was a bit of a change from the acrimony over the Keepstar thing I mentioned earlier.

The results… well, pick your battle report generator and get your results.  EVE Battle Report Repair Tool seems shy of the mark for totals while the zKillboard report is detailed but has a habit of pulling in things outside of the fight.  For a report header image I am going to go with EVE Fleet Manager, which is close to the zKillboard totals, but which lets me pull out a few oddities.  I don’t think the Guristas, for example, really took sides in that fight.

Battle report header – trimmed to the top 7 alliances –  click on it to enlarge

Overall quite a fight.  A big brawl, fairly evenly matched, lots of losses on both sides that went largely our way as we had the Fortizar to tip the balance.  And there was quite the array of space famous names from both sides.  I even saw Bad Juice, who once challenged Asher to an MMA style cage match back during a Reavers deployment.  I was happy to report in the Reavers channel that he was still around and that I managed to get on his kill mail.

That battle would probably be the beat event of the month for me, but the word is that the Goon Expeditionary Force will be deploying later today, so the promise of more fights is out there.  Or at least more structure shoots.  Mittens was using the term “glassed” again, so we might just be burning down structures somewhere.

Keepstar Down in P3EN-E

In the wee hours of the morning… 1:30am here on the Pacific coast, 4:30am on the east coast… the final timer for the Keepstar in P3EN-E in the Vale of the Silent ended.  An Imperium fleet had been gathered for that moment and proceeded to destroy the structure.

Keepstar kill mail

I choose to keep on sleeping rather than spend a couple of hours forming up with a fleet, traveling, shooting, then schlepping back home, a choice many of the people who engaged in last week’s double Keepstar kill appear to have taken as well.  There were 859 pilots on the kill this time around, down from over 1,500 on each kill last week.  I guess one Keepstar isn’t worth missing a few hours sleep in the middle of the night.

The kill mail shows the usual giant blob of titans, supers, and smaller capital ships, though this time around it looks like the supers did the bulk of the damage with fighters and then everybody else was jumped in to get on the kill.

The grinding of PanFam space continues.  There are more structures left to kill, including a Keepstar in SH1-6P, where the ihub is already under assault.

Where Will War Land in New Eden Next Week?

The Mittani was promising us a war last week, asking us to tune into the weekly fireside chat to get an update.  There were more than 600 people in the channel for that on Saturday before a ping went out to get people logged in.

A past visual from The Scope of The Mittani speaking

However, the news for us was rather sparse once the fireside got going.  We were assured that was was coming, that the next fireside would be replaced by a Station of the Goonion meeting (which differs mostly from a fireside in name, though it tends to be shorter and more on point) which would announce the target of our war, after which move ops would commence immediately while those already forward deployed would begin hitting targets.

It was also stated that this would not be a war of conquest… Delve is already making us rich, so we don’t want more space… but a war of destruction to lay waste to the infrastructure and disrupt the economic output of a region.

The question, left deliberately unanswered was which region?  Where will we be heading?

We’ll know come Saturday.  Until then there are some likely guesses.

First, given that SIGs and squads were told to carry on with what they have been up to it seems likely that we will be moving into the northeast of New Eden to operate from low sec in Caldari space.  Lonetrek or The Forge are where those groups are now, so it seems likely that a big move op on Saturday will use the Eye of Terror and cyno chain to move up through Fountain and then east into Caldari space.

Where we will likely deploy

Where exactly we will base depends on the actual target. (Base map from DOTLAN.)

The leak from Headliner on Reddit indicates that we will be assaulting Northern Coalition and Pandemic Legion in their home region of Tribute.  That would mean basing in Lonetrek, likely in Hakonen again, though maybe Taisy right on their doorstep.  We’ve been in Hakonen before, back during the summer of 2017, which led to a series of battles (example) that went against the Imperium.

That deployment had not super or titan support, so the locals were able to drop those on us with impunity.  This time we will be bringing all of the big toys so clashes may not be so one sided against us.

In favor of this target is the fact that it hits an an old enemy, NCDot, which harbors the remains of Band of Brothers, as well as Pandemic Legion.  In addition, there is already a war going on with Guardians of the Galaxy, who live in our old space in the north, and who would no doubt be keen to join in on the fun after having to pay us for peace last summer.

The path to Tribute

A war here would also draw support away from other locations in the north allow SIGs based in The Forge to continue a merry harassment campaign in the backfield, forcing Pandemic Horde to choose between defending its timers or helping its allies.

An alternative to the above would have us move a bit further along, into The Forge, from which we could attack into either PL/NCDot and their holdings in Vale of the Silent.

Into Vale and Geminate

This gets us stuck right into Pandemic Horde if we go into Geminate, pitting strength against strength, while The Vale of the Silent is a big region with a lot of targets.  Geminate, like Tribute, means a head-on assault and supers being thrown around.  Vale means the locals have to reinforce from Tribute and Geminate, but can stay based mostly at home.  It still lets GotG harass from the north end and SIGs at the south end, though both local forces would be able to respond to either more readily.

Finally, there is a possible focus on the rental income of the locals.

Where the rental money comes from

The Kalevala Expanse, Malpais, and The Spire represent prime null sec rental space from which the locals derive income.  Again, The Forge puts us about as close as we can get those regions without getting into NPC null sec space.  But those regions do not have handy NPC space for us to land in. (Otherwise there would probably already be a SIG in there.)

Going after those regions would give us a nice “going after bots” narrative, though the recently revived Greater Western Co-Prosperity Sphere, the Imperium rental alliance that operates in Period Basis, featured in the latest round of bot bans, so one might be tempted to ask when we’ll be opening a front there. (Or against Fraternity.)

The problem is that, while those are tempting targets, you cannot get a super fleet in there without multiple gates and jumps.

So I suspect that the first option I mentioned, an attack on Tribute, will be the actual destination announced this coming Saturday.  It has the advantage of being close to low sec staging as well as close to Jita for re-supply. (Now would be a good time to build up stocks if you’re a seller.)  The leak posted on Reddit was based on something said in the Imperium leadership channel according to The Mittani.  That gives it some weight, even when Mittens wondered aloud whether or not it was a ruse.

Northeast Null Sec Influence Map – May 12, 2019

(Map from Null Sec Influence maps)

My guess is that Hakonen or Taisy will be our destination on Saturday and, once the capital fleets arrive, a Keepstar will be dropped in one of those systems to kick off the conflict.  Supers will cover the initial deployment and the enemy will have to either come attack it when the 24 hour cycle finishes and the initial repair timer goes live.  They will have to either face our fleet then or allow us to setup a a difficult to assail base right on their front step.

Meanwhile, SIGs and squads will use the distraction of the main front in Tribute to harass and set times in rental space.

That seems to me to be the most likely war scenario.  However, I have no inside information whatsoever… hostile groups with spies know more than a line member like me… so your mileage may vary.

We will see in about a week.

Always Something to Clean Up in Space

After having caught the first move op back to Delve last week I wasn’t sure what I was going to do with myself in New Eden.  I haven’t ratted in over a year, and I haven’t mined in much longer than that, and have no desire to do either.  When you see those Delve numbers on the monthly economic report, I contribute nothing to those two categories.

Meanwhile the peace in the north has meant few strategic operation opportunities.  I like strat ops because the have a goal and I am a very goal oriented person.  Roaming just to roam, unless it is with Reaver, isn’t something I enjoy.

Fortunately it appears that NCDot was looking out for me.  It must be because I am friends with Matterall.  They left a couple of Astrahus citadels in Aridia set for US time zone timers, so when a fleet went up to go shoot them I was awake and ready to go.  It was going to be Hammerfleet doctrine, which is built around the Ferox battlecruiser, which meant that I would get to show off the Cordite Blossom SKIN that CCP briefly offered as a fundraiser back with the September update.

Cordite Blossom Ferox at a jump bridge

The fleet was under Dave Archer and, of course, he didn’t tell us what we were up to, just that it was a strat op.  The presence of spies and the requirements of operation security means we rarely get told much until something is already happening.  But that it was a strat op in a doctrine that is often used to shoot structures, and because there was a small carrier op under Zed Starshine going with us, it seemed like a good bet that there was a citadel out there that needed bashing.

And that we took the jump bridge to 1-SMEB pretty much guaranteed it was in Aridia.  So off we went, shepherding the slower carriers that would be used as the firepower for the shoot.  Getting there went smoothly, except for the point when somebody in the fleet set off they cyno by accident.

That wasn’t what he meant to do

That sort of thing doesn’t happen as often as it could.  But it was quiet enough in the area that we left him behind and he was able to catch up.

The Astrahus itself was being gunned, so as we orbited the structure it threw various things at us.  For the most part that kept logi awake with something to do.

Paints and webs on somebody

The unaware and incautious were in trouble however.  Small stuff had to warp off to stay safe and the few people who did dumb things, like lighting their microwarp drive when a bomb was coming in, paid the price.  But losses were minimal.  When the heard had been culled of the incompetent the gunner started in on our drones and we had to pull those and pick up with guns.  However the fighters from the carriers carried on without issue.

Unfortunately, this shoot was just for the armor timer.  There was no kill mail to be had.  The kill was set for three days down the road.

Timer counting down

Then we moved to another system and did it all again, shooting another gunned Astrahus to take care of another armor timer.

The Ferox line and a planetary atmosphere

That set up another timer for a kill next week.

After that it was a quick run back to 1-SMEB where the carriers could jump and we could take the jump bridge back home.   So I managed to get in on at least one fleet this month and helped clean up some hostile structures.  We’ll see if I remember to check for the fleet that will go get the final timers and the kills.

A Five Keepstar Day

While I was at work the Keepstars I highlighted earlier in the week were destroyed.  The EU time zone team got some shiny kills.

The Keepstar lineup on zKillboard

While I only mentioned four in my post it turns out that there was a fifth ready to be knocked off down in Tenerifis which TEST took care of.  The five kill mails:

All told that is at least a trillion ISK in losses inflicted in a single day without much in the way of resistance.

The question is now what happens next in the war?

 

Four Keepstar Targets in Fade and Pure Blind

Ops have already run in order to reinforce the remaining four northern Keepstar in Fade and Pure Blind.  The are scattered across two zones, so I ended up using the multi-region map for the area that is available at DOTLAN.

And then I flew out to take a peek at each of them just to see where the timers stood.  I have a general idea as ops area already on the calendar, but sometimes you just want to know the exact time.  So off I flew, first to C4C-Z4 and the first Circle of Two Keepstar.

Circle of Two Keepstar in Fade

From there I zipped over to DO6H-Q and the NCDot Keepstar.

NCDot Keepstar in Fade

Then I headed down into Pure Blind to 3V8-LJ to find the second CO2 Keepstar.

The CO2 Keepstar in Pure Blind

Then I made the last leg of the trip over to 7X-VKB to see the Darkness Keepstar.

Darkness in Pure Blind

All four are set to go this coming Wednesday, September 19th, at various early hours of the day.  At least early for me, sitting here on the West coast of the US.

Map of Fade, Pure Blind, and Cloud Ring – Times are in UTC

I doubt I will make it onto any of those kill mails.  But their destruction seems inevitable as northern forces draw back deeper into their own territory.  The question is whether or not there is a war once these are destroyed.  I am sure there will be some lesser structures to clean out of the area.  But once cleansed, the Imperium isn’t planning on moving in and they will stick around if CO2 comes back.  So who will end up in Fade?

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: