Here's a blessed event insofar as I can finally talk about role-playing content and procedures that are ordinarily kicked down the road. For me, Adept Play is a rousing success insofar as ideas can be introduced and resolved enough so that "next ideas" can actually be addressed, and I don't have to spray down the entry point with fire-extinguisher foam or, for that matter, disinfectant.
You are here
Pretty much what the title says! General or specific, important or unimportant, obvious or not so much ... doesn't matter.
You can go all the way back to 1998 to see me saying, “I want to talk about point-builds and dice, so let’s get past some easy points about goals of play and get to the good practical stuff.” Twenty-one years later and people are still blubbering about “but but simulation." I’ve repeated this plea many times, ever more plaintively ... Can we fucking just talk about dice already?!
Justin gave me a list of questions or topics for this session, and I realized they made most sense in nested form. So I grouped IIEE and relationship mechanics into the larger category of Bounce and system diagrams (specifically their feedback or activity loops), then put the whole into the biggest category of design processes as an experience.
At this point, we needed to do three things at once. First, to make sure we filled in any missing points or caught up with anything Justin wanted to revisit; second, to lay down some important points about design as a process, as I thought we'd maybe strayed into play-theory at the expense of the real topic of "make a game;" and third, to take the time to address any topics as they occurred to either of us as we went along.
Here's another discussion of Quella Volta Che, aimed at the nuts and bolts of "what happens" in play, due to player choices and statements. We couldn't have done this without the previous session which focused so intently on content.
Here's the second session with Justin Nichols as I test my current notions of a Design Curriculum upon him. Last time, we talked about the desireable "reward" cycle of excitement, engagement with the procedures, and inspiration. This time it's about a particular structural rubric you can find attached to this post.
Dustin isn't a naive game designer, having produced Synthicide and generally navigated modern publishing. He asked me how to promote a game which did not fit neatly into "trad or indie," "OSR or story game," or any other dichotomy which people presented to him. Which is a perfect opportunity for me to stomp upon those dichotomies with my hobnailed boots, both for him and as a general PSA.