v189 Update
Mini update:

• Fixed a bug where moles could be given the same order as selens.
• MMLs should be less likely to move forwards into range of T2 PD
• Disabled several factory builders for lower tech factories.
• Fixed a bug with the ACU determining friendly AA threat when in the water.

Acknowledgements

• Relent0r - Replay and spotting a bug with moles being given attack move orders

v188 Update
16 changes, including:

• Fixed a bug that would break M28's engineer logic if the enemy built T2 arti near M28's base
• LABs should be more aggressive if the enemy has an exposed unit but nearby combat units.
• Units should no longer try dodging shots from snoops or spirits
• Fixed a bug where deceivers would continue to cover an ACU after it's got a stealth/nano upgrade

Acknowledgements

• Radde – v186 mapgen and 3 xander replays
• Vortex – v185 QUIET replay
• Lohkrim – v187 QUIET replay

v187 Update
8 changes, including:

• Fixed a bug that meant bombers weren't sniping ACUs most of the time
• M28 should consider sniping enemy ACUs for significantly longer than before
• T1 PD should only 5 wall pieces built around it (instead of to save a precious 9 mass...

Acknowledgements

• Radde - Several mapgen replays against v186 M28

Trophy Award
Radde, GhillieWolf and Mhad - beating 1.4 resource M28 on a 15km land based mapgen

v186 Update
9 changes, including:

• Building T1 engineers on repeat should no longer cause a large group of T3 mobile arti to stay stuck firing at them
• TMD should be built preemptively for large amounts of PD at the T2 stage
• Slightly increased the range for experimentals to aggressively go for a nearby enemy ACU

Acknowledgements

• Radde - Various replays on Xander against v184 M28

FAF's rules are set out on the main FAForever website - by accessing FAF services, you agree to the rules outlined there, which are supplemental to the FAF Terms of Service.

For details of how to report rule breaches and/or how the rules are enforced, please refer to the separate page on moderation

Separate contribution guidelines exist for those considering contributing to FAF, while there are also official tournament rules that apply to official FAF tournaments.

I'd expect connection issues to be worse for TMM 5v5 than custom game with 10 players. For custom games if someone cant connect then they just dont get to join the lobby. For TMM it stops the entire lobby and everyone has to re-queue.

Re not following the argument about taking away players, the main point is that having 4 queues means you have fewer people per queue on average than if you have 3 queues. Fewer people per queue means longer queue time, unless no-one joins 5v5 at which point it's a waste of dev time (and it will go the way of the no share queue).

It'd also significantly increase the risk of connection issues, require far more people to be in the queue for a game, and likely take players away from the 3v3 and 4v4 TMMs (at least my general impression of custom games is that only a small number of games are large mapgen or on non-popular (astro/DG/setons) maps). Without a sudden influx of new players it'd therefore likely lead to much longer waits for games in TMM since people would be spread out over a larger number of queues (and while in theory people can join multiple queues not everyone will).

@Sandtrooper Only other way would be a mod that sets the following variable against the aiBrain:
Brain.M28FactoryPreferredBlueprintByCategory.UnitId = -1000
where UnitId is the unit id of the unit you want it to not build

v185 Update
13 changes, including:

• New game setting, M28 enemy threat factor, that lets you adjust the threat M28 assigns to enemy units. What this means in practice is you can make M28 much more or less likely to attack if it is unable to kite the enemy (for example, setting it to 0.1 and in an equal fight M28's tanks will think they have 10 times more than the enemy). Intended for people who want to significantly change how M28 plays or for use with shared armies mode, and it's not recommended you adjust this if you want a competitive experience.
• ACUs being more likely to stay in visual range of an enemy ACU they want to kill
• Spirits and snoops using attack orders when being aggressive to reduce the risk they die to shorter ranged units
• Various early game ecoing improvements, particularly for an air slot (delaying when to build energy storage or radar, fixing an issue in teamgames that caused too much T1 pgens to be built when T2 teech was available, increased prioritisation of mex upgrade assistance)

Acknowledgements

• Radde - v184 Xander replay against 1.4 and 1.5 resource M28

v184 Update
5 more changes relating to one of the previous replays, including:

• TMD should no longer be treated as an anti-air unit
• Fixed a bug that could cause ahwassa targeting to not work resulting in it suiciding
• Ahwassas should consider dropping a bomb immediately if they want to retreat from the enemy air force

v183 Update
8 changes mostly relating to another replay where Mhad killed M28 with ravager creep, including:

• Various small tweaks to ACU upgrades (UEF should be more likely to get nano, ACUs should be more/less likely to get later upgrades in some cases)
• Ahwassas should be even more likely to be built than they were already where M28 isnt far behind on air
• Added logic for M28 to prioritise T3 mobile arti to deal with nearby ravagers in a similar manner to how it prioritises building MMLs to deal with nearby (non-ravager) firebases

Acknowledgements

• Radde - 2 replays against M28 on Xander

@BlackRedDead said in Suggesting rule change: make immediately unpausing after a player asked for a pause against the rules.:

But, you also did an error - according to your calculations, it's 4:30min total, not 3!
And here you state 3.5m(in?, or meters?) now, where do you take that from out of a sudden??? - could you get your thoughts together first and check your math?

If you're going to make such comments you should be really sure that you've calculated things correctly. Which you haven't. Despite quoting me where I spell out the calculation for you. 3.5m means 3 and a half minutes, or 3 minutes 30 seconds (something that is obvious from the context). That is made up of 30s (that's seconds...) for the first person pausing when they go afk, and 3 minutes for their teammates who maintain the pause when the enemy team decides to ignore the request and resumes. Since you come up with a 4.5m figure as a 'correction' that suggests you are assuming an afk player is always able to pause the game while afk - in which case they're not actually afk.

In terms of the more coherent argument you make that the problem with this is the risk of accidental pauses, if it's possible to allow either the pauser or anyone on their team to resume the game that would solve the problem. If that's not possible then a shorter delay such as 20s could be done to balance the risk of an accidental pause against the risk of someone ruining the game by resuming.

@BlackRedDead said in Suggesting rule change: make immediately unpausing after a player asked for a pause against the rules.:

@maudlin27 ...i want to see how you sprint to the bathroom, even just peeing (and don't forget to wash your Hands!), in just 30s! xD - yet alone answer a doorbell or call, or looking after what you kid/pet did that made those loud noises!

I already explained in my post how 30s per pause would mean 3.5m in a 3v3, in the same sentence as mentioning 30s so it's not hard to miss...
If you need the game paused more than 3.5m then it doesn't seem fair to force one team to have to wait that long (even if half the players in the game think you should), and 3.5m is plenty of time to do things like answer the doorbell.

v182 Hotfix
Fixed a bug where ACUs wouldn't die

v181 Update
7 changes:

• Cruisers should no longer try and attack underwater mexes
• Fixed an error with a naval factory considering building an engineer
• Fixed 5 issues from running a quick test on a campaign map which mostly related to the log being filled with error messages

Acknowledgements

• Vortex - 2 QUIET replays against v176 M28

v180 Update
14 changes, including:

• Improved anti-ravager logic
• T1 arti drops should be less likely if the enemy lacks T2 mexes
• Fixed a bug causing the fatboy to kite units not in its range
• Adjustments to ACU upgrade logic at higher AIx modifieres

Acknowledgements

• Radde – various replays against v178 and v179 M28 on a range of maps.

v179 Update
9 changes, including:

• ACUs should be more likely to stay close to an enemy ACU if their death explosion will kill the enemy
• Fixed an error that could occur when a zone contained moles and a scout with a combat attack
• Several more TML adjustments to reduce cases where they fire at an enemy that is covered by TMD
• Reduced instances where engineers would repeatedly travel to a zone with enemy PD in and die to the PD
• Fixed an issue with QUIET and LOUD where M28 would think the Seraphim battleship was firing a nuke when it fired its main cannons.

Acknowledgements

• Radde - Various replays on Xander against v177 and v178 M28, including 2v5 replays
• Vortex - Replay against v176 M28

v178 Update
7 changes, including:

• Longer ranged units should be managed by the zone they're in, to reduce instances where they fail to kite nearby enemies
• Fixed a bug where corsairs wouldn't micro-turn after firing a bomb
• Decreased M28's tendancy to build torpedo bombers on land based maps so it should only build more if the enemy has a significant threat underwater and it's prevented from attacking from ground based AA (as opposed to inties/asfs).

Acknowledgements

• Radde - various replays on Xander against 1.4 resource M28
• Vortex - QUIET replay against v175 M28

v177 Update
15 changes from this update; sometimes I can have no changes from several Radde Xander replays, this time I had 14!

• Bombers should be significantly more aggressive, in part due to a bug that was limiting their search range to less than a range of 2 outside of adjacent zones
• Fixed a bug with tracking how much MAA the enemy has (which meant certain logic such as priotising sniperbots when the enemy is likely able to beat m28's gunships wasn't triggering)
• Fatboys should be prioritised over non-fatboy land experimentals after the first (to some extent)
• If M28 has got an ahwassa 99.9% complete, and one of Radde's teammates has a Ythotha that dies nearby, M28 should complete the ahwassa instead of having all of its engineers run away leaving the Ahwassa to die to the lightning storm (a change with very widespread application...)
• Also fixed a potential cause of a crash in LOUD games when M28 tries pausing units that have died inbetween deciding to pause the unit, and the logic for pausing it commencing.

Acknowledgements

• Radde - Xander replay against 1.3 resource M28 that prompted most changes this update
• Danger!? Snake? - Replay with a crash in LOUD

I like the idea of a pause with a fixed length before a player can resume, providing it's relatively short. Around 30s feels reasonable to me, since the default is 3 pauses, so in a 3v3 with 30s that'd mean your teammates could pause for 3m (in addition to the 30s from when you pause and have to go afk) with no further pauses then permitted by them.

Avoids any need for moderation, and strikes a balance between competing interests (since resuming the game while one player is afk likely ruins the game, but it's also no fun to be forced to wait for ages because of one player)