@Sheikah Can you please make the Steam overlay integration a user toggleable option instead of it always being on?

The reason I ask is because I don't play FAF, but I'm always around the FAF community to help others which often requires me to have the client open while I also have Steam running & open to help people in that community too. Since I'm not actually playing FAF but frequently have both the FAF client & Steam open, I don't want my play time altered unless I'm actually playing.

I like the idea of this feature, but it should either be a user toggleable option or only be triggered when creating or joining a game from the client.

Thanks.

To get the 2-in-1 script by @IO_Nox configured to work with the Loud mod & FAF, there are at least a couple ways to go:

1. If you haven't already done so, go into the Tools of the SCFA_Updater.exe (aka LOUD Updater) & Create Shortcuts. You should see a couple new shortcuts, one of which is called LOUD Forged Alliance. In the script, change the reference for pathOrLinkGame to point to the new LOUD Forged Alliance shortcut. The shortcut already has the parameters it needs for running Loud in the target.

2. If you don't want to use a shortcut reference, you can enter the parameters directly in the script:

pathOrLinkGame := "F:\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\bin\SupremeCommander.exe /log ""F:\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\LOUD\bin\Loud.log"" /init ""..\LOUD\bin\LoudDataPath.lua"""

The paths above are for my SCFA & Loud installs, so make sure you change them as needed for yours. Also note that for the log parameter, the full path is need instead of just using ..\LOUD like for the init parameter.

The code for the FAF side of things remains unchanged.

With the changes complete, to play Loud, just open the script file normally. To play FAF, either open the Run command (Windows+R) & enter the script's file path followed by an faf parameter or copy/paste the script file & rename it beginning with FAF.

@Manimal_

https://wiki.faforever.com/en/Changes-from-steam
https://wiki.faforever.com/en/Game-Modifications-(Mods)#integrated-mods

@Anthony_zZ Another mod you can try is Disperse Move. With that mod, you select a group of engineers (or other units) & give them a set of Shift+Move orders. After you've set all the move orders you want, use the keybind that you assign to Disperse Move & it will split that group of engineers/units into individual move orders amongst the waypoints you placed. It will try to break them up into as even groups as possible, but won't always accomplish that.

There's an older similar mod in the vault called Spread Move, but I have no knowledge of how that one works.

IIRC, the T3 Engineers use the medium hook size instead of the large hook size that most T3 units use. That's why it can lift 3 instead of only 2.

@Anthony_zZ Another mod you can try is Disperse Move. With that mod, you select a group of engineers (or other units) & give them a set of Shift+Move orders. After you've set all the move orders you want, use the keybind that you assign to Disperse Move & it will split that group of engineers/units into individual move orders amongst the waypoints you placed. It will try to break them up into as even groups as possible, but won't always accomplish that.

There's an older similar mod in the vault called Spread Move, but I have no knowledge of how that one works.

@treos If you're referring to the game updates (not client updates), then when you go into the lobby, you should see a Patchnotes button towards the bottom right.

@lamoulinette When in-game, click Map Options (the lower-left icon in the Multifunction Bar under the Resource Bar), then select Resources under Main View.

@Jip Sprouto did the same/a very similar change for LOUD. You may want to look into that to compare against your implementation.

Another way to go about this is to enable Draggable Build Queue in Options > Interface. This allows you to add units to your existing queue then move them to the front so they build next while keeping your existing queue intact. The only thing you need to do if your existing queue is on repeat build is to delete the units you added from the queue once they're built.

@Manimal_

https://wiki.faforever.com/en/Changes-from-steam
https://wiki.faforever.com/en/Game-Modifications-(Mods)#integrated-mods

@Sheikah Can you please make the Steam overlay integration a user toggleable option instead of it always being on?

The reason I ask is because I don't play FAF, but I'm always around the FAF community to help others which often requires me to have the client open while I also have Steam running & open to help people in that community too. Since I'm not actually playing FAF but frequently have both the FAF client & Steam open, I don't want my play time altered unless I'm actually playing.

I like the idea of this feature, but it should either be a user toggleable option or only be triggered when creating or joining a game from the client.

Thanks.

To get the 2-in-1 script by @IO_Nox configured to work with the Loud mod & FAF, there are at least a couple ways to go:

1. If you haven't already done so, go into the Tools of the SCFA_Updater.exe (aka LOUD Updater) & Create Shortcuts. You should see a couple new shortcuts, one of which is called LOUD Forged Alliance. In the script, change the reference for pathOrLinkGame to point to the new LOUD Forged Alliance shortcut. The shortcut already has the parameters it needs for running Loud in the target.

2. If you don't want to use a shortcut reference, you can enter the parameters directly in the script:

pathOrLinkGame := "F:\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\bin\SupremeCommander.exe /log ""F:\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\LOUD\bin\Loud.log"" /init ""..\LOUD\bin\LoudDataPath.lua"""

The paths above are for my SCFA & Loud installs, so make sure you change them as needed for yours. Also note that for the log parameter, the full path is need instead of just using ..\LOUD like for the init parameter.

The code for the FAF side of things remains unchanged.

With the changes complete, to play Loud, just open the script file normally. To play FAF, either open the Run command (Windows+R) & enter the script's file path followed by an faf parameter or copy/paste the script file & rename it beginning with FAF.

@tatsu Sorry for the confusion. I was indeed asking about IO's script.

@IO_Nox Thanks for the feedback. I used that info along with your revised 2-in-1 script & was able to setup a script for Steam/FAF & a script for using the LOUD mod with Steam. The only thing I need to do now is create a script for those cases that I want to launch the FAF exe offline (not through the client), but I should be able to mash something together by following all the provided info & examples.

Thanks again for your help!