I'm pulling on the driveway. We all know what that means. It's time for their drive to work.

Okay, so today's topic is playtesting. So whenever I do a topic, normally in the morning,

I figure out what my topic is, and then I search and look at the previous drive to works

just to make sure that I haven't done the topic before, because I'm 1100 in, so I've done a lot of topics.

And I had, in fact, done playtesting.

In fact, I've done it twice.

But both were in the 100s, and we're not only 1100.

So that's like 10 years ago.

So I decided that every 10 years I'm allowed to talk about playtesting, things have changed.

Ten years ago, we were back in the design and development

era. Now we're in exploratory design, vision design, set design, play design. So, anyway, I'm going

to talk about playtesting now. I'm sure there's a little bit overlap from 10 years ago,

but enough differences that I thought was worth doing a podcast on.

And the reason I'm doing this is a couple people have asked me recently on my blog about

they want more details of how we playtest. So I thought I would get into how we playtest.

Okay, so let me start by talking about the most important tool for playtesting.

So in order to keep track of all the cards, we have a database that we call Drake.

And the idea is every card that exists in magic is in Drake.

And not just every card that exists, every card that we are currently working on.

Like in order when you make a file and

you work off a file, the file is in Drake. And the idea is it's so that everybody can interconnect

and work with it. And so if I want to, for example, see how a certain set is going, I can go up

...