
Here's a little image to console you:

Some Off-Topic Stuff
I released a new Counter-Strike 2D version though. It seems to have some critical bugs (they came out of nowhere! I promise!) which is hell because releasing a new CS2D version is a complicated process. It's a horrible nightmare. I never invested a second on any automation and therefore my CS2D-release-process consists of many annoying and super error-prone steps. I'll share them with you because I really have nothing to show regarding Stranded III this time.
After finishing everything I do the following stuff on my Windows machine:












Then I boot Ubuntu in a VM and





Afterwards I boot another VM with MacOS and do the same here. I skip the dedicated server for MacOS though (I could make one but I really wanted to save some steps)



After doing all of this it's time to go live with the new version:



...and there are also some other small steps that I left out. Like updating changelogs, language files, command lists etc.
It's fun. I can do it in half an hour if everything goes really well but normally it doesn't.
So why do I share this with you (except for the fact that I don't have news about Stranded III)? I want you to stay sane! So please, if you're a developer: Consider to automate your build process. Especially if you're developing a cross-platform game! Everything else is madness and will lead to a lot of trouble.
I will do the same for Stranded III. I'll either set up my own little build server(s) or use Unity's Cloud Build service.
edited 1×, last 19.06.16 12:08:44 pm