Blog
Filter By
Over the past few weeks, the whole team has been working hard on finishing the game. On the development side, our work has been mostly limited to small adjustments to a few key systems, some alterations to card balance, and seeing through the end of our final usability study. On the graphic design front, everyone has been pushing the files into final layout and Kyle has been producing some amazing art pieces.
In mid July, Oath crossed a major development milestone: design lock. This means that all of the core systems are no longer subject to any change. I still have some work on the solo game ahead of me and want to take the cards through another round of editing, but the game is getting very close to being fully done.
Today we're releasing the second public print-and-play kit for Oath, and it seemed like a good time to bring everyone up to speed on the game's development since I wrote to you last in January. I also wanted to take this opportunity talk a little about game development generally and my own personal practices.
Throughout the campaign, I've received dozens of requests (mostly polite) for me to write about how Oath plays as a solo game and with two players. This is something that I would have loved to talk about earlier, but it's always felt too early to really dig into how the bot works. But, recently the design has started to settle down and it seemed like a good time to share it's general shape.
Over the past few months, I've spent a lot of time talking about design, but I haven't gotten into how we organize our development schedules. With the release of the public print-and-play kit later today, it seemed like a good time to talk about how game development works. At least, to say a few things about how we make games here.