I spent the first few hours of the compo grinding out mediocre rendered sprites. It was pretty mindless, which is good as it gave me time to think about my mechanic. “Do I like this idea?” I thought to myself as I adjusted the specular highlight on my wooden cue ball for the umpteenth time. “Does it please me?”

Turns out the answer was yes; the idea I’m working towards seems decent, if underwhelming. The graphics I churned out on the way, though? Useless. Utterly, uglily useless. So I set out to prototype the thing, which went pretty well (hurrah! Prototypes in LD = meta-prototypes). Now to have a bit of a nap and dream about visual styles and blending modes.

It's pool. And also putt-putt. In, err, vector graphics.

The (only) cool bit of all of this is that the course layout (bumpers, starting positions, hole, etc.) is entirely data driven. I’ll need an editor to layout courses; that’ll be part of the game. Obviously. And, really, if I’ve already got an editor how much harder will it be to let players share courses & scores? And how cool would that be?

Tags: physics, pygame, screenshot

This entry was posted on Saturday, August 21st, 2010 at 3:37 am and is filed under LD #18 - Enemies as Weapons - 2010. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.