It is best to build one or more prototypes, and yes you can develop final art and sound assets as you go- but at some stage it pays to sidestep and build the ACTUAL product from scratch.

And Valves Half-life one shows you that you can, infact, do this twice or more and win big as a result.

Really well-put thread! A lot of the technical debt that I accumulated came from inexperience as that project was the first game project I made.

After 4 years of experimenting with smaller games, seeing what is and isn't good practice that I'm able to try and put it all together for this.

This is exactly why we prototype. The faster we can get to the full gameplay we want, the clearer the requirements for the systems we get. Thus, throwing a tonne of programmer art, asset store junk and crude mock up models gets you to the fail point faster.

(Ditto) The lighting looks so much cooler and dramatic.

#godot #gamedev #indiedev #oneirality

If you want, I'd recommend checking out Kanri. It's an offline kanban board application you can use to organize tasks.

For me it just comes down to pacing; not doing too much or too little. It also helps to keep the work on a day to day basis varied instead of the same thing.

We're eating good now! Looking forward to Episode 2!

Thanks for this!

This is just another horrible youtube feature being added without consulting user feedback

Spring rolls? It looks good!