T1 pgens aren't essential for T2 arty, it's a 4% reload discount which ends up being a 1.19x effectiveness for fully capped arty, coming to a profit of only 62 mass which is a negligible 2.8% of the total 2200 mass cost of the setup (unitdb).
This marginal adjacency is eclipsed by the idea that sparkies shouldn't build any eco structures so that there is no chance of them not being a combat unit.
Nomander
@Nomander
Best posts made by Nomander
-
RE: UEF T2 Field Engineer (T1 pgens)
-
RE: SUGGESTION: AEON T2 Shield Generator Fix
As Deribus mentioned, I think reducing the size without changing the stats would make it too powerful in firebases, since you can basically stack 4+ instead of 3 shields to defend a T2 PD and they are high HP and low cost compared to UEF/Cybran.
Shield HP Mass HP/Mass Cybran ED2 7000 460 15.22 Cybran T2 ED1 4000 160 25.00 Sera T2 13000 700 18.57 UEF T2 9000 600 15.00 Aeon T2 11000 480 22.92 Here's the overlap possible for a PD with the current shields:

I don't think being unable to upgrade the shield is a huge drawback, it just requires you to ctrl-k the shield and reclaim the small wreck before building the very cheap T3 shield. It requires some APM but definitely isn't impossible if you're defending something important that requires your attention with shields.
For the size complaint, I'm not sure what you want to shield. It can shield adjacent structures pretty well. Not entirely but almost everything:

For this pgen specific case I'd rather opt for a tiny increase in shield size instead of making the structure smaller.I've been testing your size idea with the "Create entities" dialog (its in the hotkeys, you use the hotkey while a unit is selected and you can change its blueprint values. Spawn a new copy of the unit to make sure you get all the changes. Requires cheats):
4x4 size is just way too OP, since you get ~8 overlapping shields instead of 3:

5x5 size is enough to cover a pgen but its still a small shield so its not reaching towards diagonals:

It also still increases the coverage from 3 to 4-6 shields:

Decreasing the size even by 1 seems to bring more problems than solutions.All in all, I understand why you dislike the shield but I think its strengths in HP and cost make it above average for firebases and protecting most directly adjacent things like T3 shields, pgens, factories, or engineers. The T3 shield is also very strong because it's super cheap and the 2nd most powerful, while giving sufficient radius imo: I've seen Aeon T3 shields easily protect air grids, artillery, or game enders from artillery barrages when a sufficient number are built (and number of shields is the most mass-efficient way of defending, so having a cheap shield helps a huge amount - natural regen is nearly worthless while recharge from 0 is extremely strong).
Shield Shield HP Mass BT HP/Mass Sera T3 21000 3600 5841 5.83 UEF T3 17000 3300 4988 5.15 Aeon T3 18000 2400 4097 7.50 Cybran ED5 16500 4260 7100 3.87 Cybran T3 ED4 13000 2460 3515 5.28 -
RE: Bug Report:SMD missing target
SMD missing and having to fire a second time is unacceptable. In that game the SMD firing twice actually lost the game.
-
SACU Rebalance mod
I have published the SACU Rebalance mod. Afaik there are no bugs and its very playable: the balance is theoretical number crunching with very light T3/T4 land/navy combat testing, and all the game/visual design is implemented at a basic level (so you can look in UI for stats). Please host it/play it/sandbox it.

There's a github page with the working environment and commit history: https://github.com/lL1l1/SACU-Balance-Mod/tree/mainFrom the github:
FAF SACU Rebalance
This is a mod for Forged Alliance Forever.
Implements changes for the SACU rebalance proposed by balance team: cheaper SACUs, stronger adjacency/gateways, new army support enhancements.
Rambo SACUs are independently reworked with new weapons and upgrades to fill gaps in faction rosters.General Changes
- Cheaper SACUs: Buildtime and energy costs are significantly reduced across the board.
- RAS is more energy expensive due to decreased base SACU mass cost. RAS also increases death volatility of SACUs.
- Weaker base SACUs: Unupgraded SACUs have less HP and/or DPS.
- Stronger gateways: Gateways consume 32-44 mass/s building SACU and have 160 buildpower, while costing 2550 mass, down from 3000.
- Stronger adjacency: Mass fab and pgen adjacency for gateways is un-nerfed and made equivalent to land factory adjacency.
- Engineering upgrade buff: Engineering upgrades are made much cheaper, especially on buildpower and energy, so that they can come close to engineering stations in power.
Faction specific changes (Rambos and support enhancements)
-
UEF SACUs are highly armored with good firepower. They have powerful support enhancements and combat enhancements designed to engage T4 units.

