godot-game-template VS unity-actions

Basically I explained everything in this issue: https://github.com/crystal-bit/godot-game-template/issues/80

I don't actually know what this does, but it looks really well done (https://github.com/crystal-bit/godot-game-template) (general game template with some scene managers)

If you go with Godot, you can use a template like crystal-bit/godot-game-template to automate pushing a build to github pages. Then you can share a link for students to play.

FYI, there is also abarichello/godot-ci which I think supports 3 and 4 with and without C#. I use it via crystal-bit/godot-game-template and it exports web and native builds, hosts web builds on GitHub pages, and pushes builds to itchio.

Check out crystal-bit/godot-game-template for a github template for godot games that build for those platforms with Github Actions. I haven't actually used any of them but the html5 one yet, but really nice that it was so easy to setup.

I often wonder about this too - is it better to switch scenes or have a very basic "main" scene that's basically just a persistent container for more substantive scenes which are instantiated and freed as needed. Haven't tried it yet but I did stumble across this github repo which demonstrates one approach: https://github.com/crystal-bit/godot-game-template

The game has been made using the Godot Game Template, check it out if you want automatic CI builds + extra utils for your game!

> 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've been struggling with getting the docker images provided by https://game.ci/ to build his project at all, let alone automating it in a pipeline.

https://game.ci/ has fantastic GitHub actions to automate all of this on each PR or push to main etc and then just upload the result of the build as an artifact and job done - takes minutes to setup and you can use your own machine as a self hosted runner to get the same build speed as local builds

These guys did a wonderful job at providing a docker-based build environment for Unity, btw: https://game.ci/

(Someone's built something similar for Unity, but it wasn't as one click when I last looked -- especially since Unity may require licenses.)

My repositories are on github, so I'm using Github Actions for build automation - I found it really easy to setup compared to other platforms. + There's basically a ready-made action for building with unity - game.ci (although I wrote my own solution for iOS).

Game CI seems to be pretty good, given the fact that it is open source and you can fix it if needed