Showing posts with label Jay Amazingness. Show all posts
Showing posts with label Jay Amazingness. Show all posts

Tuesday, August 11, 2020

The Fall of the IGE-RI Keepstar

We had been up to IGE-RI late last week, when Asher led a Ferox fleet to try and defend the armor timer against PandaFam’s carriers and subcaps.  That went well.  Even though we lost the objective we managed to blow up fighters and subcaps by the score.

And we were told we would be doing something for the final timer, which was set to come due this past Sunday around 19:00 UTC.  So I made sure to be around and logged in as the time drew closer.

And then the time hit… and passed… and no fleet was called.

There was a ping for the INN stream on Twitch, where DBRB would be covering the destruction of the Keepstar.  Its destruction was never in doubt.  But it didn’t seem like we were going to do anything to drag out the event and make the enemy pay a bit for that kill mail.

Finally, about ten minutes after the hour, there was a ping.  A fleet was going up on Jay Amazingness with no details save to read the MOTD.  I had wandered away from my desk for a bit, but when I got back I joined the fleet.  The MOTD said we needed to be able to fly a tech II Cormorant and that we should take a travel interceptor to the IGE-RI Keepstar, where ships would be handed out.

That I could manage.  I had an Ares handy, so undocked with it and headed towards the Keepstar up in Fountain.  The way was clear… it generally is in an interceptor… and I arrived in the system.

At the Keepstar

It seemed that somebody used the fight notification tool this time around, as there was no tidi until I jumped into IGE-RI itself, a sign that it was on its own node.  And there was some tidi, though not much, as the event had already started.

Everybody docked up and Jay started trying to hand out ships to people which, under tidi, was apparently quite a painful process.  He eventually dispersed some of the Cormorants to other people to help him hand out.  I got mine and immediately put my loudest SKIN on it.

Fresh Corm in the hangar

We loaded up scripts and ammo and undocked to face the attack.  And it seemed like everybody was there to join in.

The NPCs even showed up

As with the Ferox fleet, we started by shooting some of the fighters that were on the Keepstar, though the tidi was making the game respond oddly.  Distances in my overview didn’t seem to bear much resemblance to where the game thought things were.  I was trying to target fighters that were alleged to be only 35km away, but was told they were beyond the 115km targeting range of my ship.  But they were clearly there on the Keepstar.

And the game itself went through points of pausing and then resuming, which I thought might be just me, as I had graphics turned up so the game client’s memory usage was… high.

Not possible without the 64-bit client

But other people were calling out that the game was stalling at the same time I was seeing it, so I suspect the server was having its own rough time.  And the fight carried on around the Keepstar.

Blue beams from fighters or drones

We fought for a bit, though not very effectively.  Corms are not Feroxes.  And we had to warp off every once in a while to get out of the way when they wanted to fire up the Point Defense System to kill any hostiles too close to the structure.  The PDS is indiscriminate, so you have to be away or tethered to avoid it.

We got to see the Arcing Votron Projector, the Keepstar doomsday, go off a couple of times.

The beam reaching up to some unseen hostiles

But we were not making much of a difference.  After one warp off grid, we were aligning back to return and it was decided that the end was close enough that we should all make sure to lock up and shoot the Keepstar at least once before it died so we could all be on the kill mail as well.  The fleet warp came and off we went.

And then we stopped about 300km off the Keepstar, looking like we were tethered… though at extreme range… somebody’s code though we were some place much closer I bet… and couldn’t figure out what had gone wrong.

Way off the Keepstar, but looking like we’re tethered

Then somebody spotted the Sabre on the overview and the client caught up and drew the warp disruption bubble in which we had landed.

We had been caught and the trap sprung.  A set of Chemo doctrine ships… smart bombing Lokis… landed on us and lit us up.

The smart bombs going off around us

You can see we had enough time to turn around to try and get out of the bubble, but the Sabre was ahead of us and kept us from warping off.  And in the middle of the Lokis was Pittsburgh2989, one time Imperium FC who was kicked out and blacklisted from the coalition for reasons still argued about.

