r/Eve • • 1d ago

Shamless Self Promotion Shameless Saturday - November 21, 2026

3 Upvotes

Hello and welcome to Shameless Saturday.

Today you're welcome to shamelessly self promote your site/video/stream/product etc provided that it's related to EVE Online and your self-promotion to interaction ratio is 10:1 (1 self promotion link for every 10 normal interactions.) Accounts should also be a month old and have prior interactions with /r/eve.

Now what are you waiting for? Go out there and sell your ~~soul~~ self!

#Don't forget to check out this months contest: https://redd.it/nhxbxs


r/Eve • • 3d ago

Weekly /r/Eve No Question is Stupid Thread - November 19, 2026

6 Upvotes

Thread comments will be sorted by "New" by default so the newest questions are at the top.

Newbies / Returning players please visit our newbie-help channel on the /r/eve discord: https://discord.gg/uHpxFaA

Alternatively check out reddit.com/r/evenewbies

Useful Links:

#Don't forget to check out this months contest: https://redd.it/nhxbxs


r/Eve • • 50m ago

FCplease Mockup of how to add relative health capacity to HP bars without losing fixed position

Post image
8 Upvotes

Image mockup represents a frigate with 500 hull hp, 500 armour hp and 2,250 shield hp, with each "cell" being 250hp

This is similar to how the current capacitor works, and encodes far more information than the new HUD proposal, as the new hud proposal only tells you relative raw HP of each, and doesn't tell you any information of the *true* raw hp of each.

And raw HP is mostly low value information as many ships are resisist or active tank. This design encodes both relative and raw hp while retaining the fixed ratios for passive/resist/active fits


r/Eve • • 9h ago

Discussion Playing with the new rigs. Will try this setup and see how it holds up to my other passive RSs. I have 3 RSs, so not a big deal lol.

Thumbnail gallery
32 Upvotes

r/Eve • • 13h ago

Discussion Have always loved the Tengu, really enjoying this new fit for PvE.

Post image
64 Upvotes

r/Eve • • 18h ago

Low Effort Meme Memes of the olden days

Post image
127 Upvotes

r/Eve • • 18h ago

FCplease Botting has got to stop!!!

78 Upvotes
FCCPLz - sort by actual ban count, not reports

As you can see, FCCP continues to design gameplay that encourages bot-aspirant behavior, celebrating Capsuleer #1 for their massive number of (automated?) spurious bot reports, while barely acknowledging Capsuleer #10 for their highly targeted and accurate reporting. Even Capsuleer #3, with their 1.2% ban rate, is shown as "better" than Capsuleers 10 and 8.

While botting bot reports is certainly emergent gameplay, I think we can do better.

I propose a simple change to the report: sort metrics by number of bans or by descending ban% so that we acknowledge value, and not some troll botting bot reports by sitting in Jita and reporting everyone who talks more than once per hour in local. (edit: what I meant to say was take the top quartile of bans by count, sort by descending percent, and show the top 10.)

Bonus points for disabling the bot report feature for anyone with a ban rate under 10% - that's probably a worse ban ratio than could be achieved by reporting every player in local as you cruise through any given region.

Double-dog bonus points for giving the #1 reporter by count each month with a PLEX bundle.


r/Eve • • 25m ago

Discussion So, these new Synchronizer Rigs, really trying to figure out how they are better in any real way but so far they really aren't all that impressive. Like to hear others thought on them.

Thumbnail gallery
2 Upvotes

r/Eve • • 1d ago

FCplease Me trying to read my ship's velocity with the new HUD

Post image
201 Upvotes

Seriously FC surely you can do better than this...

When your wife said it was too small to be of any use when things get heated, she wasn't joking.

Does your UI team really think that ship velocity is somehow the least important piece of information during a fight or indeed even in PvE? Having to "focus" to read it whilst in the midst of a fight is no fun at all. It really is quite high up on the "shit that changes a lot and is important to know" scale.

Just to make it very clear to you FC, at minimum two things need to happen:

- The text is currently so tiny that your average player (i.e. a 50+ year old) has to focus / squint to read it. Make it bigger. Quite a lot bigger. So that in the heat of a fight, we can quickly glance and know our velocity.

- Just to really fuck us over whilst we're panicking in a fight, you decided to make the text a 1/4 grey color against a 3/4 grey background. Why? Do you really hate us that much? See the contrast and huge emphasis you've put on that big static glowing white ring that doesn't really do much and doesn't change whilst you're flying... That's the level of contrast the very important speedometer needs.

As a bonus and if you're serious about making the HUD better, you could also move the speedometer text to a more prominent position rather than tucking it away at the bottom as if it's an after thought.

I've tried the new HUD for a week now and whilst I can probably get used to most of the other changes, this one thing is a deal breaker for me so I'm back to the classic for now.


r/Eve • • 20h ago

Propaganda Are you due a refund?

Post image
54 Upvotes

If you are due a refund on a failed contract The Scope is launching an investigation. Please comment below.


r/Eve • • 1d ago

Low Effort Meme Dear FCCP - May I make a counter-point to why we should keep the original "medallion"

261 Upvotes

Let's be honest - everyone understands what these health bars mean and why all of this fits so well together.


r/Eve • • 13h ago

Low Effort Meme You should never explain the joke... ok, I'll explain.

Post image
12 Upvotes

r/Eve • • 23h ago

Discussion I’m begging the new CSM- please work on fixing turret tracking numbers.

58 Upvotes

I don’t care if the numbers get displayed as degrees/second of rotation, I don’t care if the numbers are expressed in radians, I don’t care if I have to do math in my head every time I’m trying to guess at a firing solution, literally any option that has some relation to your own ship’s vector, the opponents ship vector, and the range between the two would be better than the current stats we’re given.