-
Cybran SACUs are lightly armoured and slow, but are highly upgradeable with enhancements designed to engage enemy T3, SACU, naval, or air units.

-
Aeon SACUs are agile and have a powerful sensor suite (to counter underwater cloak) but are lightly armored. They have cheap combat enhancements designed to engage enemy T3 units.
Aeon SACU nano is removed since nano does not fit the faction.

-
Seraphim SACUs are highly armored with increased Regeneration rate but reduced firepower without combat enhancements. They have unique utility/support enhancements and powerful combat enhancements designed to engage enemy T3 units.
Seraphim SACU shield is removed since personal shields do not fit the faction.

- Cheaper SACUs: Buildtime and energy costs are significantly reduced across the board.
-
Discussion about ACUs and their volatile nature (i.e. possible Disconnect Share rules)
This is a repost of a post made by @Jip on Discord:
It goes without saying that when an ACU is destroyed that it should explode. This discussion is not about the 'typical' way that an ACU ends up exploding. Instead, this discussion about what should happen when a player disconnects. There's some interest of adjusting this behavior, see for example:
And with thanks to @Nomander we now have a technical solution:
We just have to enable it. At the moment it is disabled. We can make the behavior work like any of the other share conditions. And we can also introduce a new behavior: the ACU recalls individually.
The question that remains is how this feature should work in practice. A few relevant facts:
- A) It is difficult, if not impossible to determine whether a player left the game on purpose or because of technical reasons. We'll refer to this as the player 'leaving' regardless of what the cause is.
- B) It is possible to make it configurable, in the same way that the victory conditions and the share conditions are configurable.
And the primary questions for this topic?
-
- Should we adjust the behavior of the ACU when a player leaves the game?
-
- Should we make the behavior customizable (through the lobby options)?
-
- The new (individual) recall behavior, how should that work exactly? Are there conditions, and if so - what are they?
I'd like to add some more details based on what's possible with the current implementation too:
- Aside from recalling the ACU individually, we can share the ACU for a limited time or permanently.
- The share condition for units can be changed based on if a player disconnects, and whatever anti-abuse measures are used (ex: use fullshare for disconnects unless we detect abuse, then use no-share just like for normal deaths).
- Some ideas for anti-abuse measures are checking current ACU HP, if the ACU was damaged recently, or letting the ACU live (and possibly sharing it) and calling it abuse if it dies too quickly.
-
Second Iteration of Partial SACU Rebalance
Second Iteration of Partial SACU Rebalance
The second iteration of SACU changes is now live on FAF Beta Balance.
Please make sure to host FAF Beta Balance, since the changes are not on FAF Develop.
The complete changes can be found on the changelog website.
Previous discussions about the first iteration can be found in the "experimental changes" posts on the forum and on Discord.
Iteration Changes
This iteration tries to prevent SACU rushes while making them a little more efficient lategame, and addresses Seraphim overcharge and UEF bubble shield. We encourage everyone to play with these changes and provide feedback.
All the changes specific to this iteration can be found in this commit history.
Early SACUs
Early SACUs were very powerful because you could only fight them with T3 units, and any failure would result in the SACU regenerating all damage, reclaiming wrecks instantly, and securing the area with structures. To prevent this:
- Significantly increased energy cost of survivability upgrades.
- Slightly increased energy cost of combatant SACUs
- Removed ACU priority from SACUs
- Reduce buildpower of SACUs by 25%, except for engineer presets and UEF. UEF keeps their buildpower because their engineer preset's drone can be shot down by AA, they have a weak pushing T4, and it promotes using their unique Ravagers.
Lategame SACUs
We do want SACUs to be good lategame, especially to stabilize lategame mass donations or air losses, which are factors that make players hesitant to attack and overall idle the game.
- Mass cost reduction for high-tier survivability upgrades (Cybran cloak, Aeon 2nd shield, UEF shield, UEF bubble, Sera shield)
Other
- Increase cost of Seraphim's overcharge upgrade to reduce its snowball potential. It's pretty much an upgrade over the ACU, and can replace the ACU's energy consumption, so the first OC SACU requires increased costs.
- UEF bubble shield receives a small buff to shield recharge time.
Future Changes
Future changes will be tracked in this pull request. When they are made, they will be deployed to FAF Beta Balance with a similar announcement here.
-
RE: Question on shield assist mechanics
Maudlin is correct that assistance costs vary by shield, since it is based off of regen rate, repair cost, and RegenAssistMult.
Documentation on github repo:--- How much buildpower is required to provide 1x of the shield's regen rate.
--- The cost of assisting a shield isrepairCostRate / RegenAssistMult,
--- where repairCostRate is determined by Unit:UpdateConsumptionValues
---@field RegenAssistMult? numberThese are the buildpower and mass efficiencies considering that repair cost is 0.75x the unit cost and RegenAssistMult is 60 for all shields.
Shield AssistRegen/BP AssistRegen/Mass Sera T3 2.80 6.06 UEF T3 2.18 4.40 Aeon T3 2.50 5.69 Cybran ED5 2.33 5.19 Cybran T3 ED4 2.17 4.13 Cybran ED3 1.87 4.35 Cybran ED2 1.47 3.29 Cybran T2 ED1 0.75 4.38 Sera T2 2.55 6.07 UEF T2 2.00 5.11 Aeon T2 2.30 6.07 Considering that defending a T3 Aeon artillery costs at least 165 mass/s, and a Mavor at least 550 mass/s, it is well worth economically to spam out multiple shields (they cost around 3.4k mass each) instead of assisting one, although it is riskier because the enemy can retarget the artillery, let all your shields get up, and then come down all together in the next few artillery shots as the overspill and splash damage take effect. Good for game enders that you need to protect at all costs but also need income to build.
2 Aeon T3 artillery one shot a shield and it is impossible to assist to prevent that currently.
Assisting works at full speed if you're stalling but that's a hard to fix engine bug/performance heavy Lua fix.
[Does assisting] speed up getting a collapsed shield back up?
No it does not. That is determined by the shield recharge time which will be added to the UI soon.
Aeon used to have t2 shields that couldn't be upgraded (unless my memory fails me) but that was patched as a balance decision.
The balance team does approve of letting them be upgradeable but there is simply no animation for doing so.
-
RE: Discussion about the interrupt pathfinding hotkey and a mod showcase
Good post. If you want you can take a look at/contribute to 4z0t's rings for all mod, it's set up to display range rings on top of units and currently there's no capture preview iirc.
As for interrupt pathfinding, it can get a bit out of the original scope with certain commands (attack move causing long range reclaim, load into transport from long range, capture from long range). We already filter the order to engineers only, but we could go further and filter by command type too, so it only works on what we want for good gameplay. Alternatively we should implement interrupt on assist/capture/auto ranged reclaim into the game going by the (poorly enforced) policy of integrating important mods into the game.
-
RE: TMD could be cheaper
The cost of the TML isn't just 800 mass:
- mass cost: TML (800 mass) + missile (250) + some way to kill tmd, let's say 4 (easily countered) T1 bombers (360) = 1410 mass (unitdb) which affords 5 TMD.
- You need to get an extremely valuable central map position to be able to force out 6 TMD per enemy base. You then have to get T2 engineers to that position. Taking all that time + having to get the engis there (early HQ instead of eco) gets your opponent a T2 mex.
- You also have to build a TML instead of a T2 mex which gives your opponent extra mass to build TMD while you load the TML.
Latest posts made by Nomander
-
RE: Problems with 2026.11.0?
The sound error FAQ is outdated. We now know the cause of the bug being that the engine causes memory corruption when using an unsupported sound configuration. What the FAQ's troubleshooting covers is:
- Disabling surround sound and enabling stereo, which is a supported configuration
- Adjusting audio hardware/software configuration to shuffle memory hoping the memory corruption doesn't land somewhere where the game crashes once it reaches there
- Turning off sound entirely (/nosound) so the bugged code is never reached
Your crash address 0x00915402 pops up for other sound error victims, so it is likely the cause. We fixed a different common crash/desync bug so this is the only remaining one afaik.
Another way to fix it right now is to play on the new engine, which fixes the sound bug. You can do this by downloading the alpha client and selecting FAF Develop when creating a new game.
For others in the future, I expect the next stable client update will support launching the new engine, rust client should get an update for it soon, and eventually we'll get the new engine on normal FAF. -
RE: Problems with 2026.11.0?
On Discord I haven't seen an uptick of reports that would indicate a common error with the update.
Is it your game or client crashing? If it's the game then make sure the FAF Debugger in the client settings is enabled and post the game logs (both can be found through the client's top left menu button). The debugger will write a stack trace at the end of the game log when enabled and the game crashes. -
RE: SC: FA (Moho) engine sources
FAF develop has some connectivity improvements by adjusting network parameters to make use of more capable modern networking: https://github.com/FAForever/fa/pull/7364 That's the most immediate change I know we can test right now. I don't know what's the state of the other WebRTC-based netcode or ice adapter changes.
-
Cybran land buff proposals
-
Buff brick DPS 295 -> ~304, returning 50% of the DPS it lost after the last nerf (down from 312.5) because:
- the nerf's goal was to make brick weaker vs Percy, and now Percy is strong vs brick, so there is space to buff the DPS
- the nerf's goal was to make brick weaker vs othuum/harb, and while in a 1-unit-composition matchup this nerf made it more fair per mass, the brick needs to be more unfair because their lack of shields makes sniper DPS and Ythotha AoE very strong. Their stats also struggle to beat GC/ythotha + harb/othuum compositions a bit too much, which makes getting Megalith too difficult. Monkeylord is not good against GC/Ythotha at all, so mega is required to fight those T4s efficiently without just winning hard in T2 and getting an overpowering army at later T3.
-
Add the Pulsar, which is the unreleased cybran T3 long range anti shield unit. It was wanted by old balance team, then it got delayed and eventually canceled by Rhaelya looking for an alternative solution before adding new units. Since no alternatives have been proposed and I don't see what would work better, I think the unit should finally be added. It solves the shieldless arty's low DPS against snipers and the struggle against mid-late gun coms that OC all your bricks if you try to attack anything while easily tanking with shield upgrades and mobile shields.
-
Make firebeetles jump at enemies.
- it looks cool and fits the theme
- makes them hit in the middle of unit clumps more consistently, including on attack move/attack orders.
- reduces pathfinding needed
- increases their effective attack range
The jump range in my prototype is around 5, which is the current detonation trigger range, and is small compared to any gun (LABs have 14 range).
I think after the last nerf beetle is pretty good for gameplay but is a little weak because it dies very easily, especially at T3 stage, if you don't have basically equal unit counts and are in range to tank for the beetles, so that's why I'm interested in trying this new mechanic as a straight buff.
-
-
RE: ACU Walk Animations – Adjustments as a Test Mod
What I meant is that since it modifies the bone positions even slightly, it probably eventually causes desyncs if two players have different animations. It's not a big gameplay difference in your animation example, but it's a potential desync so it can't be allowed. To relate back to cheese's post, you can't have "users could have whichever animation or mix animations they like," it would be limited to what FAF implements and officially distributes.
-
RE: ACU Walk Animations – Adjustments as a Test Mod
Animations are not safe because they modify bone positions and thus things like transport attachment position or projectile creation position.
-
RE: Updated fix to audio bugs?
I'm not sure what you mean by super buggy audio, but it would be helpful if you could try these specific workarounds since I've developed fixes for them:
- Change from 5.1 (side speakers) or 7.1 audio to stereo. Side speakers because FA supports the older 5.1 back speakers channel format. This is the bug fixed in the binary patch.
- If your PC uptime is more than 24.86 days, sounds will play once per game session. Restarting your PC will fix this. This is a bug in XACT so it doesn't fit in a binary patch.
-
RE: Plans for the near future?
FAF is all volunteers so there isn't really a definitive roadmap. Current trends are possible UI improvements (being careful of automation/making things too easy) and a lot of engine bug fixes and performance improvements.
New units and game mechanics are for mods to do due to FAF's preservation mission, but imo FAF does have some places to improve mod support in. That does have the challenge of preserving support for old mods though. -
RE: Desync Postmortem
Yes these desyncs and crashes affected replays as well as live games. Actually they were really common in replays which helped a lot with testing.
The reason why this fix was so difficult is because it's a memory corruption writing into random space. With the way your computer set up the game's memory it caused regular desyncs and crashes in replays. For a lot of other people it rarely did anything. So for Brutus's idea, this specific bug would be caught by luck in a simulation CI.
Here's how I see potential improvements compared to my experience:
- Desync tracking would automatically and seriously tell devs of deysncs. I only noticed desyncs from constantly checking forums and chats, and eventually I had to go through a specific replay search to even have any data about desyncs, and even then there wasn't a really big response. Automation would've been a more serious alert and it could've even caught it much earlier on.
- The reason this specific patch wasn't caught early was because there was 0 testing in prod. It's a tricky bug, so fair enough that some testing in dev wouldn't catch it, but since we released it without any feature using it, it took all the way up until the painting feature for its effects to show, which made the change that introduced the bug disconnected from the updates exhibiting the bug.
- With AI we can do much better reviews. This bug was a very human error that is easily picked up by AI or I guess some linter. I don't think we do very complex patches most of the time, so static analysis should work quite easily. In this sense I think we could actually speed up engine patches because of their more reliable code, but of course it's best if we just have the backup testing in prod with the two points above.