Pitts comes to kill us all

A few people got out.  My ship was very slow in blowing up.  It took the client view quite a while to catch up with the situation as it stood.  I tried to motor out in my pod.  If I could just get out of the bubbles and warp off, I might be able to grab my interceptor… which cost about 10x that of the Corm… and fly on home with it.

Pod with wrecks in the background

Alas, they picked off the pods as well.  I was soon back in 1DQ1-A, and shortly thereafter I got a notification that my stuff in the IGE-RI Keepstar was being moved to asset safety.  I guess I will be picking up that interceptor another day.  At least the Cormorant was free… and I insured it, so made a little bit of ISK on the side.

The Keepstar was destroyed.  My ship was blown up.  My pod was killed.  My interceptor was stranded. And the battle report showed that we didn’t even extract much of a price this time around.

Battle report header

All of that was very much predictable.  But what I really want to know is if anybody looted the PLEX out of my cargo hold.

For whatever reason my interceptor had 1 PLEX in the cargo, and before the fight I moved that over into the Corm’s cargo bay.  If you look at my kill mail, you will see that the loot fairy said “yes” and the PLEX survived and was in the wreck.  Maybe somebody got it.  Or maybe the smart bombs killed the wrecks.  I’ll likely never know.

Monday, July 31, 2017

Covering another Keepstar Deployment

MAX DUDES RED CRAYON CTA RIGHT NOW

TITAN>SUPER>FAX>CARRIER>DREAD

WE NEED EVERY WARM BODY WITH A HULL

THIS WILL PROBABLY BE THE LARGEST SUPER FLEET FORMED SINCE B-R5 SO YOU PROBABLY WANT TO BE HERE FOR THE SCREEN SHOTS ALONE

-tiberizzle to allcaps

How could I say “no” to that ping?  Besides, it was Sunday morning, my wife and daughter were off to other things and I had no plans for the day.  So I clone jumped to the staging Keepstar, jumped into my Apostle, and got into the armor capital fleet.  The armor fleet passed 200 people, while the first shield fleet filled up and they had to roll out a second.  There didn’t seem to be any special fit required, aside from having a prop mod to speed up gate travel.

Once I got myself squared away I undocked and warped off to one of the citadels ringing the Keepstar so as not to be yet another massive object on the undock that people might bump into.  The force auxiliaries are not as big as a titan, but they are bigger than a super carrier and make carriers look like mere battleships in the fleet.

My Apostle in warp with Tiberizzle’s Wyvern super carrier

As the fleets settled down we were given a destination to gate to and off we went.  Traveling in a capital taking gates means jumping through a gate, clicking warp/jump for the next one, then running your prop mod as you align until your ship finally approaches the speed it needs to warp off.  Then you turn it off and, as it cycles down, you should warp… unless you bounce of of another capital, which has a habit of knocking your speed back down to below the warp threshold.

Then you just want to get through the gate at the far end without bouncing off of somebody as ships land in a streaming mass and ending up out of range to jump.

That gate has to be feeling the pressure…

On voice coms somebody was telling people to spam the jump button in order to avoid that fate.  I opted for the old auto pilot trick.  Since we had a destination, as I my Apostle headed to the gate I would turn on the auto pilot which would then jump me through the gate itself hands off.  You just have to remember to turn it off as you jump, as you could end up 15km off the next gate and slow boating for the next jump if you’re not careful.

Then you’re through the gate and everybody is spread out, uncloaking, and aligning for the next gate.

Capital fleet doing its align thing

We bunched up on a Fortizar as our first waypoint, then were given a new destination a few more jumps out.  There was sat on a Raitaru, bunching up in a giant mass of capital hulls.

Make room! Make room!

We sat there for a while, so I was pretty sure this was where we would be jumping from to get to our destination.  I still did not know what we were up to, if this would be my first capital op to involve a fleet action.  Things were quiet on coms and I wondered what was going on in the command channel.

Then the order came through to jump to cyno that had been lit.  The order was quickly amended to restrict faxes from jumping through, so everybody else jumped out leaving a convention of force auxiliaries on the Raitaru.

