Last active
August 29, 2015 14:25
-
-
Save vbawol/39bb75329c8e5211ad7e to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @ECHO OFF | |
| SET [email protected] | |
| SET STEAMPW=chamgeme | |
| SET ARMASVRPATH=C:\Arma3Server | |
| SET ARMAAPPID=107410 | |
| :: Workshop IDs: EpochExperimental = 455221958, Normal Epoch = 421839251 | |
| SET ARMAWORKSHOPID=455221958 | |
| :: remove mod folder | |
| rd /s/q "%ARMASVRPATH%\@Epoch" | |
| :: update workshop mod | |
| START "" /WAIT steamcmd.exe +login %STEAMUN% %STEAMPW% +workshop_download_item %ARMAAPPID% %ARMAWORKSHOPID% +quit | |
| :: copy files back to server | |
| xcopy /s/e/y/q/i "steamapps\workshop\content\%ARMAAPPID%\%ARMAWORKSHOPID%" "%ARMASVRPATH%\@Epoch" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Best I can tell this script does not work on a machine dedicated solely to running an Epoch server instance without having Steam installed and the Steam Workshop Epoch subscription (which is kind of a pain if the Steam account you are using is only for an Arma Dedicated Server). (In other words, a PC with as little installed on it as possible.)
In the long run, I believe it might be easier to just navigate to your local machine's workshop folder (which is correctly identified in your script as \steamapps\workshop\content\107410\421839251 (for the normal current Epoch client build) and FTP its contents to an emptied @epoch folder in the server's target instance folder.
Unless I'm misinterpreting the terrible documentation for SteamCMD.exe...