turing-machine VS thetawave-legacy

But now let's be honest with ourselves, are we really that busy or is this the 9th project you started but aren't intending on finishing anymore? With around 5 years of coding experience I realized that it's more often the latter than anything else. Recently I finished version 0 of a touring machine I wrote in rust as a way of learning the language. Something I realized after finishing the project was, that I wanted to create a completely different app. Did I start the project and create the repository? Yes, I even did my "initial commit" with some libraries I needed etc. Will I ever finish it? I have no idea. Only time will tell. In the meantime I decided to put that project off even further and write an article about why I am putting it off. Quite paradoxical.

That's in the pipeline. Check out https://github.com/thetawavegame/thetawave-legacy for a preview of some of the things that are coming.

Similarly, the InvasionFormation phase takes in an InvasionFormationPool parameter and spawns a vector of Spawnables with positions from that pool at random. Below is an example of an InvasionFormationPool called Level1Easy defined in spawner.ron.

I tried installing via cargo install --git https://github.com/amethyst/theta-wave which panics at runtime due to missing configuration files. Is there any reason why you don't bake the .ron files into the binary using the include_bytes! macro and replace Config::load with Config::load_bytes? Is it so the end-user can change the configuration without having to recompile?