#madewithgamemaker

Considering my lack of coding skills overall, I am unfortunatelly not allowed to think about a feature I want to implement for 15 seconds, put my hands on the keyboard, write all the code, press enter and harvest the fruits of my labor.

Being the idiot that I am, I have developed a simple, fool proof process of implementing individual features.

Simply go from most barebones, broken, ugly "as long as it works" state to a somewhat polished version.

As of now, a great example would be my recently implemented spawner objects.

At first I just made a single color block with a wave count, and time. Then added --timer. Put into game room, tested, works. Next.

Second step, implement code for running the timer to 0 and substarcting from the amount of total "waves" in the spawner. Refresh game room, tested, works. Next.

Lastly add a code for spawning a selected object instance after the timer reaches zero. Also should check that the correct amount of enemies are spawned. Refresh game room, tested, work. Next.

Stupid simple, but works and also ensures I do not have to spend hours finding a simple typo or a bug.

Most of the time i do not do the final polishings, because i intend to do those in waves, but exceptions arise. Sometimes implementing them make me feel more motivated, due to the fact that I start seeing the project in its final light.

If this step by step process does not workwork I refrain back to other "weapons" in my arsenal like "From now on that is a feature" or "fuck it - it will have to do".

We are happy to announce that Box Kid Adventures is available now on Steam (https://store.steampowered.com/app/1217870/Box_Kid_Adventures/) and itch.io (https://trexinteractive.itch.io/box-kid-adventures).

Here's a quick puzzle from the #BoxKidAdventures

This is what happens when you push a crate onto a conveyor belt. #screenshotsaturday #BoxKidAdventures