Create Release script
- Lenguaje dominante
- PowerShell
- Estrellas
- 5
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Implement release script, to allow automatic building and publishing of the mod.
Hopefully there's a way to force publishing using a custom user!
---
### Requirements to pull this off
- [x] A user account on steam needs to be created
- [x] The user account needs to have Arma 3 bought on it
- [ ] SteamCMD needs to be downloaded on each users computer (this should be done within the script)
- [ ] Publisher data needs to be included in a vdf file, this should be committed into the repo with all data except `contentfolder`, `previewfile` and `changenote`. The first two need to be handled by the script (goddamn absolute values)
- [ ] A preview file, Arma 3 publisher recommends a ratio of 1:1, and the guide recommends no bigger than 1mb. Must be committed into repo in the same folder as the `make.ps1` file
### Script actions
- [ ] If the current Git commit does not have a tag associated with it (use [this](https://stackoverflow.com/a/33733020/3774356) to check) then prompt for which version the user wants to release as (make sure only one single "v" is ever on there, in case user puts "v2.0.1" instead of "2.0.1")
- [x] Build the script as per usual
- [ ] Download SteamCMD (if not already present) into the `\tools` directory (alongside armake.exe)
- [ ] If the `workshop-data.vdf` file doesn't already exist, create a template file and prompt for the desired data to fill in for `visibility`, `title`, and `description`
- [ ] If empty, place the absolute paths relevant for `contentfolder` and `previewfile`
- [ ] Error if the actual preview file does not exist for whatever reason (just in case, and also for when this script is copied to other projects)
- [ ] Prompt the user for any text to add in the changelog (can this be done in the same way github does committing?)
- [ ] Execute the SteamCMD file with: `C:\steamCMD\steamcmd.exe +login myLoginName myPassword +workshop_build_item C:\WorkShopItems\myMap\myMap.vdf +quit`, replacing the absolute paths with variable `$projectRoot`
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.