A meeting of faxes

There were complaints of tidi and bouncing and whatnot from those who had jumped.  After a few minutes that settled down and faxes were given the clearance to jump.

Entering the jump tunnel from the Raitaru

Once through I could see capitals strewn about the field, but that was all the client was drawing for me immediately.

Landing after the jump

This happens some times when you land on a grid with a lot of objects to draw.  Ships get drawn first.  After a bit though the client got around to filling out a Keepstar citadel where we were all hanging about tethered or bouncing.

There we are

You can see some titans a bit off that may have bounced a bit.

This was the point of the operation.  Whenever a Keepstar is set to go online a large capital fleet is assembled to protect it while it goes through its initial repair cycle, the point at which it is most vulnerable because a hostile force can blow it up without all that mucking about with timers, as happened with the Keepstar over in Auga about a month and a half back.

To prevent that a large force is mustered to sit on the Keepstar to dissuade any attack.  And so there we were.  No fight was likely given the forces we had on the field.

Sitting on the Keepstar waiting

This was the first Keepstar for our Imperium colleagues in The Initiative who, as it was going online, also won their match in the alliance tournament.

So there we sat.  Jay Amazingness said that once it was online we would sit out our jump fatigue before we headed home again.  That was going to be a while so, to entertain us Jay asked a pilot in a Phoenix dreadnought if the fleet could doomsday his ship if Jay bought him a new one later.  He agreed and warped off to another citadel before returning to be in range off us but at a distance.  On command all of the titans fired on him.

Doomsdays away

I did not have a very good angle setup when the doomsday fire went off, but Jay linked us a better screen shot in fleet, which I have borrowed.

Jay’s view of the doomsday fire

To stretch out the shoot the Phoenix pilot activated his Emergency Hull Energizer which boosts resists to 99%.  However, even with that the weight of damage being thrown at him was so much that he exploded fairly quickly.

Phoenix down

That left us some time to sit around and stare at the fresh wreck or take a break while our collective jump fatigue timers ran down.

Phoenix wreck lit by an explosion

As I was looking for a good screen shot of the Phoenix wreck, it was lit up by something that happened behind me.  While I missed it, The Initiative blew up an Archon on the undock to sanctify the Keepstar going online or just to join in on the fun.

After that we mostly sat about.  There wasn’t anything like a BBQ war in coms, which was probably a good thing.  With about 15 minutes left on jump fatigue we were roused out of our torpor and given a destination.  We set out to take some more gates to put us in range of home.

We had to wait a bit as there was a titan running behind.  Somebody needed a bathroom break, but only after we started out taking gates.  He eventually just jumped to us, leaving him within range of home and giving him the option to either double jump, and take a jump fatigue hit, or just wait it out and use the safe cyno later.

I don’t know what he chose, but the rest of us took the cyno once it was up and landed back at home.

Back at the staging Keepstar

Unlike the move op the other night, we were not cyno’d into the Twerk zone, there being some fear that a titan might bounce, escape the model, and end up flung hundreds of kilometers away.  I’ve seen that happen.  While the ship would likely not be in immediate danger, it is best not to take chances with expensive toys.  After all, PL keeps dreads on hand for such opportunities.

And that was it for the operation.  Another capital op for me, though I have yet to use my Apostle to rep a single ship.

John Hartley took some video of the fleet which includes us landing on the Keepstar, featuring some titan bounces, and the doomsday shoot of the Phoenix at the end.

 

Monday, March 13, 2017

Getting Home from Oasa

The ping said that if we got in Cainun’s fleet fast, there was a chance of a big kill.  The call was for the armor T3 cruiser fleet doctrine, which features the Legion and Proteus strategic cruisers along with armor logi and support.  I happened to be at my desk at just the right moment to log in, get in fleet, get into my Oneiros and undock as we warped off to a titan to get bridged on our way.

Off we go, are we committed yet?

The bridge off the titan sent us to another system where a wormhole to Thera awaited us.  We formed up on the null sec side of the wormhole, waiting for the orders to go through.  The wormhole was not fresh and there was concern about how much mass we would be pushing through it.

