Tag Archives: Fortizar

Fortizar Down in Hakonen Again

Round three of the battle to secure a Fortizar in Hakonen ended pretty much the same way that the previous two attempts did, with the Fortizar in question exploding.  I sat on grid to watch it after most everybody else has stood down.

One might well paraphrase Wellington for this fight.  “We deployed it in the same old way and they blew it up in the same old way.”

The now familiar pattern started as the timer drew down.  They first arrived with Machariels and Abaddons supported by Apostles for triage.

Battleships spreading out on arrival

Then a cyno went up and the mass of super carriers and Apostles, with a few titans in support, jumped into the system.

Hostile supers on grid

They in turn put fighters and drones on the Fortizar, stopping the timer at 13m 51s, a point from which the repair cycle never budged.

Timer stopper

We had capitals on stand-by, but did not bring them out to face the super capital gauntlet again.  No aggressive drops of dreadnoughts in hope of knocking out a few supers happened.  We stuck with sub caps for this round.

I was with the ECM Burst fleet again, hovering on a perch in my Atron, waiting to be warped in on hostiles to break their target locks.

Again my Atron swoops down upon the foe

After a few runs my security status was down to -7.1.  I am no longer safe to wander through high sec.  I will have to do quite a bit of ratting at some later date to fix that.

Our main striking force was a pair of Typhoon fleets whose progress I could mark from my perch by following the explosions.

Typhoons blowing up, they didn’t align in time

At one point both Typhoon fleets warped in on the far side of the fight, putting the hostiles between themselves and the Fortizar.  I put my camera on the fleet as it began to erupt in a near continuous series of explosions.

They did not stay on grid for long, warping off after taking quite a few losses in exchange for a few Machariels.  Our defense was called off shortly thereafter.

The fight itself was not plagued by as much time dilation as the previous two rounds, something a people on coms were quick to attribute to the fact that many of the groups in the conflict declared war on each other since the last fight.  That was alleged to lighten the load on Crime Watch, though the fact that there were 800 fewer people in local for the fight seemed a more likely explanation to me.  The war decs will likely just mean less worry about gate guns firing on people.

The battle report reflects the fact that we spent less time on grid fighting, with total losses adding up to less than 10% of the second fight and only 25% that of the first.

Battle Report Header for Round Three

The ratio of losses remained close to the same 70/30 split of the previous two fights, so we are consistent on that front.  We clearly lost the ISK war, but we drew some blood.

As a skeptical line member, whose only insight into overall strategy is what he reads in the papers, I am not sure where this Fortizar plan is headed.  It was reported that the fight managed to cover the deployment of a couple more Astrahus citadels in hostiles space.  These “roach motels,” as they have been dubbed, are set to be open to anybody, so if you want to camp in Tribute or Vale of the Silent, there are now rest stops where you can tether and repair or dock up for the night.

Attempts to return the favor by dropping citadels in Delve have been thwarted so far.

And even as we were fighting last night, another Fortizar was anchoring in Hakonen.

Aptly named “Another One”

This Fortizar is different in two ways.

First, it is in a slightly different location, since it was deployed while the one that just died was also going online.  Everybody will have to make new bookmarks.

Second, it is set to anchor and hit its 15 minute repair cycle during EUTZ, giving out European brethren a bite at the apple and some content of their own.  Will Jay Amazingness and the European members of the Imperium fare any better than we in the USTZ have done?  I suppose we’ll get the answer about two hours after this post goes live.  The fun is supposed to start at some point after 18:00 EVE time.

Anyway, as the line member space tourist, I’ll keep logging on for these fights.  It is what I signed up to do.  Join the Imperium and see New Eden!

Another Day, Another Fortizar Down in Hakonen

Last night was the return match.  After Monday’s fight another Fortizar was put down in the same spot in Hakonen.

Second Fortizar coming online

There was a Fireside chat scheduled before operations were supposed to begin, which was marred by network issues that dropped a large portion of the audience off the server.  “Something, something, fleets will be going up…” was about all I got.

Fleets did go up.  There was a ping for two Typhoon fleets and a Jackdaw fleet as well as a call for capital ships to be ready.  And there were a few special fleets forming up, including another small ECM Burst fleet, which I joined.

We were in the same Atrons with the same plan.  Since the Fortizar had been dropped in the same position as the previous one, our perch bookmarks were all still viable as well, though I went out beforehand and burned out to make a few more.

We formed up, Atrons were handed out to the people who hadn’t been on the Monday op, and went over the “how to” of the fleet.

It looked like our bookmarks might be troublesome.  The new ones I burned were a little closer in than the originals and there was a gang of five Raptors zipping around the area, not too far from one of my perches.  They got close enough to another pilot in our fleet to decloak and blow him up.  As they edged towards me I weighed the option of decloaking and warping off versus just sitting tight.  I chose the latter, which turned out okay.