If you don’t know what I’m talking about, when you hover over your turret and you get the turret tracking number, that number to my understanding only exists relative to all other turrets.

That’s to say, they only exist to measure one turret against another, a small blaster has a higher number than a capital artillery piece, and everything else falls in between. It’s useful for a quick ship comparison, “ah, these guns track twice as well as those other guns” but you cannot look at the in-game numbers and infer anything useful about how you’re supposed to fly for tracking unless you have a large amount of prior experience with other weapon systems.

You can never find out for example how close you need to transversal match a target, or what your minimum effective weapons range is based off of the in game numbers provided, and it’s easily one of the most obfuscated stats in the game for no good reason.


r/Eve • • 12h ago

Question Project Discovery Oddity

7 Upvotes

I think if there was a second cluster I should see a second "Bump" in the x axis sum graph? ( what I out in, in Red) I guessed that there was a second cluster without any more evidence that the density of points. Would have seen the bump if the graph was logarhythmic?


r/Eve • • 16h ago

Question What ships are best for me?

7 Upvotes

I'm coming back to Eve after a long hiatus and I'm wondering what ships I should be looking to fly in. I've got 70 million skillpoints but only 2 billion isk. I can fly every T2 frigate and destroyer except logi frigates and command destroyers and I can fly every T1 cruiser to level 5.

I am trying to get into angel's factional warfare and grind LP for credits with a fight to interrupt it every so often, and when there isn't an insurgency I did a lot of cloaky exploration.

I'm interested in nano gang shenanigans but I don't have the money yet to afford bling. I've got myself into a kitey pulse Navy Omen that I was hoping to use to grind LP and occasionally get into fights pledged to angels. My other considerations were a Navy Exequror, AB pulse retribution or even interdictors. I am also interested in robbing an ESS every now and then.

What ships should I be looking to getting into? I want to leverage my high skillpoints without spending a ton of isk and make some money doing FW.


r/Eve • • 11h ago

Question BRM significantly more dynamic in the last week

3 Upvotes

Has anyone noticed BRM in systems changing quite a bit from day to day lately? I've ratted in the same system for 2 months and it hasn't changed at all. We've had 600 man battleship brawls where 250 ships died and it didn't budge 0.1%.

Now I've run two forsaken hubs with no one else in system and no other heavy ratters for the large portion of the day I was online and watched it drop 9% while warping to station after the second site. The system has dropped 25% in the last week or so. No smart bomb ratters, no one five boxing ishtars 24/7. Me and another guy running a few anoms a day.


r/Eve • • 16h ago

Low Effort Meme The Campaign is How Long?

7 Upvotes

When the current campaign launched, miners made 2% progress in a week. On pace to complete the challenge in a year.

FC pivoted, and now the mining campaigns have done 50% in week. On pace to complete the challenge before December.

The campaign is scheduled to last 2 months. Is player behavior really this unpredictable?


r/Eve • • 13h ago

Bug Is security status / standings broken? Being shot at in hisec by a faction while I have positive standings with them (evemore, +1,27) and -1,7 sec status

4 Upvotes

Title. Tried loggin out and in, changes nothing


r/Eve • • 22h ago

Question How to deal with frigates?

17 Upvotes

Ok so for context I have been trying L4 Missions lately and there ist something I was wandering. How do you deal with some of the frigates that web and scram you cause I've never seem to do any damage to them? It is my first time flying a bigger ship like a Battleship so i am not really familiar with stuff like this. I even lost a ship recently cause of them (still hurts a bit).


r/Eve • • 23h ago

Battle Report I came back for a night, and I killed and died. Day 1 of a solo hobo

17 Upvotes

I got a message from FFCCPP: free omega.

I hate those, because they are essentially a small tease: "you want to come back," "you need to get in your ship," "you need to kill, and die, a lot...."

I logged in. I took the 7 day Omega offer from the NES store. I walked my Armageddon from the LDXQ freeport toward C-J, and walked into my old faithful: my Dawson's Christian, my The Dude, my 1v1mepls, my Stabbie Feet Tissues.

Drugs, filament, go, and I arrive in Malpaise at approximately 2100 EVE time.

I change my overview, I check my bindings, I organize my HUD, D-scan, probe scan, etc., all during the 19 jumps to HOLD MY PORBS space.

There are two blues! They're camping around their staging, neat.

So I start shaking my tail feather. Eventually, we get some glory: a Retribution, Tengu, and a future Cyclone join us at the gate.

We nuke the Retribution together. He tries to say, let's leave, and I stay to nuke the Tengu. He stayed long enough to aid, but then the Cyclone drops.

