This echos my experiences, especially with the move to “live services” model for games. Often the teams working on the services for multiplayer games are very small so it’s all about leverage. They’re also embedded within a culture that doesn’t value or understand the practices and tools that are taken for granted in webdev, mostly because they’re hard to transfer to the other domains in gamedev.

I’m glad to see the open source development of these tools. Personally, there’s a lot of stuff colleagues and I have built that I would love to see open sourced. Otherwise we just end up implementing the same services over and over again.

Another example is patch delivery. It’s a solved problem yet everyone keeps rolling their own, or only shipping to Steam. Of course, all managed with some Jenkins scripts written by someone that’s no longer at the company. I want Fastlane for games that makes it easy to target the various distribution channels across desktop/mobile/console.

The lack of a standardized patch system for games is mind boggling! Sure there’s some for desktop software exes which just ship the new version every time but those apps are rather small and games can be several GB! We had to roll our own for our game but I couldn’t believe there wasn’t a universal standard when I went searching for one last year. Butler from itch.io looked interesting but I couldn’t decipher how to use it in the end. Also rolling patches manually seemed crazy to me and we ended up using a library similar to rsync that works pretty well and makes deploying patches easier but still not perfect.

Thanks for sharing your experience and kind words — we would always be happy to talk shop. I think it’s a shame that current infra solutions prevent a lot of hobbyists and studios from ever launching a multiplayer games, I would love to see it as prolific as single player experiences.

> https://game.ci

I don't recommend it.

Game CI has been in development for a long time. It only really supports GitHub Actions. It can't correctly build il2cpp Unity projects. The licenses needed to run it are more expensive than Unity Build Automation / Unity Cloud Build. If you want to automate Unity builds and you don't want to learn the Windows Containers ecosystem, Jenkins and/or Tekton, you should use Unity's service.

CI/CD is a bad choice for most developers, on most platforms, for most clients. That said, it makes sense to do for your backends.

> or (as has happened to us with different game web service/API/middleware providers) they may choose to abruptly deprecate the service upon which you built.

Which service was that? GameSparks? That sucks.

> with inappropriate cloud dev tooling

Well everyone takes their own journey to discover how shitty Lambda, Cognito, CloudFormation and related are.

> with basically any datastore other than Redis you will run in to issues matchmaking

Matchmakers do not have to be complicated.

I'm having a good experience with some automation build automation with Councourse CI. Of course, I self host, and I am doing some real trivial stuff right now.

> CI/CD is a bad choice for most developers, on most platforms, for most clients. That said, it makes sense to do for your backends.

Are you making this statement about game devs, or more broadly? I don’t know much about fame dev, but if more broadly that’s a pretty spicy take.

Only in my experience, automated building of the client side of a game is usually low ROI. In broader contexts yeah you should be doing CI/CD.