[BUG] Steam API

[jupster]

Investigating

We are aware of a recent bug that we are investigating.

Something from the Steam API is not working as before and prevents recently updated files from being downloaded, thus preventing those mods from updating properly.
There is currently no workaround for this issue but we are doing our best to fix it
We do not have an ETA on a fix, please be patient and know that we are sorry for the trouble it may cause for your units and games with your friends.

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
A clear and concise description of what actually happened.

Screenshots
If applicable, add screenshots to help explain your problem.

OS Version (required):

• OS: [e.g. Windows 10 1903]
• FASTER Version [e.g. 1.9f_102]

Additional context
Add any other context about the problem here.

---

Please add a comment if your having the issue

[OverlordZorn]

yea okey so steam updated something in terms of how the updated items data is formatted. That something is being accessed after Verification completed, 35 files queued for download. (388535247 bytes) and before Progress 00,12% ( 567,00 B / 903,76 MB)

[Grezvany13]

Got the same issues; seems to only add files to the queue and doesn't actually update.
Happens with all mods which need an update.

• OS: Windows Server 2022 Standard (21H2)
• FASTER: 1.9f (1.9.6.2)

Updater Console Output (truncated):

Connecting to Steam as **********
	Client : Attempting connect..
	Client : Connected
	Client : Logged on
Connected !
Adding mods to download list...
Almost there...
   Starting 3117898674
   Getting manifest for 3117898674
   Manifest retrieved 3117898674
    Attempting to start download of item 3117898674... 
    OK.
    Downloading 244 files with total size of    7.37 GB...
    File verified : addons\ww2_spex_assets_c_characters_americans_c.pbo ( 185.03 KB)
    File verified : addons\ww2_spex_assets_c_characters_commonwealth_c.pbo.ww2_spex_2025_07_15.bisign ( 572.00  B)
    File verified : addons\ww2_spex_assets_c_characters_germans_c.pbo.ww2_spex_2025_07_15.bisign ( 572.00  B)
    ...
    Verification completed, 242 files queued for download. (7910273169 bytes)

[derbilbo]

Same issues here.

Workaround for still being able to add new mods/updates is:

Step 1: Add new Mod via ID as you would normally
Step 2: Update mod, producing the Bug
Step 3: Open the Mod folder. A basic structure (addon, sometimes some readMEs) has been created.
Step 4: Manually add the mod content (full copy including readMe, possible extensions etc, PBOs)
Step 5: Cancel Update, Update Mod again

Result: Mod shows as fully updated and installed, can be used.

[SpaceFahad]

Use this temporary solution until the issue is resolved...

Instructions:

1- Create a .bat file and paste the script below.
2- Set your steam cmd path / steam username / the mod you want to download (One mod only).
3- Run the .bat file and you will be asked to type your password. (should get cached for future downloads).
4- once done, you should find the mods downloaded in steamcmd\steamapps\workshop\content\107410.
5- copy the mods you downloaded and paste in FASTER mod staging directory.
6- click update in Faster and it will show as up to date.

@echo off
setlocal

:: ========== CONFIGURATION ==========
set STEAMCMD_PATH=C:\steamcmd\steamcmd.exe
set STEAM_USERNAME=your_steam_username
set MOD_ID=450814997
:: ===================================

:: Download the mod
%STEAMCMD_PATH% +login %STEAM_USERNAME% %STEAM_PASSWORD% +workshop_download_item 107410 %MOD_ID% +quit

exit

[Sparky0313]

@SpaceFahad Just for Clarification, do we place the mod directory path in the configuration line for MODS_DIR=D: ?

[SpaceFahad]

@SpaceFahad Just for Clarification, do we place the mod directory path in the configuration line for MODS_DIR=D: ?

@Sparky0313
yes, I'd manually copy the mods from that directory to the mod staging directory that FASTER is using though.

[aliasalpha]

Could SteamGuard be the issue? My group has just had the same problem and we tried to download one mod via steamCMD and that required a steamguard login, it worked properly and now faster seems to be working correctly again.

It's a server that's not quite 2 weeks old and we haven't directly used SteamCMD on it before so it might be a separate issue but it might be worth a try for anyone else having the problem.

[Foxlider]

The issue seems to be an update in SteamAPI and how they zip content on their servers.
A PullRequest is being worked on to fix the issue.

[SpaceFahad]

Use this temporary solution until the issue is resolved...

Instructions:

1- Create a .bat file and paste the script below.
2- Set your steam cmd path / steam username / the mod you want to download (One mod only).
3- Run the .bat file and you will be asked to type your password. (should get cached for future downloads).
4- once done, you should find the mods downloaded in steamcmd\steamapps\workshop\content\107410.
5- copy the mods you downloaded and paste in FASTER mod staging directory.
6- click update in Faster and it will show as up to date.

@echo off
setlocal

:: ========== CONFIGURATION ==========
set STEAMCMD_PATH=C:\steamcmd\steamcmd.exe
set STEAM_USERNAME=your_steam_username
set MOD_ID=450814997
:: ===================================

:: Download the mod
%STEAMCMD_PATH% +login %STEAM_USERNAME% %STEAM_PASSWORD% +workshop_download_item 107410 %MOD_ID% +quit

exit

I have removed the line with set STEAM_PASSWORD=your_steam_password you will now need to insert your password manually when starting the .bat file and it should work fine. been a long time since I used this but this appears to fix this basic bat file.