That's right. When you run a playtest it's not about those parasitic players. You're the one who should be under the microscope.
Not exclusively, and I talked about player feedback from playtests before, but I want to stress the importance of examining your own experience as the person running the game.
I'm looking out for two things:
Unfulfilled Wishes
Those mid-game GM moments when you think:
"I wish I'd prepared X"
"a random table of Y would be so useful right now"
"I wish I could just roll a die whenever Z happens to see how it goes"
A lot of the random generators in Mythic came from this, and the broad guidelines for Exploration Actions, which were introduced as a replacement to a rigid set of actions (set up camp etc).
Glimmers of Gold
I like to note cool moments that happen in the game, even if I feel like they emerged from outside of the rulebook, and think "how can I make stuff like that happen more often?"
In an early version of Mythic, each player had their own set of quests, and it was fun when they lightly contradicted each other. The Oath ended up being a better way to give the knights a set of objectives that occasionally felt mutually exclusive and forced interesting choices.
The Link
The link here is that I'm often testing for content as much as I'm testing the rules. Yeah, numbers will need tweaking, mechanics can get tweaked or stripped back, but I'm just as interested in everything else that goes in the book, and how that gets used in preparation and play.
--------------------------------------------------------------------------
This post was originally sent as a reward to all Patreon supporters, and is released freely on this site the week after its original publication.
If you want to support my blog, podcasts, and video content then head over to my Patreon.
No comments:
Post a Comment