He says "bail," I say "nah," and me and the Cyclone go head to head for a solid minute of brawling. Both of us are dipping into claxon siren wailing of our hull. The Capacitor is Empty a constant refrain from my robot brain. But he has two XLASBs and I have balls, and time is on my side. Eventually, as my time begins to run out (hull, no paste in the ancil, I'm now bleeding constantly into hull), the Hecate asks if I need help?

Yes. Thanks.

I later die on another filament. The Khiz is super cool.

---

I go out again after a short bio break. I end up right where I belong, in Northern Cooperative Dot Matrix space.

I head over to their staging and shake my butt, and the locals get happy to see me.

One offers me a 1v1, and it's a scyfi vs sfi; this is a 50/50 tossup. If the Scyfi is HAM, I die to 800 dps. If the Scyfi is Medium Autocannons, I die to kiting (if he has dual nanos). He was neither, and I score the kill.

Wife aggro means I die to taking a fight I should have never taken, against the SFI's hard counter (cap issues): an Ashimmuuuuuu

---

Am I back? I guess I have seven days to answer that question, but if EVE Online provides me this sort of content at a consistent 2-3 times during those seven days, I'll be back.


r/Eve • • 1d ago

Art Manticore and Oddyseus watercolours

Thumbnail gallery
201 Upvotes

r/Eve • • 21h ago

Question Moving through camped warp gates

7 Upvotes

Hey. I've been moving all over the map just to see it. Now I'm going from Amarr to Jita and AHBAZON is between us. I'm in an Astero and sold off most of my loot in Amarr but still have 100 mil of stuff I want to keep. I've done a bunch of research on gate camps over the last few months I've been playing again. And there is one QA research Q I've posed the AI that I've never been satisfied with.

When I approach the Ahbazon system it's easy to get through. When I get into the Ahbazon system it's also pretty easy with my sub 2.0 align time in the Astero. But does that align time help me when I exit Ahbazon (on the Ahbazon side of the warp gate)? Or is that where I face my greatest danger? Does my align time matter there?

Thanks.

ADDED LATER - thanks all. it worked ... this time. Warped to far side of gate, warped in and there were campers using smart bombs (in the last hour anyway). I feel safer now which I'm sure is quite situational.


r/Eve • • 1d ago

FCplease FCPlz add Pirates Synchronizer BPC to the loot table of Pirate Data sites in WH

Post image
29 Upvotes

Do you remember the era when faction control tower BPC was a jackpot of them?


r/Eve • • 1d ago

Battle Report Deteriorated Alliance Tournament XXII AAR

40 Upvotes

Hello, I'm Cue Cappa, current CEO and team captain of Deteriorated. Inspired by the Tuskers AARs of the previous two years, I was peer pressured into writing our own. This will be a pretty long post, hopefully formatted to make it readable.

What the heck.

Still not sure how we got here, but I guess a decent amount of luck, some mindgames, a whole lot of effort and a very positive team mentality. This whole thing technically began in 2014, when most of our original core members met, but I don't want to make this too long. You can read more about it in Matniz's writeups from his perspective: Part 1, Part 2, Part 3. Part 1 contains history and ATXX, part 2 is AT21, part 3 is this year.

Now, originally I wanted to do 2 AARs, one for prelims + main event Saturday (11 matches total), the other for just Sunday (13 matches). But two posts is boring, and Erdinhok already covered the prelim matches pretty well in his writeup here: A tale of two victories

So instead, I'll just talk a bit about general thoughts for this year, and then do my POV analysis of all of our seventeen main event matches. Tuskers had it easy with like 10 matches last year.

Before prelims preparation:

Before prelims, we did on average a bit under 4 scrims a week. From early on a decent amount of our focus was on medium gunspam, as a lot of good ships for it were discounted, while the triple battleship comps that can statcheck it were nuked (by the fact that 3 battleships weren't allowed this year). I'd like to add here that historically, in the previous ATs, we were terrible at medium gunspam, and never really practiced it. 

Another archetype that's always worth checking for value are the two rushes, AC rush and HAM rush. Before prelims, we slightly preferred AC rush, but neither felt good this year. We tried Enigma as well, but quite late into the pre-prelim scrim period, so we weren't feeling that comfortable with it. We also had a comp we were pretty sure was a hard counter for Enigma, in case we ever felt that we'd be facing it based on the bans. We had some other more control-focused comps ready as well, but due to the low number of bans, we felt they were vulnerable to too many archetypes. The best ban strategy seemed to be to ban generically strong ships you don't plan on using. Which coincidentally means that the best overall option was to run a hard-to-ban jack-of-all-trades comp that can with good execution handle most situations. Hence, medium gunspam.

As I said, I won't go into detail about our prelim matches. We faced some tough opponents, and we made plenty of mistakes, but we played just well enough to make it to top 16.

After prelims preparation:

After prelims, it was time to both figure out the uniques and to figure out which flag we wanted. I could write an entirely separate, really long post about this year's allowed AT ships and the balance around them, but I'll shorten it here. 

Cobra, Sidewinder, Geri bad. Cybele tested, but overpointed. Shapash usable. Skua good. Bestla and Anhinga both crazy in their own way. Originally, like most teams, we thought Anhinga would be the boogeyman of the tournament, but unlike some teams (as far as I've been informed) we actually got to practice with and against it a decent amount. It fit well into shield rush and kite, and could be used in enigma as well. It definitely makes all of those comps better, but it never felt like the boogeyman its stats said it should be. 

As for the Bestla, one late night, Lord Jaxom and I sat on comms, and he told me "Hey, check out the stats on this HAM Bestla". And so we revisited HAM rush, and it was good. Specifically, in the very first scrim where we tried the Bestla rush, we brought it against a very good gunspam team, and it won convincingly. In the same scrim, they brought a very similar Bestla rush into our gunspam, and again the rush won very convincingly. So from here on out, our conclusion was that it auto wins against gunspam. And with further testing, we refined the comp, and found it doesn’t really lose to any matchup (except Zarm) unless we mess something up.

For the flagship choice we knew most people would pick the Navy Armageddon, and just like in AT21 we wanted to be special, so we were testing the Barghest and the Vindicator. Now, you have to understand, it's really hard to convince me to run shield comps. I think in the recent years they're generally weaker than armor comps, with the exception of rush. They sacrifice too much ewar *and* protection from ewar. But we're not stupid, and the thought of a ship that can fit into the same types of comps as 3 different very good uniques was very tempting. So we tried a bunch of Barghest comps, both shield and armor, both with uniques and without. I ended up liking very very few of them.

The Vindicator, on the other hand, opens up some comp archetypes that aren’t as strong with most other flags, such as our favourite Widow/Vindi comp. Another advantage of picking the Vindicator was that in AT21, we were the only team that ran it and in AT22, we were one of two. The other being Rusty Hyenas, who were also our scrim partners. So we were already very comfortable with the general archetypes that the Vindi allows, while most teams wouldn’t have gotten to practice against it as a flag for the past two years. Plus I really just like the ship, I mean who wouldn’t? So Vindi flag it is.

It bears mentioning here, after prelims, our plan of 4 scrims a week hasn’t changed, but our partners did, and organizing the scrims with only 16 teams left, spread across 3 timezones, and avoiding the ones that we might meet early? Absolute hell to schedule.

Without further ado, the Saturday best of 1s.

Match 1 - Platinum Sensitivity (1-0):

Going into the first match of the main event is also always in at least one way the most stressful. You don’t know how good your read on the meta is, you don’t know what your immediate opponent was up to in the past 7 weeks, lots of missing information. In short, we didn’t know what to expect from Platinum Sensitivity. We’ve looked at their prelim matches, and we weren’t too impressed by their performance there. That said, we didn’t want to underestimate them, so we banned some generically good ships and declared a unique. They in turn, did not declare a unique, and they banned the Anhinga, so with Bestla HAM rush fully open we decided that was probably our best option for a comp that can handle nearly anything. PS decided to bring a flag ArmaNI drone neut comp, despite the Eos ban.

Landing on grid we felt quite confident, some of our scrim partners loved running drone comps into us so we had plenty of practice with the matchup. That said, the first thing I did was a dumb target prioritization mistake, on top of that we ended up not screening very well for our Scimi, so we traded as poorly as possible for the first 2 or so minutes of the match. We corrected quickly enough to win the match, but not quickly enough to save the Bestla. And big props to Platinum Sensivity, I don't think they could have played the match any better than they did. They went on to knock out PGR, Tuskers and Barcode in the loser bracket. We also did warmups with them come Sunday morning, cool bunch of people.

Match 2 - Psychokids (0-1):

Going into Psychokids, we expected them to bring their flag. We’ve seen a few Bargh flag comps in our scrims, some armor control, some shield HML kite, so we opened, once again, with generically good bans. We banned the Zarm, but what caught us by surprise was that they banned both the Guardian and the Oneiros. So armor heavy control was now suddenly way less likely. My crucial mistake here was banning Anhinga instead of Bestla. We thought they might ban Bestla since we ran a Bestla rush in the previous match, but they didn’t. And since we lost ours in that match, we unfortunately didn’t have a spare at this point in time. With Bestla open, we didn’t feel comfortable fielding our flag, and decided to go with a fairly generic armor gunspam instead. We expected them to bring a shield HML kite with flag and Bestla, and therefore warped our DPS ships to 0.

This was the correct decision, as that’s exactly what they brought. We wasted some valuable time trying to pop Jackdaws early, didn’t intercept their Scimi well enough, and after we killed the Scimi and their low end I fumbled further target calling. They slowly out-traded us, and so to the loser bracket we go.

Match 3 - We Form V0LTA (1-0):

For V0LTA, we wanted to run a particular flag Vindi comp. It was the loser bracket, time to use it. We were hoping that showing it here and (hopefully) winning convincingly would influence the rest of our loser bracket run. We just didn’t know at the time how long that run would be.

Our plan was to ban similarly to what we normally ban, plus the Kitsune because V0LTA use it in their gunspam, but since we had last ban here we’d leave Zarm open if possible. We knew from their prelims match with Tuskers that they’re not afraid of leaving it open and running a Zarm gunspam setup. They, for some reason, opted to ban the Guardian and Oneiros somewhat early, which left Zarm as the only t2 cruiser logi. So after the regular ban phase, we intentionally did not declare a unique, to deny them the option of banning the Zarm as well in the extra bans. We felt really strongly that this would force them to bring a Zarm gunspam, since no shield comp can really deal with a Zarm, most drone comps can’t deal with it either. This let us bring our favourite comp, 2 years in the making, the Widow/Vindi/Zarm combo. And we skewed it towards anti-gunspam. The comp is a bit of a Catch-22. You’ll struggle to kill the support ships while the Zarm and Widow are alive. You can’t kill the Widow if some of your ships are tackled, and the Arbi and Zarm are still alive. You can’t kill the Zarm… etc etc, you get the point. Sure, it’s possible to deal with the comp, it's not invincible, but unless you’ve practiced against it, it’s not easy to do. Especially when you have 6 dps ships and we are TDing 3 of them.

Their gunspam was also skewed to be a bit anti-Vindi, with the inclusion of the Phobos. So the start of the match was a bit of a waiting game. They sent the Phobos ahead, and the Phobos and our Vindi stared at each other outside of tackle range, neither wanting to come closer. They decided to pull range, gathering somewhat close but not on an MJD beacon. Not sure if they were planning to do a jump play or not, but either way, by happy accident, I decided to fit a self-MJD on the flag in this particular match, and with them grouping up about 100km away, I happily jumped straight into their entire fleet landing 8km away from their Zarm. Now, that ship being what it is, it still took nearly 5 minutes to kill, which gave them plenty of time to adjust, and they decided to mostly go for a logi trade. If they had fully committed it might have worked, but initially they left their PNI and Phobos to try and bump me away from their Zarm. I don’t know why they didn’t try to bump the Zarm instead, possibly towards the beacon, it’s much lighter, but it is what it is.

Props to the rest of my team here for both reacting quickly to my impromptu jump, clearing the rep drones from their Zarm, and screening very well for our own Zarm. The match ended 200-0, but in reality it was closer than the score implies.

Match 4 - Ragequit Cancel Sub (1-0):

Ah, the Anhinga incident. Our bans here were finally very different because we wanted to run something very different, our double Barghs. We intentionally left Huginn/Rapier open, and started banning some common gunspam ships instead. The idea is, we have a flag Vindi, if we leave Huginn/Rapier, and ban some gunspam, it'd push them into seeing Enigma as a really strong open comp. Their bans to me seemed like just generically good bans, and very much not targeted at us or any particular strategy. After we both declared a unique, and both banned the Bestla, leaving the Anhinga open, we were now very sure they would run Enigma, if our read on the meta was correct. This made us confident in bringing our double armor Barghest comp. They caught us slightly by surprise by bringing… I think VLD won’t hit me if I call it a shield Enigma. Basi, Huginn, 2 DPS ships and a lot of damps. It seems to me they were expecting us to bring a more standard armor Enigma, and they were hoping to damp out all the ewar and favourably trade the DPS ships. Unfortunately for them, our Enigma counter also counters the shield version.

Usually, in most comps, I was the Anhinga pilot. Unfortunately, in this comp, I had to be a Barghest pilot, which left Cal in the uncomfortable position of flying a 370b ship with not enough practice. With that in mind, I am going to now rant a little.

So, we’ve reached the point where I talk about what happened in the match itself. Well, the match started, and my Anhinga pilot got primaried. In his brilliance, he decided, “Hey, if I’m primaried, I should click this button.” And so he clicked the forbidden button. The forbidden button is there in case the opponent brings a comp you can actually outrange. It also should be pressed with great care, after you are sure you are facing the right direction (he was), and you are sure you won’t get bumped in the immediate future (well, well). Furthermore, if you are fit with a 100MN, and the opponents use missiles, and they are not in web range, and are in a low DPS comp? Do not the button. Rant over. My Anhinga pilot jumped into the enemy fleet. I don't blame him though, we checked vod, he got bumped, shit happens. He jumped, did some damage to their Basi, and died 35 seconds into the match. That's about 10b isk/second. Thankfully, the comp difference was too big, they struggled to prevent our Barghests from finishing off their Basi, and after the Basi was down, everything else was pretty quick cleanup.

---

Before I start getting into the specifics of the Sunday matches, I have to mention here. Huge thanks, and props, to the entirety of my team here. Whatever dumb idea I had, or whatever gut feeling I had, they were fully supportive and positive about. They'd discuss the bans, give ideas and voice opinions, but I never felt pressured, and whatever decision I ended up making they supported. I think this was crucial. It allowed us to make draft and certain weird warp-in distance decisions with confidence.

---

Paper Numbers (2-1):

Between Saturday and Sunday, I only managed to sleep about 4h. I thought I wouldn’t have trouble sleeping, because at this point even if we lose we already placed top 6, which we were very happy with. Despite that, I started anxiously thinking about how to actually beat Paper Numbers. My expectations were low, we scrimmed them every week before prelims, and they consistently beat us, at least in the prelim meta. We had one significant advantage though, our flag was still alive.

Match 1: Enigma near-mirror

I decided to open the series with a comp we haven't shown before. Well, realistically, if they had left the Barghest open we'd have gone with our dual Barghs again, but I suspected they'd ban it, and they did. So Enigma mirror it is. We didn't practice it often, and especially not in mirrors, so we were not expecting to win the match, but it would provide at least 1 great avalanche ban, the Huginn. We both declared uniques, they banned the Anhinga and we banned the Bestla, so we somewhat expected them to bring a Skua enigma that we've seen in a scrim once before. Instead they brought an interesting variation with no unique which involved a Curse, which caught us by surprise. We brought a pretty standard Enigma with no unique as well.

Now, because we scrimmed them before, we made some assumptions on how they fit their Enigma DPS ships, which made it seem like a good idea to run in and try and trade the DPS. And despite the casters praising their Griffins, what really caused issues for us was the Curse. It neuted out our Muninn, and the moment it did they primaried it, and with no cap it died before through Guardian reps very quickly. Even before this they established some pretty good control, we messed up resebos, so the moment the Muninn died that match was already over. Soon after they killed my Claymore as well, so I called WF in local, asked for a reset, but unfortunately they said "next", so we moved on.

While the Curse and us not taking it seriously enough won them the match, it gave us a second perfect avalanche ban. We banned Curse and Huginn, they banned the Keres.

Match 2: Bestla rush vs Geddon gunspam

With Huginn and Curse out of the picture, we prepared our usual set of bans which are great for both our flag comps and our usual favourite, Bestla rush. We expected either a gunspam or missile kite out of them, and they brought a variation of gunspam with a full neut Geddon. We both declared uniques again, they banned Anhinga again, we banned Cybele. The Cybele ban was part mindgame, part not. We wanted to ban a ship that was neither Anhinga nor Bestla, so if they ban either we can use the other. And the mindgame part was, well, the Vindi really wouldn't like seeing one, so maybe it nudges them into thinking we'd bring it. It certainly worked on the analyst desk. We of course decided to bring the Bestla rush instead (which was FC Overload's initial theory, so props), which we were reasonably confident could handle either of the things we expected from them.

And, it would have handled it confidently, if we hadn't had an oopsy in the middle of the match with our logi pilot deciding he'd had enough of getting neuted and preferring to boundary instead. But at that point the match has already snowballed enough in our favour. Close match, but a win is a win, and the Bestla lived. Honestly, not much to say about the rest of the match. We traded very favourably at the start, it ended up being a close call due to the boundary.

They avalanche banned the Scimi and the Loki, we avalanche banned the regular Geddon.

Match 3: Gunspam vs Anhinga Shrapnel

With this being the last match and them not using a unique yet, we were pretty sure they'd use it here. We opted to leave Anhinga open rather than Bestla. This kind of locked us out of using our flag, but we were confident gunspam can handle most Anhinga-based comps, especially with both the Scimi and most of the Enigma variations being banned out. With them banning the Maulus, and us banning most WDs, we felt a Keres pair would be an overinvestment for ewar, so we went with tackle frigates instead. We chose Nergals, but in hindsight, faster and cheaper tackle such as the Malediction would have been overall better. Nevertheless, we were sure they'd bring an Anhinga, but not sure if it'd be a kite or rush comp, so unlike in our upper bracket match against Psychokids, we chose not to warp to 0 on this one. Shivon in the Nergal hero tackled their Basi early, and Giacomo soon after tackled the Anhinga. We were told after the tournament the Anhinga was tackled with 1 or 2 server ticks left on MJD activation. Unfortunate timing. After trading logi and removing the Anhinga early, and without any ewar on either side, armor gunspam just trades better with what the teams had remaining, and so we took our first series.

---

Psychokids (2-1):

With us somehow beating Paper Numbers, who I personally considered one of the tournament favourites, we secured top 4 and were up against Psychokids next. With Psychokids winning their series 2-0, there was practically no extra break between the two series. After the third PN match we had 5 minutes before we had to do bans for this one. Then another 15 minutes before checks, then another 5-10 minutes before being teleported. This tempo was present throughout the whole day.

Match 1: Neut drone mirror

Psychokids have also lost their flag in the upper bracket, and therefore did not have it going into the series with us. We decided to open with something different again, and for the second time in the main event we left the Eos open. This is also the match where us showing the Vindi comp started paying some extra dividends, since Psychokids banned the Widow. We declared unique, they did not. For their unique ban they banned the Anhinga. After looking at all the bans, what felt the most natural was a drone comp. And only after we already got into our ships, it occurred to us, wait a minute, that probably means they'll bring a drone comp as well. And so we brought our standard drone comp, the same one we beat Tuskers with in prelims, and Psychokids brought a near-mirror, similar to the one Tuskers brought. They opted to bring damps, while we had a Vexor for more neuts and damage, which in the mirror is a slight advantage.

Not too much to say about the match itself, our target prioritization was good, and the match quickly snowballed in our favour. We started trading logi frigs at about the same time, but while we successfully caught both of theirs, our Deacon managed to slip away while they were busy killing our Thalia, which had a compound effect on the snowball we already started. This made it seem like the match wasn't close, but again, it was only a couple of slight differences at the start of the match, which quickly added up, that got us this win.

At this point our cruiser logi pilot, Matniz the ever-stressed, who was busy fitting ships for future matches as he wasn't flying in this one, started yelling at us to hold the last ship and start looting the field for compact medium capacitor boosters, because we were out. As you can tell, we didn't exactly expect to get this far.

After the match, we avalanche banned the Armageddon and its navy counterpart, while they avalanche banned the Sentinel.

Match 2: Gunspam near-mirror

I can't remember exactly what my thought process here was. When all the bans were done though, expected a gunspam mirror here.

We did not expect a 100mn Rook with infinite rep drones on it, however. This messed up target prioritization enough that the match snowballed in their favour. Props to Psychokids for that wild addition to a gunspam.

After the match, we opted to avalanche ban the two classic gunspam ships, Astarte and Absol. Psychokids banned the Oneiros.

Match 3: Armor Barghs vs Sentry drones

We noticed they weren't banning the Barghest in the earlier matches, so we opted to leave Enigma open and hopefully make it an attractive choice. Psychokids saw through our bait, however, and instead brought what I assume to be their own counter to Enigma, a sentry focused drone comp.

We deleted the Algos Navy first because it is a very squishy target. After that, we rammed our Huginn in pretty close to get webs on the logi frigs, and removed those next. This turned it into a match of attrition, where we had all the range control and logi, but they had the dps to kill our Barghs through logi, if we stay in sentry optimal. They did break through one Bargh, due to some indecisiveness on our part whether to go into the sentry cloud passing dangerous close to their ships, or sending the primaried Bargh far into Sentry falloff. That said, I never felt particularly threatened in my Bargh. They initially didn't drop the sentries at the very center, meaning I had the option to pull out of range if needed, while I'd still be in range myself. The match *was* close, we lost a Bargh, but we managed to kill the low-end, then kill the Ishtars and stabilize the second Bargh before the point of no return.

---

This marks the first and only series we won where we brought neither a unique nor our flag Vindi. This doesn't mean the Vindi did nothing here, in both this and the PN series, it was still a threat our opponents had to think about the entire time, and it made several comps less desirable for them to field. Whether it *actually* influenced their decision, you'd have to ask them.

This secured top 3 (wtf how did we get here), and our next opponents, Rote Kapelle.

---

Rote Kapelle (2-0):

Match 1: Bestla rush vs Anhinga rush

Well, we finally met our match in being silly. We both declared uniques, and neither of us banned the Bestla or Anhinga. We practiced Anhinga, both rush and kite, but never did we have both ships open. I had a hunch that in a rush mirror, the Bestla rush is stronger, but I wasn't sure. We brought it anyway. I had a feeling it was stronger because there is no good time to shoot a Bestla. Shoot it too late, it doesn't die. Shoot it too early, you trade two of your DPS ships for it. While the Anhinga is the first primary the moment the logi is gone. You could argue the rest of the rush is what won that match, but I'm not sure, would love to test it more. Rote told me later they felt they made some mistakes, but I felt we also made some mistakes, so maybe it cancels out? Either way, while we lost the Bestla, we won the match, and at least for now settled the Bestla vs Anhinga rush debate. And yes, their Onyx would have died anyway, it was hitting armor with 2 minutes left. You can't really escape the Jackdaw range.

Match 2: Vindi flag control vs Gunspam

Here Rote made the same mistake V0LTA did, they left the Zarm open against a team with a flag still available. They did ban the Widow, but believe it or not that's not the only flag comp we have. With the Zarm open, and the other bans being what they are, we were 90% sure they'd bring a Zarm gunspam. So we refit for that, and finally brought our flag again, just no Widow this time. I opted to go with a more defensive triple web Vindi over the MJD, and it proved correct. Between our NApoc and the flag we tackled 4 of their ships as they burned in, and managed to keep all of them away from our logi and ewar. Cal in the Cruor also did a great job immediately webbing and neuting out the Maledictions that burned for our Zarm. After this, it was a matter of splitting DPS, occasionally landing a BB jam on their Zarm, and damping it when we needed it to come into web range. We grinded down a few dps ships first, then removed the Zarm, and that was pretty much it.

Huge props to Rote Kapelle, they also had a banger of a run, and were very cool to chat with in local. At least you guys could rest now.

---

And so here we were just before the grand finals. All this time I wasn't thinking "damn we're so good", I was thinking "how are all these amazing teams losing to us today?". I think, honestly, after PN, who we expected to lose to, we felt very free, and had nothing but positive vibes throughout. This helped a ton with the exhaustion and the insane stress and tempo of the final day best-of series. We also happened to keep our flag alive the entire time, while every other team we faced in the loser bracket so far has lost theirs before. It was a huge advantage. Either way, grand finals it is.

---

Dracarys (3-2):

Dracarys. The short time I had before bans, because we got our first 20 minute break of the day, I looked at their comps so far. Their flagship-supported gunspam seemed kinda unbeatable. We never really scrimmed something like it, so we decided to start this off similar to our first PN match. A comp we've not shown yet, one we didn't care if it gets avalanche banned, and something that would give us a good feel for how their apex comp functions.

Also important to mention, going into them, we had the timezone advantage. Grand finals would be starting at 2am their time, but they had the upper bracket advantage. We've already played 8 matches with no breaks, for the past 5h, they played only 2, with a 3h break. And they could watch all our matches and analyze them. Apples and oranges, no idea which debuff was worse here.

Match 1: Controlslayer vs Flag gunspam

They in fact cooperated with our plans and brought their signature comp. We on the other hand brought a comp we stole and have not practiced much. Not sure what to call it, Reggie would probably call it "Controlslayer". 2x RHML battleship with some ewar and tackle. It's a well-rounded comp, and works well as long as you keep stuff away from your logi cruiser. Instead, I jumped straight on top of their Rodiva, and Dracarys in a very practiced fashion adjusted immediately, and went for a logi trade. We messed up screening for our logi and traded, but that is very much in favour of their comp, not much we could have done after that.

Now, the interesting bit here is, I avalanche banned Rodiva and Malediction. I didn't want to avalanche ban any gunspam ships in case we wanted to use it ourselves in a future match, and I wanted them to bring the same thing just a little bit weaker. Honestly, I didn't think too much about the bans, but they ended up being crucial for match 2. They avalanche banned the Sentinel.

Match 2: Bestla rush vs Flag gunspam

For regular bans they banned the same things as match 1, while we banned the Ashimmu and some ships with high kin/therm resists, that Vindi prefers not to shoot at. That said, our plan wasn't to bring the flag, it was to bring the Bestla rush, yet again. As I'm writing this, I noticed I didn't ban Huginn/Rapier here. I am pretty sure it's because I was exhausted, but instead I'll say here that I was just *that* confident that they'd bring the same comp again, and not something with a Huginn. Might even be true. In any case, they obliged again, and brought a no-Rodiva version of their comp. One that has 2x Deacon instead. This ended up incredibly important, because our rush is very dangerous for logi frigates, while a Rodiva would be able to happily sit 60km away, as they tackle our entire comp down. As for the match itself, everything was proceeding as one would expect, until our Alligator entered very very low hull, and started holding. What happened was, we killed a ship just as it reached that point, our Scimi got in better range (and slightly escaped neuts), and their flag swapped targets expecting the last volley to kill it. This little miracle bought us a whole 45 seconds of a living Alligator that should have been dead. We traded 1 Alligator for 2 cruisers and half of a Navy Brutix. While I'm pretty sure we'd have won the match even without this, we snowballed hard here, which allowed us to kill their flag with a minute remaining. And if we hadn't killed their flag here, I think the whole series goes differently.

With their flag dead, we avalanche banned the ArmaNI, while they avalanche banned the Scimitar and the Jackdaw. For a little bit of backstory, our very initial Bestla HAM rush used t2 logi frigs instead, and only one Jackdaw, so for us this was easily replaceable. So I got the brilliant idea of "Hey guys, what if we Bestla rush twice in a row?". And so we did, because my team is very supportive.

Match 3: Bestla rush vs regular gunspam

This time I did remember to ban the ever problematic web ships, while keeping the other bans mostly the same. We also banned the Tholos to do a little trolling. We declared a unique, they finally declared a unique, we both banned the Anhinga, so our planned and beloved Bestla rush was open. They brought a gunspam, for the third time, without an ArmaNI this time. As for their unique, they brought a Shapash. This can be quite a problematic screening frigate due to the tank and extra scram range it gets. But they initially used it to tackle our Raptor, which let a lot of our DPS through.

Our first actual primary was the Oneiros, and on the way there we shot some of the tackle frigates. The Ares lived, but the Punisher didn't, which freed up an extra DPS ship. They initially primaried our Bestla, which tanked comfortably under logi reps. So they swapped to our Raptor for a bit, but since it already got close, the little transversal it had let it survive under reps, even webbed. The Oneiros got caught quickly by the Bestla drones and died pretty soon after that. They primaried our logi only after their Oneiros died, which was too little too late as the match already snowballed hard in our favour. Our Bestla even survived due to some miraculous tanking by Giacomo, and us barely destroying the PNI which was the last ship tackling it, which let it pull range.

After taking the lead in the grand finals, and with our flag still alive, we were feeling confident. We were also feeling very very exhausted at this point. With the limit of 2 unique usages in the Bo5, we were out of uniques. Dracarys still had one more.

They avalanche banned the Nighthawk and the Loki, I banned the Deimos. Because I still wanted to leave gunspam open for ourselves just in case, and we didn't use the Deimos. The avalanche bans at this point made HAM rush very weak if one brought it.

Match 4: Flag Vindi 3xBS vs Enigma

This match I consider my greatest failure. I am going to activate my one time use excuse of "I was exhausted" here. A ton of ships were already banned, and I missed one. HAM rush was gone, Sentinel was gone, they banned their usual stuff meaning the Bargh, Curse, Arbi and Zarm were all gone. Long story short, I hoped a Guardian ban would discourage Enigma. It didn't. And I completely missed the Crucifier. We basically countered ourselves here, with 3 easily controllable battleships and some frigate tackle that Enigma can quickly kill.

I got a good double jump onto their Blackbird at the start, which we managed to kill. We unfortunately lost a Pontifex in trade, which means we were on a 2 minute timer before it becomes infinitely harder to do anything to an Enigma when our info links go down. We didn't manage to kill anything else. I messed up my second jump opportunity, Dracarys adjusted their range well. They slowly killed our low-end until we had just the three battleships remaining. I made a second, huge mistake here. I went for another jump play, trying to catch one of their DPS ships. Without info links, I was damped to 5km lock range the moment I jumped, meaning the jump was pointless and I should have just tried to preserve the flag at all costs. As I jumped in, their Huginn got me webbed and they primaried the Vindi. What saved me was their Shapash never getting into scram range, despite their damps and TDs. When my self-MJD was off-cooldown, I jumped again, which bought some valuable time to rep a little while they got back in range. All in all, I lived in 13% structure, if the match was 10 seconds longer, we'd have lost our flag here.

Dracarys played this Enigma basically perfectly, I don't think we had a very high chance of winning this match from the get-go, but if I played better, our flag wouldn't have ever been threatened.

Match 5: Vindi/Widow vs neut drones

Over 20 ships were banned at this point. Enigma was out. HAM rush was out. Gunspam was very weak. Drones were weak. Half the TD ships were banned. Honestly, props to Dracarys for showing up with a working comp, because if we had lost our flag in the previous match, I'm not sure we'd have a working comp here. We decided to bring our Vindi/Widow, despite the Zarm ban. We've practiced this comp plenty of times with both Oneiros and Guardian. It's not as strong as with a Zarm, but it still works. And with the amount of other archetypes that were banned out, we felt Oneiros was the better pick here, because it's easier to keep safe.

Start of the match, I was tired and on autopilot. Called for Ishtars to be kept away from me, due to their resists. Webbed the Armageddon at range myself. Called for jams on the Hyena, and at some point, found myself in web range of the Myrm Navy, which I felt was a good target. So I shot that first. Zarii in the Vexor in the made an excellent jump into their backline, and started chasing the Dracarys Oneiros. He got tackled by a Ponti at some point, but not before chasing the Oneiros to the other side of the arena, 100km away from the targets I was shooting, where Virion in the Magnate Navy caught up to him and kept him there.

So now I had free reign to kill the Myrm Navy, removing a quarter of their DPS. Giacomo in the Nergal caught their Kitsune in the meantime, removing their only jams. Erdinhok and Zarii both dropped me cap charges with perfect timing, just as I was using my last one while shooting the Geddon. This let me finish it off, removing another quarter of their DPS and a lot of neut pressure. In the meantime, with the Kitsune gone and their drones focused on our logi, they never got to remove our little frigate-that-could off their Oneiros, so I burned to it in the Vindi, Reggie running to me to get me skirmish links before he died. They managed to finally kill Matniz in our own Oneiros at some point, but it was too late. We removed too much already. Their Oneiros was now Vindi webbed with nothing to remove the webs, they had 2 DPS ships, a Celestis and a bunch of tackle left on grid. They managed to kill the Widow, but its job was done. We killed the Oneiros, we killed the tackle frigates, we caught an Ishtar, and with 20 seconds, we killed one of the two remaining Ishtars and we knew it was over. And my Vindi lived. I am so happy it lived.

I'll keep to the same formula of the Tuskers AAR, and leave suggestions for the next AT here:

  • For absolute fairness, do not allow uniques again.
  • Because I know you won't do the above, at least limit them to the best-of series. 1 per bo3, 2 per bo5, like this year. Disallow them in bo1s.

    • In a series, they're an interesting strategic decision, in a bo1 they're just an advantage.
  • Keep Swiss prelims, it was great. Though try to fix the scheduling issues if possible.
  • I like the 2 battleship rule, but I think overall the gradient inflation is a too harsh on them on top of that.
  • Also the inflation is too lax on frigates, specifically ewar frigates.
  • Now that the Bhaalgorn is not allowed as a flagship (great decision, please keep it), can we *point* the Bhaalgorn as a non-flag, please?

I'd like to thank all of our scrim partners, both this year and in previous ones. I am running out of characters in the post though, so a special thank you to Rusty Hyenas, for being our longest running scrim partners overall. You guys rock. Go win next year.

I'd also like to personally thank my entire team. This wouldn't have happened if even a single one of you wasn't with us. Special thank you to both Reggie and Matniz for going through absolute hell fitting ships before deadline on that final day.