waffelzNoob

• BO advantages can be massive and can be caused through BO whoring or just dumb luck (both players improvise BO, but one happens to get a good BO by chance, or happens to win the rock-paper-scissor mechanics BOs can have in 1v1: aggressive vs greed vs passive)

• "Minor" (non-)interactions like a lab finding an engineer VS missing it, a bomber only barely grazing past ur scout's radar range and proceeding to do game-winning damage, an interceptor losing a 1v1 to another interceptor, a transport only barely (not) landing, or a proxy that went unscouted for a little too long, can cause massive impacts on the game. This makes earlygame sometimes come down to pure luck

I enjoy 1v1 once it gets past minute 5-8 with even odds. Sadly this occurs very rarely and it can be seen from the fact that tons of the semi-competent ladder replays are around 15 minutes in duration (and this is ignoring time added by players continuing to play in a lost position)

@mach said in How come you don't play ladder?:

teamgames provide stability for game to get played to its fuller potential unless you are a pro that can do all of this solo while having fun doing it, it kind of seems you need to have "minimum mastery over the game" to be able to enjoy 1v1, and it seems pretty high

i agree with this too. im ~2k in 1v1 and I can only play close to full potential on 10km. Playing 15km or larger makes me feel like I'm doing a terrible job at everything. It also increases the odds of these minor interactions with potentially massive results that i was talking about earlier.
That's just personal preference though, and i do not suggest removing >10km maps from ladder.

I used to enjoy watching upsets in ladder and seeing if someone had gained a large amount of rating since last checked. I have no idea where between 1700-1900 these two players place. The leagues tell me next to nothing.

I think I heard this change was made to reduce complaints regarding "odd" rating changes, but this just isn't it

@giebmasse said in Username rules updates:

Are homophobic, racist, political, or otherwise offensive

Can I have a mod statement about IndexLibrorum's use of words in the Discord server? Shouldn't rules regarding homophobia, racism, or otherwise offensive words be consistent in anything FAF-related?

I hear @Strydxr received a warning for a man in a gif lip-reading the n-word. That is, the man supposedly said, or looked like he was saying the n-word in the gif, but the n-word itself was not mentioned anywhere.

Yet... this is okay?

The apostrophes do not remove the meaning from the words.
There's more instances of this, by the way.

Delete this message if you like for whatever reason. Just apprehend your moderators first. I've also not seen or heard anyone but the moderator team complain about renames by the way. Most people think it's pretty funny, so the other changes are just taking away the fun that can be had with renames.

Cybran engineers/acus with T3 build suite have the ED4 shield available to them, which can be upgraded to ED5, but either one of them are awful.
Aeon 18k HP 2400 mass
UEF 17k HP 3300 mass
Sera 21k HP 3600 mass
Cybran 16.5k HP 4260 mass (or 13k HP 2460 mass)

This is either way too weak for its mass cost or way too expensive for its shield HP. To keep in line with cybran shielding being weaker (like in T2), I'd suggest making ED5 the main blueprint for T3 buildpower and reducing the build costs for ED5.

this is the simple solution, alternatively you could rework all of cybran shield's phases because as it stands now, upgrading them is a massive scam

It has come to my attention that my factory unit queue templates are in great demand. I only have land factory unit queues because air & navy queues are highly situational. Make sure to skip to end of replay before copying anything!

The replay features:

1. Solid T1 land queue, it's the same for UEF, cybran, and seraphim; 1 mobile arty and 1/2 maa for every 5 tanks, with tanks frontloaded so you don't end up with an arty at min 3. Aeon unit queue features slightly more scouts.
2. T2 land queues featuring flak and ilshies for seraphim. Pillars, flak, and shields for UEF. Flak, shields, blazes and obsidians for aeon, and rhinos, flak, and deceivers for cybran.
3. T3 land queues featuring othuums, shields, snipers, and T3 maa for seraphim. Percivals, spearheads, flak, and shields for UEF. Harbingers, flak, and shields for aeon, and bricks, flak, and deceivers for cybran.

https://replay.faforever.com/26281018

Notes:

• T3 queues don't feature T3 maa, you should add it manually because it's only needed if T3 air is a threat to you. Seraphim queue does contain T3 maa because it's too good to pass up.
• T3 queues don't feature loyalists or titans. You generally don't want too many of them anyway.
• Aeon T3 queue is very mainline, doesn't feature snipers, add them yourself if you want to make them.
• Seraphim T3 queue does contain snipers because othuum bad. If you can't afford snipers and shields yet, queue othuums yourself and use the template later... Or of course make additional templates that supplement mine
• T2 queues don't feature MML or sparkies, add them manually if you want them
• Don't rely on these blindly. They're good default queues, but it's important to put some thought into your unit queues. I only use these if minor details aren't relevant, or if thought isn't necessary. I almost always alter the T3 queues slightly based on the situation.

To copy them, go to ingame settings -> gameplay -> Factory Build Queue Templates -> on. Then, simply select the factory in my replay, head over to templates, and click the button on the left.

Chrono Dampener was nerfed recently, but I don't think it was enough. I couldn't even tell you what was changed about it because it's still broken.

The issue with Chrono is not directly the frequency or duration of the stun, but the fact that the stun will bring units to an immediate standstill. After the stun expires, the unit movement speed will be 0, and it has to reaccelerate to its max speed, which can take a second or two. Sadly at this point the next stun will have hit, bringing the movement speed back down to 0.

So, not only does Chrono stun units, it also significantly slows them down. This makes chrono extremely powerful (basically unkillable) when the ACU is retreating. I believe the best two fixes would be, in order of preference:

• Allow units to keep their momentum after being stunned
• Reduce the frequency, but increase the duration of stuns to allow units to get back to their maximum speed, and maintain it for a longer period of time

lotta text that i aint reading but i very very much prefer the old factory looks, especially HQs
if it is not possible to make them look like that with better shading/animations, then i'd prefer there be no shading/animations and we keep the old models

@TheCodemander I don't think you could've missed my point harder. Well done.

mapgen only 1v1 will just make people bored of mapgen too. after a dozen games u start to realise mapgen isn't all that diverse either