[BUG] INVALID CONTENT CONFIGURATION

[Fluxerr]

Prerequisites

• I have searched existing issues and confirmed this has not been reported.
• I am using the latest build version from the releases page.

Steam client version

1780352834

Windows version

Windows 11 25H2 26200.8457

Describe the bug

When installing a game like "Sledding game" as tested it will says INVALID CONTENT CONFIGURATION after during download. All files are correct. Heres the contents of the lua:
addappid(3438850)
addappid(3438851, 1, "30e1f7e188e92cc3ddfe88f8da2ddd9201e70d77603ac4bc798e055b2fdb91f1")

Doesnt happend for all games but this one in particular that was tested seems to have this issue

Steps to reproduce

1. Place Dlls in steam directory
2. Create or get a lua with the correct contents like shown above
3. Place it in the lua folder "steam\config\lua"
4. restart steam
5. press install

Expected behavior

Game should download all game files without error

Actual behavior

Doesnt start the download and shows a red error text on the game saying "INVALID CONTENT CONFIGURATION"

Log files

There is no build logs in the steamtool folder

Lua configuration (if relevant)

addappid(3438850)
addappid(3438851, 1, "30e1f7e188e92cc3ddfe88f8da2ddd9201e70d77603ac4bc798e055b2fdb91f1")

Additional context

No response

[OpenSteam001]

Thanks for reporting this.

I think this issue may be caused by the current manifest/code fetching source. I already have a new manifest API ready: manifest.opensteamtool.com, but I haven’t built a new OpenSteamTool version with it yet.

Once the next build is released, please try again with that version. If it still fails, I’ll look into it further.

[Temlpe]

Thanks for reporting this.

I think this issue may be caused by the current manifest/code fetching source. I already have a new manifest API ready: manifest.opensteamtool.com, but I haven’t built a new OpenSteamTool version with it yet.

Once the next build is released, please try again with that version. If it still fails, I’ll look into it further.

@OpenSteam001
In the next version, you can consider supporting the use of multiple manifest APIs at the same time. For example, when the wudrm API is unavailable, you can automatically switch to your new manifest API:manifest.opensteamtool.com, which may be more flexible when obtaining manifest and does not need to modify toml frequently.

[Fluxerr]

Thanks for reporting this.

I think this issue may be caused by the current manifest/code fetching source. I already have a new manifest API ready: manifest.opensteamtool.com, but I haven’t built a new OpenSteamTool version with it yet.

Once the next build is released, please try again with that version. If it still fails, I’ll look into it further.

No problem ill test the new build once finished

[OpenSteam001]

@Fluxerr please try the build from #92