Our game team overlord @Jip has asked what large features you guys would like to see worked on next.
Useful links:
Weekly Discussion #29 - What would you like to see in the game next?
Pretty much everything I could think of fell into the client, server, or balance domains, but after extensive thought I did think of a single thing.
There is a blueprint variable:
AttackGroundTries = 'n', <This determines the number of shots at a ground target before moving on to the next target.>
That would be cool if it was set to 1 for bombers, or able to be toggled in some way, so that you can queue up multiple ground attacks ahead of time. The problem is that when you use this variable it causes bombers to miss by quite a bit, like how all bombers used to miss their first pass when FA was launched. It would be nice if this was fixed and implemented in some way.
Interesting 
, it appears to miss by quite some margin. But we can look into that
A work of art is never finished, merely abandoned
Unsurprisingly mine are PvE related! However they're all UI/client related rather than changing the actual game.
- AI in matchmaker (https://forum.faforever.com/topic/5549/the-what-ais-in-ladder-season-2 and the separate discord discussion)
- UI rework for both the lobby and the client, to improve the experience for PvE players. On the lobby side, an improved AI selection interface where you just select you want an AI opponent and then it results in a separate drop-down menu to pick the AI; a drop-down menu to set its AiX modifier individually (if it's possible for it to be different for individual AI); and a button to get more AI that takes you to the mod vault and shows you a filtered list of the AI mods to pick from (with a nice to have being a rating displaying for each AI so players have a better sense of its strength); On the client side, introducing something like this (and earlier post in the same thread) to improve the campaign selection:
https://forum.faforever.com/topic/5642/coop-campaigns-order/13
M27AI developer; Devlog and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v70-devlog
Limiting the number of SACUs: https://forum.faforever.com/topic/4715/sacu-lives-matter.
@thomashiatt said in Weekly Discussion #29 - What would you like to see in the game next?:
Pretty much everything I could think of fell into the client, server, or balance domains, but after extensive thought I did think of a single thing.
There is a blueprint variable:
AttackGroundTries = 'n', <This determines the number of shots at a ground target before moving on to the next target.>That would be cool if it was set to 1 for bombers, or able to be toggled in some way, so that you can queue up multiple ground attacks ahead of time. The problem is that when you use this variable it causes bombers to miss by quite a bit, like how all bombers used to miss their first pass when FA was launched. It would be nice if this was fixed and implemented in some way.
I've looked into this. It appears the bomber acts as if it a regular move order and therefore de-accelerates too soon, causing the bomb it is dropping to hit somewhere in the vicinity, usually in front of the target
A work of art is never finished, merely abandoned
I would like to see a Beetle being built and used...
Also would like to see a Beetle explode on a GC's claw, now when it falls to the ground.
Idk what to tell you boss but i see more beetles build in high lvl teamgames than rhino's.
The main reason why you see very little of them in general is because 1. The current meta is focussed on t3 land rush while beetles are only really good against t1/t2 and 2. Because the map were you play 50% of your games on is specifically bad for beetles because there's a big chokepoint where 1 radar can see everything.
Beetles exploding in gc's claw sounds cool though
How about overlays for units and structures as implemented in e.g. ecomanager and idle-engineers?
Quite a few of the better players use ecomanager purely for the overlays and having a nicer looking version of idle engineers accessible to everyone from the settings menu would certainly be amazing 
I dont know if this is possible but having groups of engineers of different tech and factions that are selected at once be able to build anything that one of the selected engineers can (eg if you select 2 uef t2 engineers and 2 t3 aeon engineers, you could get them to build a t3 pgen (uef would assist the aeon engis) or a triad (aeon would assist the uef engis). Ideally via the main building selection screen and hotkeys but I expect only hotkeys might be feasible.
Similarly seecting a mix of t1-t3 engis would allow building t3 buildings with the lower tech engis assisting the higher tech engis
M27AI developer; Devlog and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v70-devlog
@maudlin27 what you're asking is not possible. But we did implement a hotkey that allows you to quickly split your selection. See also:
And then specifically option (7). You'll need two key bindings:
Then you hit the 1st one to create the splits, and hit the 2nd one to switch your selection between the splits. That way you can quickly do what you're asking:
- first split only contains the highest tech (tech 3 in your example)
- issue build order for tech 3 power generator
- second / third split contains tech 2 or tech 1 engineers
- issue assist order to one of the tech 3 engineers
A work of art is never finished, merely abandoned
@jip said in Weekly Discussion #29 - What would you like to see in the game next?:
I've looked into this. It appears the bomber acts as if it a regular move order and therefore de-accelerates too soon, causing the bomb it is dropping to hit somewhere in the vicinity, usually in front of the target
Does that mean it can be fixed or not? Strange that changing the number of times it does a ground attack changes the interpretation of the order. I guess it is probably a new variable that was added with FA and was never properly implemented or something.
Has anyone ever tried using DLL injection to get more control over engine side things? Maybe you could intercept calls to the audio API and fix them or pass them along to a more modern API to fix the sound bug. I don't know what else could be accomplished with it, I'm just vaguely aware of the technique.