The timer was counting down on the Fortizar, our fleets were undocking, and the enemy subcap fleets started landing on grid.  There looked to be two Machariel fleets and an Abaddon fleet, supported by Apostles.  Once on grid they lit a cyno and more Apostles jumped in along with a fleet of super carriers with four titans for support.  The arrival of these fleets and their supporting ships drove the roving third parties off and my perch was never in peril after that.

As the timer hit zero there were about 2,600 people in system and the time dilation was very light.  And then everybody, launched fighters, dropped drones, or otherwise opened fire and tidi quickly got down to 10%.

Opening the fight around the fort

Our little ECM Burst contingent did not have as much to do this time around.  The battleship fleets ended up a toe-to-toe slugging match, running smart bombs to clear drones and fighters.  In this situation we had to take care where we dropped lest we end up annoying our side as much as our foes.

So there were runs on the periphery and runs where we had to warp off without running our busts.  We tagged a few people, though some runs were pretty minimal in effect.

Two from my own fleet

The outcome of the Fortizar itself did not seem at all in doubt.  The repair timer was paused by damage just seven seconds into its fifteen minute count down and stayed fixed at that point throughout the fight.

Repair timer paused

So for a while I was mostly sitting on a perch, cloaked up, and able to watch the fight unfold.  Not a bad view.

TEST showed up again with their Nightmare fleet and joined in shooting NCDot, PL, and their assorted allies.  There was a sore temptation to take a shot at one of the Nightmares in the fleet, but we focused on the enemy at hand, leaving other scores to be settled later.

Its like a friend coming to your party with your ex

Then somebody noticed a couple of enemy super carriers warping off in somewhat random directions.  In a battle like this there are always lots of disconnects, and when you get disconnected your ship automatically warps off to a distant spot in space.  However, the ship is still in the game and can be probed down.  Azure and Argent, our FC, had us change fitting to add a warp scrambler and set us off to join in hunting these missing super carriers.

The first was a Nyx.  A Broadsword heavy interdictor had landed on it already and started to tackle it.

Broadsword and the Nyx

He then lit off a cyno and soon some friendly dreadnoughts started landing on grid with the Nyx.  The pilot had reconnected by then and was trying to get himself turned about and back to the relative safety of his fleet.  However, the dreadnoughts neuted out his capacitor as they oped their attack on him.

Nags on grid taking down the Nyx

I managed to get in close enough to get in a few hits… and take a few hits from the smartbomb the Nyx was running… so was on the kill mail.

We went after a second Nyx, but it was down before I arrived on scene, while a third Nyx just managed enter warp to escape as dreadnoughts were landing on it.

That seemed to be about the extent of the disconnect super kills to be had and we headed back to refit and then went to our perches to join back in the main fight.

The situation had changed some since we left.  While the Fortizar still seemed as unlikely to survive as ever, TEST had dropped a ball of dreadnoughts on grid at range to try to long distance volley faxes and super carriers.  Thi caused NCDot and PL to cyno in titans, who turned their doomsday weapons on the dreadnoughts.  The big guns were out and anybody who had not previously seen a doomsday in action got their chance as they shot dread after dread.  TEST ended up sustaining a third of the losses on our side of the battle, about 94 billion ISK, due to dreads being popped.

We only made one more run in to fire our ECM Burst projectors before we were told we could dock up.  I stayed on grid, cloaked up again at one of my perches, so see the Fort explode.  It had been a long fight for a week night, passing the three hour mark, and people were clearly ready to be done.  The hostiles were jumping out of the system even as explosions began to erupt on the doomed citadel.

Flames begin to appear on the Fortizar

The battle itself had about the same exchange rate as Monday night, favoring the foes in about a 70/30 split.  However, looking at the battle report, the total destruction was much greater, with almost three times the ISK destroyed, though only about 300 more ships were blown up.  Throwing in dreads and killing some super carriers no doubt added to the growing ISK total.

Battle report header

There also were not as many random third parties showing up.  The alliance list on Monday was much longer.

And so the battle was over.  I somehow missed getting a PAP link, but I imagine that I will get enough while we’re deployed to not sorely miss one.

The post-battle bit of “story time” where we head a bit about what happened indicated that we had dropped small citadels in Tribute set to come out at the same time as the Fortizar, so the enemy would have to choose.  They chose to kill the Fort, which would have been a major strategic asset to us, but now we have places to hole up in the middle of their territory, places where fleets can linger and dreadnoughts can safe up and wait to drop on targets.

