Timing
Games: , , ,
1 comment

Luke, who writes backwards like DaVinci did some more game design with help from #bbg (on irc.freenode.net – anyone’s welcome to drop by to talk browser game development, it’s a great place). Reading his note photo, it looks like he’s breaking cards down into Settings, Characters, and Monsters. There’s not a lot more info, just that he’s spending his hours planning out his game.

Continue this post

Breakdowns
Games: , , ,
2 comments

When Jim asked me how many hours I could put to So Play We All this week, I said “Negative three”. That turned out to be pretty accurate, as I managed to drop on the floor all but the three most important things for my week. Unfortunately, Oaqn didn’t make that top three so I sent $20 each to Jim and Luke. So, let’s look at what I funded this week.

Continue this post

Keeping Jim Busy
Games: ,
1 comment

Oops, got totally distracted by flying back to Chicago and forgot to write my So Play We All response post on time, so there’s $10 each to Luke and Jim. Late but not lost, here’s that response. (Luke didn’t post an update this week, so I’m only responding to Jim.)

Continue this post

Rewriting My Competitors
Games: , , , , , , ,
7 comments

It’s really clear that the polls So Play We All are measuring progress. When we have a quiet week, there’s a lot fewer votes. This week, there were 4, evenly split between Luke and I. The SPWA site doesn’t have code to handle ties so it highligted me as winning, which I guess means the bugfix is not my problem. :)

Continue this post

Two Turnarounds
Games: , ,
1 comment

I was really impressed by Luke in week five of So Play We All. He built a playtestable game fast and, more importantly, he learned from it. He’s decided to completely rework his gameplay. Player interaction wasn’t what he wanted and he realized it would be a huge amount of work to write. It’s not easy to decide you’ve spent time building the wrong thing, and that maturity impressed me.

Continue this post

Now Featuring Monsters
Code: , , , ,
5 comments

The So Play We All theme this week was “core game objects” and the time budget was 3 hours. I did did well for myself, time to review the others’ work — both of which included monsters.

Continue this post

SPWA Week 2: Funding and Forms
Games: , , ,
6 comments

So Play We All is partly a motivation hack, with teammates/competitors and penalties to make sure we each put in time towards our games. Luke’s job sent him to a conference for almost all of the week, so he didn’t get to do any of his hours. He’s paying us both $20. To keep anyone from falling behind, we’ve tweaked the rules to say that anyone who pays the penalty for missed hours can make them up when they have the time.

Continue this post

SPWA Week 1 Response: Code Hassles and Kittens
Games: , , ,
2 comments

This week in So Play We All our topic was “Signup” and our budget was 4 hours. I originally pushed for more time, but I ended up glad that it was short as I hacked things out on the last day. I don’t need to belabor that, let’s look at how Luke and Jim did with their games.

Continue this post

SPWA Week 0 Response: A Strong Start
Games: , , , ,
2 comments

As mentioned in the rules for So Play We All, we’re required to respond to each other’s progress update. I’m going to be doing the Oaqn progress updates on that blog but the feedback here, mostly to keep that blog focused.

Continue this post

So Play We All
Biz: , ,
8 comments

Peter Harkins, Jim C. Gadrow, and Luke Hutscal are each building an online game as part of a contest between us. Every week we’ll pick a new area of our games to code on and budget how many hours to spend on it. Every week, someone will be judged to have done the best. Anyone who doesn’t put in the time pays the price by funding the others’ games. Anyone who quits has to delete their entire codebase and all backups.

Continue this post