Hi there!
What I did for automating the Steam Workshop updates of TLD is this:
Code:
https://github.com/tldmod/tldmod/blob/master/.travis.workshop.sh#L111
Basically you can bypass the buggy TaleWorlds uploader altogether by using the official command-line version of the Steam client:
Code:
https://developer.valvesoftware.com/wiki/SteamCMD
--
There's a slightly under-documented parameter called
that, if paired with a correct
.VDF configuration file, can create/upload/upgrade any Workshop item no matter the game.
You can see an example VDF file in the official Steamworks documentation site:
Code:
https://partner.steamgames.com/doc/features/workshop/implementation#SteamCmd
You basically need the correct Steam
AppID of the game (for Warband is
, you can find them in the URLs of the Workshop and Store pages:
Code:
http://steamcommunity.com/app/48700/workshop/
) and a
you own (the one for
The Last Days is
; again you can find it from the URL where people subscribe:
Code:
https://steamcommunity.com/sharedfiles/filedetails/?id=299974223
). If you don't include it will create a brand new entry. The preview image, base mod folder, hidden state and other parameters are optional and essentially identical to the counterparts provided by TaleWorlds, it all ends in the same place, so this way is less buggy and more interesting.
Right now our deployments are completely automated by a bot account, all under demand.
--
TL;DR: Create a text file with the Workshop item configuration, save it as
and run the
SteamCMD client with the correct parameters, something like this:
Code:
steamcmd +login myLoginName myPassword +workshop_build_item my_mod_conf.vdf +quit
Code:
workshopitem
{
"appid" "48700"
"publishedfileid" "299974223"
"contentfolder" "C:\Warband\Modules\MyCoolMod\"
"changenote" "This appears in the changelog, but you can edit it later from the Web page."
# swy: you can add more configuration keys here :)
}
Hope that helps!