Now we’re building replacements for many of the hulls we lost thanks to the Raitaru and Abzel we have in Hakonen, while the Jita market is booming because of the resupply efforts of both sides.  Now would be a very lucrative time to have a researched Tyhpoon BPO.

That is my own limited view of the battle.  Other reports I have seen so far:

And, of course, sitting on a perch, watching the fight, means I have plenty of screen shots.  We shall see when round three comes up.

Fortizar Down in Hakonen

The flip side of your staging system allowing you to jump into hostile space is that your enemy can easily return the favor and jump into your staging.

One of our goals is to get a Fortizar up in Hakonen to stage out of.  That would free us from a station undock that can be camped and let us set up our own market, free from people screwing with contracts and such. (The latter has happened to me.)

So a Fortizar, along with a few more Astrahus citadels, was anchored and set to come online at 02:00 UTC.

Fortizar waiting for 02:00

A fight was clearly expected and early pings went out advising people to have their doctrine ships ready and to be logged on by 01:30.  The enemy would not want us able to set up in the comforts of a large citadel.

This time around though I did not go with the Typhoons or the Hurricanes.  Asher had a special small fleet setup for some of the Reavers.  We would be going to battle in the lowly Gallente Atron frigate.

My Atron with the YC119 Yoiul skin

Fit with ECM burst modules, our job was to sit on a perch cloaked up and, when called for, decloak and warp into the midst of the enemy.  At that point we were to set off our over-heated ECM busts, breaking the target locks of the ships around us, and then warp off to our perches again to cloak up and wait for the next call.

We got out early and set up perches and cloaked up, waiting for things to start happening.  That gave me a bird’s eye view of the battlefield.  I saw our Typhoons and carriers undocking as well as the hostile battleships, carriers, and super carriers arriving on grid.

And then the timer ticked down to zero and the fight was on for sure, with the hostiles pausing the timer almost immediately.

Timer paused

The goal for our side was to keep the enemy off the Fortizar long enough for that timer to run down to zero.  At that point the Fortizar would be online, could be manned and equipped with defenses, and killing it would require the dread three cycles of attacks.

The enemy’s goal was to apply enough damage to pause the timer and then burn the structure down.  That would allow them to blow it up right then and there, no need for any return trips.

The fight itself did not go our way.  In a clash of carriers versus carriers and super carriers, the enemy was able to clear our fighters from space, leaving our carriers defanged and unable to assist the fight further.  Then the blows began to rain down on our Typhoon fleet.  Fighters chew up sub caps, so losses started to mount.  Our side was able to re-ship, but more people kept piling into the system, with the peak number in local exceeding 2,700 pilots, which also meant time dilation kicking in hard.

Local plus the expected tidi

The tidi seems a bit worse than usual, though fights in low sec space add a layer of complexity.  In null sec nobody cares who you shoot, but in low sec it has to account for your initiating aggression and modify your security status and set a suspect timer along with the usual combat timer.  (Imperium Logi King Arrendis is making the case to turn some of that off when tidi hits.)

I ended up with my client crashing twice during the fight, though I suspect that was more from memory usage than anything else.  Task Manager showed the client trying to load more and more RAM until it couldn’t address any more.  This is where having a 64-bit client would help.

Turning off some of the graphics features seemed to sate the clients need for RAM, and once I did that I was stable.  I didn’t go into full potato mode, but I turned off trails and drones and launcher effects and a couple other items.

As the battle ranged we started making our runs into the thick of things.  With each run you get a count of the number of people you aggressed.  We called these numbers out in fleet, with the range being anywhere from a dozen to over 150 hit with our ECM bursts.

I hit 72 on this run

That was an easy way to whore on kill mails.  You just have to get a hit on somebody with your area effect and you get counted on the list if they get killed.  It is also a handy way to burn through your security status.  Initiating aggression on low sec causes a reduction in that number for each person engaged, so I managed to go from a 4.8 security status to 1.1.

I ended up getting on a lot of kill mails, but a good portion of them were allies, this was in part because the fleets were close, but also because our side was dying in greater numbers.  We were losing a lot of Typhoons for each Machariel brought down.  With the carriers no longer of use and no supercaps of our own to call upon, after about two hours of slogging through tidi we were told to break off the fight and dock up.  The Fortizar was left to its fate and blown up shortly thereafter.

The battle report tells the tale.  While we got in some blows, we lost a lot more.

Battle Report Header for Hakonen

If you go down the list on our side you will see a number of people counted twice because they reshipped in system and rejoined the fight.  TEST is also counted on our side as they showed up with a Nightmare fleet to join in on the fight.

So the first shot at putting up a Fortizar failed.  Word is that the combat commanders are working on changes to the battle plan for the next run.

So far the only write ups about the battle I have seen:

