volcanicgiraffe

LD36

Ludum Dare 37

40+ pages of progress posts? Wow!

Nice to see all the roomy ideas.
And so much furniture art around as well.

LD37 Volcanic Giraffe
Booking expectations went wrong?

LD37 Volcanic Giraffe
Sometimes angry stormtrooper in coat just gets stuck inside your table for no reason.

Tags: furniture, LD37

LD 38

LD38 Cardio

So, we have another couple of ideas in ‘we-are-in & warm-up’ style.

Worms series by Team17 is not as easy as you can think:

VG-LD38-00
you see? rounding errors

Especially when you want to add some physics to your plain bitmap — it just becomes way too slow:

VG-LD38-01

Ninja rope strategy puzzle?

VG-LD38-02

Voxel based pseudo-3D warship fight? It has shaders and 2D/3D mode, just take a look.

VG-LD38-03

And a small hello from my 3D artist friend:

VG-LD38-04

Do your cardio before the workout and be prepared!

Ludum Dare Principle

Game jams is not a best place to show your OOP patterns knowledge. And well, code written on LD has no chance to win «Best Architecture Ever» award. Just look at this God-object class of our Protolife game:

God object class on Ludum Dare

Class with ~1K lines and 26 dependencies? I would have a serious talk with myself about this code.

But good practices still make life easier even if they take longer. This is how we decided to define our micro-buildings. Here is a simple turret:

Protolife small turret

More powerful turret:

Protolife t3 turret

«d» means «blue block», «e» means «yellow block», capitalized letter means «anchor point», e.g. turret muzzle.

Yeah, hardcoding all the coords would be much simpler, but this pattern system allowed us to quickly add new buildings – as fast as we invented them. This part would be first candidate for DRYing – so we DRYed it.

Do you guys use the best practices in your code? SOLID? GRASP? Unit tests?

Tags: ooc, programming, Solid