Still not possible to auto deploy to Steam after build?

Unity Services
,
1

I have searched on/off for a while but still haven’t found a solution to have Unity Cloud Build auto deploy to Steam on successful build (only for the build that is setup to it of cause). I don’t want it to auto release, but want it to auto put up that build on Steamworks so I can pick which branch it goes to.

It’s really annoying to manually download a zip file and upload it to Steamworks - and I’m really surprised there isn’t an “easy” solution for this already as there must be ton of people facing this issue?

Or am I the only one actually updating my game after release? :smile:

2

… so it seems I’m very alone with this wish :smile:

3

i saw this repo while ago, havent tested
https://github.com/alanlawrance/steam-deploy-public

4

Thanks, I have seen similar things and I’m sure this dude made a great solution. I’m just thinking why it have to be SO complicated. It’s not his fault, I’m just saying it have to be done simpler.
https://github.com/alanlawrance/steam-deploy-public/wiki

:slight_smile:

5

I’m the guy who made the above mentioned system – it’s still shocking to me that Unity doesn’t have built in support for deploying to Steam.

You may want to look into using Jenkins as a good off-the-shelf solution. I wrote a custom node app partially because I wanted to learn Node JS.

BTW, we are using this system for two projects, so it is battle tested. Let me know if you have questions about it.