To this end we were asked to go to our fitting window and offline the armor plates on our ships to reduce the mass going through the whole, though I admit that I did wonder how you can turn off something like an armor plate.  Armor isn’t like a shield, it doesn’t go away when you turn off the switch.  But I followed New Eden logic and set mine offline.

Lolling about at the first wormhole

Tackle was sent through first, and they zipped off to the exit whole in Thera, through, and off to catch up our intended target.  Then the call was for command ships and logi to go through the hole and into Thera.  After we were in successfully, the DPS ships were called to jump through.  That was enough to collapse the hole, though only about a dozen ships got left on the other side.  No wormhole adventure for them and they got to head home.  That still left over 200 ships in the fleet.

Once we were warped to the out hole in Thera, we followed the same routine.  Tackle had already gone through, so the call was for command ships and logi, with yet another follow up reminder to turn off armor plates in case somebody hadn’t done it when asked the previous dozen times.  Command ships and logi went through successfully, so the call went for DPS ships to make the transition.  About six DPS ships made it through before the hole collapsed.

That left us in something of an awkward position.  A small fleet consisting mostly of logi was now in 1-HDQ4 in the Oasa region, a long way from home, while more than 150 T3 cruisers were hanging about in Thera where the direct hole home had already closed and the hole to the target was no longer available to them either.  Those left in Thera docked up at one of the stations there.

Those of us stranded up in Oasa were told to start burning to KED-2O where an Imperium Caracal fleet, which had used the same holes before us, was already engaged.  They had killed a Rorqual up there and had a titan tackled.  So off we went with Thomas Lear now leading us.  Why not?  We were already there and didn’t have anyplace else to be.  But even as we closed in on the destination system, word came down the line that a titan kill wasn’t going to happen.  The defenders had been successful at blowing up any tackle and the big ship got away.

So there we were, up in Oasa, a long way from home, 33 ships made up of boosts, lots of logi, and a few DPS ships.  We were like the incarnation of old school WoW paladins in New Eden; we weren’t going to die, but neither was anything we rolled up on.  It was time to figure out how to get back to Delve.

As it turned out, there was another Thera wormhole about 20 jumps from our current location, over in The Vale of the Silent in 9-GBPD.  We just had to get there.  Getting there though, turned out to be a bit of a chore.  Going gate to gate for 20 jumps takes some time, but that got multiplied as we went through Russian space in Perrigen Falls.  The Russians have a habit of covering gates around their space with anchorable warp disruption bubbles.  Lots of them.

The gate inside the bubbles

So for a series of gates we ended up landing 60-90km off of a gate, slow boating with after burners lit to jump through, then slow boating on after burners out of the inevitable bubbles on the other side of the gate.

Out of the bubbles on the far side for another warp

The bubbles were all around the gates, so there was no sending somebody ahead for a perch around them, and we didn’t have enough DPS to blow them up as we went. (Though I think we did destroy a single small bubble as we motored to a gate, just out of boredom and anger more than anything else… launch logi whore drones!)

The bubbles probably didn’t cost us all that much extra time, but subjectively, having to motor on ABs felt like a long time.   Ironically, tomorrow’s patch is making a change to anchorable bubbles so that they decay and go away after a given amount of time, so this might be the last time we have to drag ourselves through a series of forever bubbles.  And if our trip felt like a long time to us, I am sure the rest of the fleet wasn’t happy about it either.

While we had been gating about the northeast of New Eden, the rest of the fleet had been hanging out in Thera just waiting for us to get back.  Jay, who was with us, started trying to get them to rise up against Cainun to get him to take them home rather than waiting for us.  I have to admit, keeping more than 160 people hanging about waiting for 30 or so of us had a lot going against it.  On the other hand, our detachment was made up of the boosters and logi pilots.  Everybody tells us we’re special… everybody who just wants to fly DPS and get kill mails… so I guess it was time for them to show us just how special we were.