Meanwhile, sitting on a perch and occasionally diving into the fray means I have some screen shots which still look pretty nice even with some of the effects turned off.

 

A Fortizar Goes Online in 1-SMEB

TODAY 23:00 MAX NUMBERS DIVORCE YOUR CHILDREN, SACRIFICE YOUR WIFE AT THE ALTAR STRAT OP, SUBS, CAPS, SUPERS, TITANS, RORQUALS. BE THERE.

~~~ This was a broadcast from asher_elias to all at 2016-08-01 18:29:53.901185 EVE ~~~

Somebody was trying to impress upon us the importance of the 23:00 op.

As it happens, 23:00 is about the earliest time on a weekday when I can possibly make a fleet op, and I was home in time, online, and ready to pile into Asher’s fleet once the official ping went out and the fleet went up.  This was officially a Proteus fleet and I got into my Oneiros again.

The fleet filled up quickly enough and a second fleet went up on Apple Pear, one of our EU TZ FCs who was up late.  His fleet seemed to be… less discriminating.  There was a call to get people in fleet, alts included, in whatever ship was to hand.  So I logged on my combat alt, put him in a Crucifier, and had him join Apple Pear’s fleet.

Meanwhile, there was a capital fleet forming up… and all of us were using the same coms channel.  While confusing at times, this is generally a sign that we are doing some sort of coordinated op.

With one fleet full, another filling up, and the caps doing whatever it is they do as they assemble, we began to undock, with Asher’s fleet going first.

Once more out of the Genolution Biotech Production station

Once more out of the Genolution Biotech Production station

We undocked, headed to the 1-SMEB gate and jumped through.  The Apple Pear’s fleet undocked, warped to the gate, and then stood to there as the capitals began to hit the gate.  The landed there in two streams, one from the station and one from the safe POS, and jumped through.

Caps landing on the 1-SMEB gate in Sakht

Caps landing on the 1-SMEB gate in Sakht

On the 1-SMEB side, once most of the caps were through, Asher warped us to a spot on grid.  Had I been more aware of my surroundings, I would have seen it on the overview.  But, as I have grown used to citadels showing up there, another one didn’t strike me as something worth noting.  But as when we landed on it, I saw what was going on.

Fortizar going online

Fortizar going online

Yeah, I know, big deal, right?  There are lots of Frotizar’s in New Eden now.  We lived under the unblinking gaze of three of them in the Quafe Factory Warehouse back in Saranen.

You can see three Fortizars on grid now

You could see three Fortizars on one grid in Saranen

But this was ours.

The Imperium has put down dozens of Astrahus medium citadels.  They were in Saranen, all over Venal, in Pure Blind, and dotted the route south to Delve.  But for us to actually bother putting down a Fortizar, as common as they may be, is something of a statement I suppose.

And we were all there to make sure it went online without a hitch.  So all three fleets spread out around it and watched it count down through its final period of vulnerability, after which it could be gunned and would require the whole timer routine to kill.

Supers in a semi-circle around the Fortizar

Supers in a semi-circle around the Fortizar

One hostile landed on grid with us during the process, but warped off quickly.  Otherwise nobody showed up to try and keep our new citadel from going online.

When the counter finished and it was live, there was some cheering.  Asher and another titan pilot shot off their lance doomsday weapons.  And Jay Amazingness let us shoot his Chimera, a sacrifice to the welp gods in Delve no doubt.  We were also encouraged to troll Reddit by putting up pictures with 1-SMEB replaced with 93PI-4.  Somebody did one that looked pretty good.  My own attempt was a bit more… raw… in the grand MS Paint tradition.

And that was that.  We had a large citadel in Delve.  It isn’t a Keepstar, but we’ll get there I bet.

Then it was time to run the whole thing in reverse, with subcap fleets covering each side of the gate as the capitals went back home.  A participation link was generated, my first one for August, and I got to click on it with both my main and my alt. (Though, since they are both linked to my forum account, I am not sure if that really means anything.  But I did it anyway.  Never not click on pap links.)

Not a terribly exciting event, but one that was good for the team.  Once we were done shepherding the capitals back, the op was done.  We were encouraged to go mine and rat in 1-SMEB to build up the ADM.  I got out my Procurer to help out, but as it turns out 1-SMEB only had two asteroid belts (one of which was already mined out, and the other was almost gone) and wasn’t spawning any mining anoms, which put a damper on that plan.

So I decided to use the time to jump clone back to Jita to list all the items I shipped there from Saranen.  More assets converted to ISK.  I also stopped to look at the TNT Delve 2016 video.  See, we’re still a thing, we have a video!

The array of ships around the Fortizar as we babysat it was pretty neat, and a number of people put up good screen shots:

And I have my own screen shots from the Fortizar op: