The Imperium’s invasion of Providence is now through the second day of its plan.
Day one, Sunday, was the announcement and the “getting there” phase of the plan. People flew individually or in convoys down to our low sec staging system while the logistical arms of the various alliances got ships up on contract for members. This was what the map of Provi looked like then.
Day two, yesterday, was the first Entosis Link module day. Structures throughout Providence were reinforced during their vulnerability windows. This is what the region looked like at the end of the second day.
Systems with the orange highlight around them are the ones where structures were reinforced during the day two operations. The total numbers, which I gleaned from the Timer Board site, are 50 infrastructure hubs, 25 stations, and 20 territorial control units, for a total of 95 structures reinforced across the 84 system in the region. (The data for this is after the cut at the bottom of the post if you want to check my ability to count… and you probably should. I just looked at row numbers in Excel.)
The plan was to try and reinforce the ihubs in every system in the region, but clearly that did not happen. And if you line up the systems that are not highlighted in orange on the map above with the Activity Defense Multiplier in the map below, a pattern emerges.
The systems that were successfully defended during the day two operations all had higher ADM numbers, which require the attacker to spend more time reinforcing structures and, in turn, allow the defender more time to form up and send the attacker packing.
So that is the big picture for day two. Not a full success, but a lot got done and some unlikely candidates showed up in space and even on kill mails.
I had to look that kill mail up because it stank of Photoshop. The Mittani and Xenuria team up to kill a HERETIC during the holy war in Provi? How does that even happen? That is Bizarro world unlikely in the extreme.
But it is a real thing. I seen it here and here and here! (As an aside, after The Meta Show interview with Xenuria last Saturday I was pretty sure he’d be in GSF soon enough. He already writes for TMC. And yes, this is something of an EVE vet test. If you know why I brought this up, then you get it. If not, you’re probably lost.)
My own response to the question, “Daddy, what did you do during the Provi invasion?” is somewhat less dramatic. As the vulnerability time windows for most of Providence were set for European time, the Entosis Link operations largely happened while I was at work and were just wrapping up after I got home and was able to log in. I managed to get in on the tail end of a Laz fleet… not even my own alliance… but spent the whole time dodging gate camps and never did end up linking up with the fleet until they landed in the staging system. (The idea of camping in a POS out in the various constellations seems to have fallen by the wayside for practical reasons.) I did enough running about, and provided some intel, so I felt entitled to click on the participation link, but I was nowhere to be seen when Entosis Link activity was going on.
Instead, I ended up having to clone jump back to Tribute. Mordus Angels decided to use this time whileThe Imperium was away to hit some systems. They reinforced the ihubs in four Circle of Two systems in Tribute last night and then started in on the station in UMI-KK, our alliance capital. So a ping went out on TNT Jabber… which I recently hooked back up… calling for a defense fleet in UMI.
We managed to chase MOA off and reset the station timer with our own Entosis Link module, then disbanded. However, MOA came back a while later with more pilots, while the second ping for a defense fleet only drew a dozen TNT defenders. So we sat in the station while our leaders dialed up GSF HQ and asked for some support. We got a small Harpy fleet down to help us from YA0-XJ, which was enough to hold the grid immediately around the station, blowing up any MOA ships that wandered too close to the undock. But their doctrine of high speed Vexor Navy Issues and an interceptor orbiting the station at 200km at very high speed hurt our ability to deter them. We did not have the fleet composition necessary to stop them.
We did eventually get our own Entosis Link module on the undock and running, blocking the MOA progress with less than two minutes on the clock. MOA sacrificed some ships to get in close and hit it, eventually blowing it up. Ships running the module can get reps, so all we could do was try to hit attackers and swat drones as they wore him down.
As it turned out, that was the only Entosis Link module we had available, so we had to sit and watch the timer count down until the station was reinforced. And ignominious defeat. If only our ADM had been higher!
After that we blocked their way back home and hunted them for a while, getting a few kills, which made us feel a bit better. But their over-prop modded Vexor Navy Issue drone ship (here is the fit from one we managed to catch) were able to pull range on us quite effectively, saving themselves time and again.
(Also depressing, The Mittani is on more kill mails than I me this month, and there aren’t even any structures kill mails any more. Must fix this.)
So we have a timer of our own to worry about. And it looks like MOA has been busy today, as more things have been reinforced since then in Circle of Two’s part of Tribute. They had best get their act together on defense when the time comes. However, those timers all have a ways to go.
Today is day three in Providence, and the plan is just to roam about camping gates, shooting ratters, and generally looking for fights while reinforcing more structures if possible. Other groups, including Brave Newbies and some of TEST, have decided to come on over to Providence in search of action, so there will be fights.
Tomorrow will be the big day. Day four, when all those timers come out and the capture events start, will be the real test of various Fozzie Sov doctrines. That will be the day when Provi Bloc can save the day or lose big.
As noted above, the list of reinforced structures in Providence is after the cut.
System Structure Owner R3-K7K IHub Curatores Veritatis Alliance R3-K7K Station Curatores Veritatis Alliance ZT-LPU Station Curatores Veritatis Alliance D-GTMI Station Curatores Veritatis Alliance D61A-G IHub Gun Fun Alliance D-6WS1 IHub Gun Fun Alliance 5IO8-U IHub Curatores Veritatis Alliance MH9C-S Station Curatores Veritatis Alliance MH9C-S TCU Curatores Veritatis Alliance H6-CX8 TCU Curatores Veritatis Alliance U-HYMT IHub Curatores Veritatis Alliance H9-J8N TCU Curatores Veritatis Alliance T-RPFU Station Curatores Veritatis Alliance F-YH5B TCU Curatores Veritatis Alliance F-YH5B IHub Curatores Veritatis Alliance 4B-NQN IHub Sanctuary Pact BK4-YC IHub Curatores Veritatis Alliance VKI-T7 TCU Curatores Veritatis Alliance C1-HAB Station Curatores Veritatis Alliance AY-YCU Station Curatores Veritatis Alliance Y-MPWL IHub The Volition Cult QR-K85 IHub Curatores Veritatis Alliance TXJ-II Station TSOE Consortium OXIY-V IHub Curatores Veritatis Alliance 9UY4-H IHub Curatores Veritatis Alliance Shintaht IHub Gun Fun Alliance 2-TEGJ IHub Curatores Veritatis Alliance HP-6Z6 IHub TSOE Consortium SI-I89 IHub Gun Fun Alliance 9-F0B2 IHub Sanctuary Pact GA9P-0 IHub TSOE Consortium F-YH5B Station Curatores Veritatis Alliance 7YWV-S Station TSOE Consortium FSW-3C IHub Curatores Veritatis Alliance 7YWV-S IHub TSOE Consortium FC-3YI IHub Curatores Veritatis Alliance C1-HAB TCU Curatores Veritatis Alliance HP-6Z6 TCU TSOE Consortium T-RPFU IHub Curatores Veritatis Alliance H9-J8N Station Curatores Veritatis Alliance 8P9-BM IHub Sev3rance DP-JD4 IHub Curatores Veritatis Alliance MVCJ-E IHub Curatores Veritatis Alliance AY-24I IHub Curatores Veritatis Alliance C1-HAB IHub Curatores Veritatis Alliance 3GXF-U Station Silent Infinity N8XA-L IHub TSOE Consortium N8XA-L TCU TSOE Consortium VKI-T7 IHub Curatores Veritatis Alliance GA9P-0 Station TSOE Consortium 8P9-BM Station Sev3rance G7AQ-7 IHub Curatores Veritatis Alliance T-RPFU TCU Curatores Veritatis Alliance N8XA-L Station TSOE Consortium TXJ-II IHub TSOE Consortium TXJ-II TCU TSOE Consortium H-GKI6 IHub Silent Infinity U-HYMT TCU Curatores Veritatis Alliance MVCJ-E TCU Curatores Veritatis Alliance X-R3NM TCU Care Factor FSW-3C TCU Curatores Veritatis Alliance MH9C-S IHub Curatores Veritatis Alliance YQB-22 Station Silent Infinity AY-YCU IHub Curatores Veritatis Alliance H9-J8N IHub Curatores Veritatis Alliance YQB-22 TCU Silent Infinity ZT-LPU IHub Curatores Veritatis Alliance D-GTMI IHub Curatores Veritatis Alliance YQB-22 IHub Silent Infinity X-R3NM Station Care Factor H-GKI6 Station Silent Infinity H6-CX8 Station Curatores Veritatis Alliance Y9-MDG IHub Sev3rance 3GXF-U TCU Silent Infinity TU-O0T IHub Sev3rance H6-CX8 IHub Curatores Veritatis Alliance KBP7-G IHub Sev3rance E-YCML Station Sev3rance B-WPLZ TCU Sev3rance B-WPLZ IHub Sev3rance LF-2KP Station Care Factor 3GXF-U IHub Silent Infinity LF-2KP IHub Care Factor X-R3NM IHub Care Factor 5IO8-U TCU Curatores Veritatis Alliance G-5EN2 IHub Sev3rance LF-2KP TCU Care Factor 49GC-R IHub Silent Infinity B-WPLZ Station Sev3rance 8P9-BM TCU Sev3rance KBP7-G Station Sev3rance YWS0-Z IHub Sev3rance TU-O0T Station Sev3rance E-YCML IHub Sev3rance Y9-MDG Station Sev3rance