I described Stars Fall Up as a “Communal Action” roleplaying game in the launch post. It’s a term I came up with myself, so I figured I should elaborate a bit more. In a roleplaying game that uses the Communal Action model, all players share equal power in creating the world they’re playing in, and determining the consequences of the actions their characters take. Many would recognize similarities to improv theater or collaborative writing.
This is the second Dev Log for Stars Fall Up. One good piece of criticism I got about the last Dev Log was that it was more about my personal philosophy on game design, rather than focusing on my process or the mechanics. It’s true, and the latter is where I want to be focusing with these Logs.
However, I’m also letting myself write about what’s buzzing about in my mind most, so a balance may have to be struck. This Dev Log is more about “game writing” than “game mechanics”, and I’m fine with that.
So, I’m writing about working on my game while I should be working on my game. Great.
For those who haven’t seen it on our Current Projects page, Stars Fall Up is a TRPG I’m working on—or, more descriptively, a mini-RPG for Us Damn Millennials.
A design factor that’s been on my mind a lot with this project is simplicity. That’s the word my brain goes to, but the full concept has more facets than the word “simplicity” can portray. I’m talking about simplicity in the way of “stripped of non-essential fluff and mechanics”. It’s the minimalism of game design. To be honest, this kind of simplicity is my modus operandi for creating games; I want to make games that other people who have little to no knowledge of TRPGs can pick up and be encouraged, not daunted, to try them out. I want mechanics that don’t feel like they have to be comprehended like the rules of a board game before any kind of fun can begin.