I know LD #29 has already started, but I didn’t have time before it started to write my triannual “What I learned” post.
So, to recap, last LD I did not finish my game, Naught. This was very disappointing to me, and I’ve been good on my path so far this time to not replicate it.
- Two dimensional arrays. And how tricky and paradoxically simple they are.
- Make sure your idea is a good and doable idea before you start.
- If where you’re going doesn’t lead anywhere, notice it quickly and start turning in the right direction.
- Get all needed work done (homework, job work, etc.) BEFORE Ludum Dare starts.
- But hey, if those are more important, it’s not the end of the world to miss out on a LD.
- If you plan on making a three dimensional game with physics, make sure you know how basic physics work first.
- Actually, if you want to make a 3D game, ask yourself why it has to be 3D. Only if that’s a good enough reason, continue.
- Python is a great language, but it’s very bad at memory management.
- Have a thorough understanding of your tools before you use them.
- Fractals are cool and can be used to generate procedurally-generated landscapes and such. (In conjunction with 2D arrays, of course)
- Make it fun first. Always think about what’s fun. Think about what you find fun and why you find it fun. I think I say this every time I write this post.