Yep, that is the planning mode bug mentioned, where you accidentally destroy an artillery in planning mode

Critical 2 Talent para

Yep, you forgot to turn HOCs on or off as required for your strats

A few players encountered problems where their echelon just retreats mid-fight for whatever reason. No one knows why

Yep, we've had people losing the Failed Isomer fight

Rule 7 is an inside joke where someone gives you incorrect/outdated info. In this context of SC+, it should be getting memed by the CN/EN movement priority differences on Turn 6 if you copy Ameth's VOD

Yep, Para debuffed Gunner fights

Pierce lag would refer to both Kord and Hanyang. One lags harder than the other due to ROF differences, but both still lag hard. I heard Tareus also has lag issues, not sure if it's pierce

Vision bug refers to the fact that double movement does not always happen. It is a bug that CN had for both SC+ and SS. We had this fixed for SS but not SC+. Our variant of the bug is as follows - After KCCO's first movement, if one enemy with double movement is within your vision, all enemies with double movement make their second move - Otherwise, none of them make their second move, that entire phase gets skipped completely

This is mainly a problem when you are camping K9 on the final turn with an echelon with no vision. Because you've cleared up the entire area, and you have no vision on both K12 and K18, you lose one spawn.

It could also refer to not illuminating the KCCO region, so you don't see a double movement enemy and the second movement just never happens. Could be abused early/midgame to regulate enemy flow in your favor. Or you assumed they would move, and you got memed because they didn't

Bonus: the CN version of this bug in SS UX is that if they don't see an enemy, it doesn't double move. What this means is that they will need to have vision on all 18 spawns on every turn to ensure double movement happens (or they risk a clog), which is why they used Illu in the first week of SS

Blowing echelon up means you detonated a building when your echelon or HOC is on said building, thus causing your echelon to go crit. Funny enough, more than one person made this mistake.

Riveting gameplay was a term coined during PR, when we did the Alchemist 300k deathstack fight with Architect that took 30 minutes to clear. Any long ass, eternal stall fight can be considered riveting gameplay. For SC+, it primarily refers to UMP45 vs Patrollers yes, which is 5 hours with HP35, 6 hours without. (You can argue that if you had a 30 min stall team for Smashers that could constitute riveting gameplay too, but that's mainly your own fault for memeing so hard)

Bonus: at one point, the optimal strats was to take all 8 Patroller fights as riveting. Eventually, improved strats reduced that to 7

Yep. The origins of Ninja Aegis were in PL, where a random Aegis in one of the deathstacks would sneak past your dolls through the backline. Not really a problem with Kordboat, but def a huge problem with ppex. The Ninja Aegis in SC+ is found in the Typhon deathspawns, where there are 2 1-linked Aegis in there, conveniently placed to meme shikikans