We made it past the bubbles gates and finally arrived in 9-GBPD where B33R was sitting on the wormhole as a warp in.  We went through and found Cainun and the rest of the fleet sitting there waiting for us.

Back with the fleet in Thera… also, the only good Oneiros SKIN

Once we were all through and back into Thera, Cainun warped us to the out connection.  There, we had a plate check once again.  Then he called out four Guardians to stay behind before sending people through.  This hole was also questionable, but there was another Thera connection option if this one collapsed.  Cainun just wanted to be sure any fleet that had to take an alternate route had some logi support.

And he was correct, the whole did collapse before we all got through.  I was through and in the system I-ME3L in Stain.  That put us 23 jumps from home on a route through Period Basis, Delve, Fake Querious, and Delve again.

Down in Stain

Fortunately, there was only a single anchorable bubble on the route home, reported by our scout, and it was down before we even got to the system where it was.  We were able to gate home without incident.

All told, that was about a two hour adventure which took some of us on a multi-region tour the length of New Eden.

Our route, Blue for wormhole travel, Red for gate travel

You could certainly find systems more distant from each other than we hit, but Oasa to Period Basis does cover a lot of the breadth of New Eden.  And it also shows how handy wormholes can be and the hazards of them collapsing on you.

Monday, August 1, 2016

Breaking into Delve

Not everybody in the Imperium spent last week wandering casually down to our staging station in Sakht.  Fleets had been active in Delve for several days, focusing on the constellation YX-LYK, and by Saturday we had already taken the system Q-HESZ.

But the first real test of the invasion wasn’t until yesterday, when the ihub, station, and TCU in the system 1-SMEB, previously reinforced, were contested.  1-SMEB was also the capital system for the League of Unaligned Master Pilots (ticker: LUMPY), which gave it a boost to its ADM, making it a tougher nut to crack.

There had been pings in advance asking people to show up and be ready for a fight.  The first ping for a subcap fleet, under Jay Amazingness, went out at 16:30 and it filled up quickly.  It was a Proteus fleet and I got out my Oneiros, which I had just run down from Saranen on Friday, and joined up with the logistics contingent.

Once that fleet filled another went up, and another subcap fleet after that.

We undocked after only a short wait.

Emerging from the Genolution Biotech Production station

Emerging from the Genolution Biotech Production station

We held on the gate to 1-SMEB and waited for a bit.  Then a fourth fleet showed up to pass through the gate.  It was a fleet of capital and supercapital ships, jumping into 1-SMEB for the event.

Once they were through, we jumped into 1-SMEB ourselves, then into 6Q-R50, and then into RCI-VL, where we set up around the MJXW-P gate, which seemed like sort of an odd, dead-endy location.

However, it turned out to be the right place, as the hostiles fell on us there, starting with the Pandemic Legion FC Killah Bee, who landed on grid prematurely and was immediately targeted.  I even managed to get an ECM drone on his, so as to get on the kill mail.  After that though, I let my drone take its own course as there were reps to be applied as the two sides closed and got stuck into each other.  NCDot and PL had a T3 fleet, which formed the bulk of the opposition, while the locals, led by LUMPY, were using Gilas.  On our side there was the Proteus fleet, a Confessor fleet, and Asher’s Cerberus fleet.  Bubbles were up to hold the foe in place.

The fight develops

The fight develops

In the middle of all of that, a cyno went up.  As I watched, a single Wyvern supercarrier landed on grid.

A wild super suddenly appears!

A wild super suddenly appears!

Time dilation was already hitting hard, so the capital fleet jumping in on top of the fight unfolded slowly.  Soon, however, I was in the middle of a lot of big ship.

My Oneiros in the midst of a lot of caps

My Oneiros in the midst of a lot of caps

With the presence of a capital fleet on grid, the fight went from a brawl to trying to knock off as many hostiles as we could before they could get away.  I even got to see one of the new doomsday effects as one of the titans  We even got an official observer when ISD Lunaire Elois showed up in a Polaris Inspector Frigate to watch the supers in action.

Somebody has come to watch us

Somebody has come to watch us

