Blinders; Once More with Feeling.
First, the previous entry got mentioned on RPG Theory Review, making this the 3rd mention there of this blog, and the fourth of CSI Games.
Second, this is the second post of December 2006, I’ll do my best to keep at least two entries a month, which leads us to the next point!
Third, if you have any ideas or thoughts regarding CSI Games as a whole, or something that might be relevant, feel free to send me articles via my email and I’ll upload them. I think content from more contributors should be helpful, especially concerning that my writing is not that clear.
Fourth. There’s a good reason all the entries are shown on the front page: They are all open to discussion. Feel free to peruse and comment, and engage in discussion on all entries. It’s not only optionable, but encouraged!
There’s already an entry planned for the upcoming weekend, another for the week after, and yet another (and this one will be most interesting) for when Jessica Hammer completes her part of our “trade” :)
I think this is an apt topic for the last subject of the year. It actually closes a circle with the first post on the topic of Blinders (disregarding the Meta-Chanics post which is only a bridge). The issue came back to my mind because of the thread “Does System Matter?” on The Forge.
I looked at my own game, Cranium Rats, and what happened in its playtesting. I wrote in the manuscript that there should be violence and interwoven storylines. In the playtests the characters were mundane and normal if there ever were mundane characters. As such, violence was low.
But the storylines slowly began to cross with one another, work-place of one is the shelter of the other, one sees the third as he drives to work, etc. But there were no benefits to this behaviour, if the players had the characters and their stories cross-over or not, the effects would be the same. There is nothing changed, nothing gained, nothing lost, in each of the scenarios.
But those of the Indie crowd keep saying “System Does Matter“, and that was when System usually meant “Mechanics”. If I were to write in the game’s manuscript: “Storylines should interweave and cross-over, with the storylines drawing tighter and tighter and towards a conclusion where all the loose-ends are tied together”, and this were to occur in the game, then why do you pay someone to write game-rules and game-text, the mere idea is enough.
We keep saying we’re “beyond” Cops and Robbers, that this is not make-believe, but make-believe shaped by rules which help you govern what occurs.We have different rules for different games. We use rules to help maintain the mood and theme we want to introduce. But that means introducing rules, and not telling people what kind of game they want and how to get there. They can do it themselves by imbibing the source-material.
There’s a simple way to see if a game does what you want it to do, or rather, if the mechanics do what you want them to. Present someone with just the mechanics and see what kind of game emerges. This isn’t the complete game, this does not include all the background and colour, this does not include the interactions between the players. But this is not your goal, this is you checking if your mechanics produce the effect that you desire.
If the mechanics don’t do what you want them to, you have two options:
First, add mechanics that add what you want to the game.
Second, add advice telling people what they need to do to get the desired result. This is also fine, but be aware that this is what you’re doing.
After an hour and a half of chatting with Joshua A.C. Newman and Nathan Paoletta about this post, we discovered what was unclear in the post. I add it in this format because it’s a conclusion and it’s an edit. The article though unclear still has its purpose, which is served better once these are added.
- I’m not saying advice are bad, I’m saying it’s their job to point at what is already done by the mechanics.
- If your mechanics do something you don’t want them to, remove said mechanics.
- If your game doesn’t do something it should, add mechanics.
- If advice in your game REPLACE the mechanics, then something is wrong, and you should either add mechanics or remove that advice/thing from the game.
- It doesn’t work the other way around though, if something doesn’t work, or the mechanics don’t do what you need, you do not add advice.
And why say something once if you can twice?
If your gameplay does something, but it’s not included in the rules, but in the advice, either excise the advice or add a rule