Help with the architecture of a quick game development tool

I am toying around with an idea for quick game development, where quick actually stands both for quick iterations of the gameplay code, quick setup of a new game and quick deployment to different platforms.

I have the basics concepts down:

  • live reload of a shared library for quick gameplay iterations

  • setup of a new project might be done with a kind of template that actually just creates a and the Cargo.toml file with the correct dependencies

  • quick deployment is a whole different beast and that's where I need your help.

As for the deployment, I'd like to be able to write the code once and deploy it to Windows, macOS, Linux, iOS and Android.
I have a proof of concept working as part of my mini test game but it's made up of a lot of small moving parts and I would like to streamline it as much as possible.

I thought that the guys who made OpenFL and Lime (Haxe) did an excellent job at it as they actually wrote a command line app that takes care of compiling and packaging the application for each platform. I would like to do something similar but I need a hand with the architecture of it.

Suggestions are definitely welcome. If you also want to jump on board this could actually be a community driven project.

1 Like