That was towards the end of the fight and, as usual, a couple of pilots lit our after the ISD ship, only to find its performance envelope was well beyond their ability to catch.

Meanwhile, our foes escaped as best they could and that was about it for big fights for the day.  All told, that was about 90 minutes of time from undock to the caps heading back towards 1-SMEB where they formed up on a gate to smart bomb the Pandemic Horde and Mordus Angels frigates and interceptors that were in the area.  The battle report for the fight unsurprisingly shows the ISK war going in our favor, though not that much ISK was expended given the values of the fleets on grid.   However, the totals and participants keep changing when I go back to look at that report, so I am not sure how far to trust it.

July 31, 2016 RCI-VL fight

July 31, 2016 RCI-VL fight

It did seem that the majority of the hostiles were not Delve locals.  They must miss us up north.

With the fun over, the work began.  It was time to play the Fozzie Sov game so, over the next few hours we spent time running entosis link modules over command nodes in order to take ihubs, stations, and TCUs.

A command node in "action"

A command node in “action”

There was a bit of see-saw on a couple of the objectives.  At one point LUMPY was at 95% for the 1-SMEB TCU.  However, they seemed to give up before they got that last 5%… though with us roving through the constellation in force, I guess I can understand why… and the actual command node objectives were left to us.

The only opposition was a gang of interceptors that were dropping on nodes to try and break lock on the nodes to slow things down.  This was aggravated by our decision to use force auxiliaries… fax machines… for entosis work.  If I understand correctly, we did this because they were supposed to be immune from ECM while sieged.  However, this turned out to be only true for directed ECM and not area affect ECM burst.

So we ended up with the worst of both worlds.  Fax pilots had to endure the capital entosis warm up cycle penalty both when they started in on a node AND whenever an ECM burst broke their lock.

Fax machines continued on, but there was also a call for subcap pilots to come out and run entosis links as well.  By that point our fleet was split up by wings and sitting on nodes in a system where no hostiles bothered to show up, so I got out my alt.  He happened to have a Rapier fit for solo entosis work, so I ran him out to our system and put him on whatever nodes were available.

With multiple objectives in play, coordination was… not very well coordinated.  If the goal of Fozzie Sov was to reinforce the officious “spreadsheets in space” aspect of EVE Online, then op success, because this sort of event pretty much requires some master spreadsheet coordinator to run with any efficiency.  Instead we had multiple fleets on multiple coms and people going here and there.  On a couple of nodes I was running a fax machine would show up, having been assigned the node.  I would convo with them and tell them to let me know when they had spun up through their initial cycle, after which I would fly off to another node.

But at least I was out doing something with my alt.  The majority of our fleet was just sitting around watching nodes get wanded.  As I have said before, this is not engaging game play.  You don’t see ISD ships flying out to watch people conquer sov.

Asher, on his latest podcast, had some idea for updating Fozzie Sov to make it more interesting, or at least force more fights.  But it seems like CCP, buoyed by the cheers of people who don’t actually engage in sov warfare and who, in some cases, seem to actively dislike sov null and its residents, will not be revisiting Fozzie Sov for the foreseeable future.

Life in sovereign null sec.  We’re told get too much attention paid to us one day, and then on another day we’re blamed for the PCU drop because we’re not warring hard enough to keep people’s attention.

On the bright side, hours of entosis work… I spent 3 hours on it myself after the initial fight before decided I wanted to do something else for the rest of the day… did get us some ihubs, and TCUs, as well as freeporting a couple stations in Delve.

The result of Sunday's work

The result of Sunday’s work

The Ministry of Truth even put out a song about the fall of LUMPY in Delve.

So the conquest of Delve seems to be off to a good start.  Now we just have to hold what we have taken while doing the Fozzie Sov shuffle in a about a dozen more constellations.

My screen shots from the day collected up into a gallery:

Emerging from the Genolution Biotech Production station The fight develops A wild super suddenly appears! My Oneiros in the midst of a lot of caps Lance doomsday activates Somebody has come to watch us A Minokawa fax machine o Supers orbiting a gate at 10km Shiny silver Avatar skin