BrewLAN 0.8.3 file

Contents

You can safely skip this section and go right to installation if you don't care what the individual parts are.

Inside the 7z download you will find folders called mods, maps, and gamedata.

The gamedata folder items contain UI textures and lobby options, neither of which can cause desync because it's all client side. They are not strictly required for function, but you will be missing custom unit icons, strategic icons, buttons, and the ability to configure Crystal Hill, TeaD, and Crate Drop in the lobby.

The maps folder contains a custom 8-player version of Gentlemen's Reef, called Mentlegen's Reef, with a starting position in the centre, for 1 vs many games with Paragon Game. The other map, Dev-Tex, is a white map I use for creating icons and other testing. Neither are required. Add seasoning to taste.

The contents of the mods folder is where all the business happens. The BrewLAN folder, contains BrewLAN, and the other five folders that start BrewLAN_ contain the other 20+ sub-mods, nested in groups so it's tidier in your mods folders, and it's easier to uninstall. Which is relevant if you want to install a later version.

Installation

If you wish to use BrewLAN with FAF or LOUD, get it from their respective mod vaults. Remove any and all old versions of BrewLAN before beginning, from both your documents and your directory. Note that mod installations in your documents folder will overwrite installations in your game directory.

Inside the 7z file you will find mods, maps, and gamedata folders. The mods and maps can either go in your documents or your game installation folders. Valid directory examples include:

• %UserProfile%\Documents\my games\Gas Powered Games\Supreme Commander Forged Alliance\
• ...\SteamApps\common\supreme commander forged alliance\
• ...\Program Files\THQ\Gas Powered Games\Supreme Commander - Forged Alliance\

If the folders already exist in the target locations, merge. Maps will already exist if you're doing this in your installation directory, but mods might not. I can't guarantee either will already exist in your documents, but there should also be a replays, savegames, and maybe screenshots folders if you've ever played the game before.

The gamedata folder needs to go in your installation directory, see the last two examples above. There will already be a gamedata folder there, so merge the contents. If the scd files end up with other scd files, then you know they are in the correct place.

Verification

If you did everything correctly, assuming installation entirely in the game directory rather than split between your documents and the directory, your game install should look like:

• Supreme Commander Forged Alliance
  • bin
    • ForgedAlliance.exe or SupremeCommander.exe on steam
    • ... (a bunch of .dll files and other files)
  • gamedata
    • brewlan.scd
    • cratedrop.scd
    • crystalhill.scd
    • experimentalicons.scd
    • tead.scd
    • lua.scd
    • units.scd
    • ... (a bunch of other .scd files)
  • maps
    • BREW_REEF
    • BREW_DEV
    • SCMP_001
    • ... (a bunch of other folders containing scenario data)
  • mods
    • BrewLAN
    • BrewLAN_Gameplay
    • BrewLAN_Modules
    • BrewLAN_Plenae
    • BrewLAN_RNG
    • BrewLAN_Units
    • ... (potentially other mod folders).
  • ... ('movies', 'sounds' and other folders)

You should not have any instances of /mods/mods/ in directory structures, or any .scd files anywhere within mods folders.

Troubleshooting

If the mod icons appear yellow on the mods list, they are not installed in the correct location, and are probably nested in a way that they shouldn't be. If unit icons are missing in game you didn't install the scd files for the gamedata folder correctly.

Any other issues, feel free to ask. If you want to be helpful with your troubleshooting questions, run the game in windowed mode, press F9 to launch the log window, un-tick the debug and info messages, and quote the warnings and errors that are shown. You can also access the log with the launch option /log logname.log which will create a file called logname.log in your game directory.