There is a hotkey to copy the queue of an engineer you're mousing over ("Copy orders of the unit the mouse is on top of"), and I often use the the ctrl + right click game option version of the feature that ("Assist to copy command queue"). Can queue with 1 engi and then add new engis without the assist behavior slowing things down. Can also remove the original engi to do something else while another engi continues the queue.
It's not exactly keybinds but it's still an essential way to control units (for me).

It's fixable, in AirUnit.lua you have to disable the vision and unit intel when the unit is killed instead of on impact. You also have to disable vision in Unit.lua for navy. It already disables radar/sonar on death.
Whether or not it's desirable for balance I'm not sure, people often use dead scouts for vision into bases through SAM walls or to counteract Cybran stealth more effectively. Your idea for slowing the scout down as if its experiencing air drag seems like a decent way to make dead scouts decent vs armies (slower t1 scouts) but worse vs bases (faster t3 scouts).

Pathing stuff like this is really tied into the engine so there's not much we can do. I think you can't even make ACUs path over units because it would automatically apply that 1x1 footprint to all 1x1 units (all t1-t3). So a lot of it is wishful thinking unless you dive deep into reverse engineering.

I think this would be a good thing as I dont believe players consider the known poor pathing in this game to be a positive aspect.

The bad pathing has cemented itself in the game's balance and micro so for some it is a positive aspect just to diversify supcom from other games, even though it has its frustrating moments.

@Nuggets said in Ranked vs unranked games:

i have 0 trust in anything else it shows from lobby settings

Its display of the share condition is bugged but everything else is good I think.

https://forum.faforever.com/topic/272/why-was-game-x-not-rated

The UI mod Supreme Scoreboard2 displays if a game is rated or not, although I think it only handles common cases like mods, victory conditions, AIs, and unit restrictions.

Also I'd like to mention that Aeon gets another anti-Percival unit in their double range double shield ACU long before a GC can be built, so it's not like Harbs are even bad on one-lane maps where in theory Percivals always kite and win. Harbs are great for keeping Percies off your ACU in that situation because the Percies have to try to swarm your ACU to kill it instead of dying one by one but that requires moving forward into Harbs/shields.

@FtXCommando said in AEONS are GARBAGE!:

Percies are slower than chickens and same speed as GCs let alone t3 units.

Percies are 2.2 speed, while chicken/GC are 2.5/2.4 speed respectively. You're thinking of bricks with 2.4 speed. The rest of what you said with them being unable to start fights is correct though.

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

It was only reduced from 10000 to 8000 compared to the Steam version. On top of that, shields can reduce crash damage by 20% of their own max HP (basically this means Czars/Ahwassas crashes can only kill 3600 HP SMD through shields).
@Kilatamoro is correct in that it's like a normal AoE that gets absorbed by shields. I did write some code where crash splash damage ignores shields, since it is reduced by shield max HP already, but the issue is that if the unit crashes right outside a shield it deals 8000 damage straight through the shield, which isn't fixable.

@FtXCommando said in AEONS are GARBAGE!:

bomber that granted has some micro quirks.

Was fixed, it no longer flips out when you try to micro it.

@Sprouto I randomly found out that Monkeylord's SinkLower causes this, as for GC it doesn't use SinkLower and its target is rather messed up still so I don't know.

@Kilatamoro said in Wish-A-Mod Foundation:

A visible cooldown for Billy nuke on your com. Otherwise you have to look at the in-game timer and remember the cooldown duration.

The ACU model has a small animation for the missile hatch closing depicting the reload time. It's not visible at a distance, but it's good to know about. It also reloads in 30s and rebuilds in ~30s with T3 suite (or 3 T3 engis) so those numbers match up.

@TankenAbard The examples your own post fit the criteria of supporting an army and not replacing it itself, because those effects are way stronger when used by units with good DPS/HP stats compared to the same mass in pure SACUs.

As for replacing the ACU, that's a good thing as it allows using the cool things the ACU has on a large scale across multiple fronts (like 1v1) and without risking ending the game due to a simple shift in mass from the entire map concentrated to snipe the ACU.

You can hack around the issue with projectiles by setting the ACU's hitbox to very small so that it paths around units a bit better, and then creating an entity attached to the commander with a hitbox. Then you can override the new entity's OnCollisionCheck, OnCollisionCheckWeapon, and OnDamage functions with the ACU's versions.

There is an example of creating an entity attached to a unit in the Aeon T2 Torpedo Launcher script. I don't have an example of an entity with a hitbox passing damage to the base unit, although I know it's possible since giving props projectile collision was an experiment we did.

Monkeylord has a target bone on its turret, and as far as I know all surface targeting weapons can target the seabed layer too, so it is not an issue with seabed layer targeting or bones. I thought it was related to LayerChangeOffsetHeight, but changing that doesn't affect the targeting, it only affects how deep in the water the Monkeylord shows up with vision (which would be a good improvement by itself). So it seems to be entirely an engine issue with how weapons target things on the seabed but on the land layer (because if you disable AboveWaterTargetsOnly, then the weapon fires at underwater, seabed-layer targets just fine).

For example, although these two can hit and see each other, they won't do it without an attack command:

Slacking on the job when the commander isn't looking :

Make sure the "Always Show Custom Names" option is enabled in your game settings.

I'm not aware of any little arrow to open the map. Typically you enable the minimap using the map options button in the multifunction bar in the top left:

I've had this issue, there needs to be a minimum time for how long you have to hold left click.

There's a few console commands that adjust the pathfinding budget starting with path_, maybe those have an effect.

For FAF the file blueprints-ai.lua already calculates threat levels from unit stats, you'd want to overwrite the function SetThreatValuesOfUnit in there to properly replace the threat level calculation. This also means you don't have to worry about mod load order since that threat calculation is done in PostModBlueprints.

There are MANY combinations and control values that can impact the actual DPS calculation - it goes far beyond the 'RateOfFire' blueprint value, which many consider to be the 'be all and end all' of DPS calculations. It is not - and anyone who has done sufficient weapon 'rigging' can tell you the many pitfalls, in the blueprint values, that can lead to an erroneous DPS value.

@Sprouto There's a rather comprehensive DPS calculation in FAF's unitviewdetail.lua, I think it's only missing fire rate when it is limited by energy requirements or animation speed, and if I remember correctly some rounding for some stat should be floored instead, but it's still quite complete. I should really put that calculation in a library.