Beyond Solitaire Podcast 147: Jason Carr on Development at GMT
Transcript
it's ad break time I'm proud to announce that Beyond saler podcast is sponsored by Central Michigan University's Center for Learning through games and simulations and as usual they're up to some amazing things their next game hydrologic cycle is scheduled to come to Kickstarter on March 26th clgs also continues to offer classes and partnership with Gen Con the next course Jason Fury's crowdfunding with confidence starts May 6th and we'll teach you all about board games and crowdfunding go check it out also I'll include a final plug for myself if you like the show and want to support it you can do so by going to patreon.com beond Soler thanks to listeners like you I've been able to keep upgrading my equipment subscribing to streamyard and more but for now let's get on with the show hey gamers is Liz David from beond soliter and I'm here on the Pod with Jason Carr he is the director of game development at GMT how you doing Jason I'm doing really well thanks for having me yeah it's fun to finally have you on uh so you actually do a lot of things for GMT how did you get started with them and then how did you end up as the Director of game development yeah I I mean I've told that story a couple times and so I'll keep it on the shorter side so I don't bore people to death but um I've been with GMT for uh going on eight years now um and um started out doing development for the coin Series so the very first thing that I did as sort of a standalone development uh project was working on Gandhi with Bruce Mansfield and Scott Mansfield um and that was really fun and got me kind of in the door but if I'm really being honest the thing that made it uh possible for me to do game development was um working with
Mike Bachi on tank duel um Mike is a good friend and he's a way better game developer than I am and that was his first published game design and he brought me under his wing and kind of carried me along showed me the ropes taught me what I was taught me what to do um so I'm listed as the developer on that but Mike probably did 85% of the development on that game and um and Gandhi was my first like Standalone thing so um once that shipped and it and it was well received and it was clear that that I had done you know finished a project and actually shipped something Jean Jean and I started talking about doing more and one thing led to another and I ended up kind of running the development show oh that's awesome so I guess you mentioned it's it takes a lot of training I guess to to become the developer that you are today um what does it take to actually be a good developer what are the things that you had to learn to do to get it right yeah that's a really good question because I don't know if everyone really understands or even thinks about game development the same way um so for GMT when we talk about game development we mean um this interesting mixture of product development where you're thinking about what the game should be and representing kind of gmts interest in the game um and then project management right you're just keeping all of the different parts moving so what's going on with play testing what's going on with the rulebook what's going on with
the design elements if you ask the designer to redesign something um art is a big part of that so coordinating with the art Department to make sure that art is done well and right um if we work with an editor coordinating with the editor um and then there's a certain aspect of design sensibility that's associated with it as well like being able to play a game and say this isn't Fun and here's why or play testers are complaining about something but they're they're not complaining about the cause they're complaining about a symptom and understanding how to fix that and make suggestions and work with a designer to fix games and make them more fun it's it's a there's a little bit more of art than science in that world and it can be really difficult to to explain it but you know it when you see it oh no you know it when you see it that's tough it's the worst answer of course no it's okay that's what we're all about on this podcast um so when you talk about all those different aspects of the work I think what do you find to be the most difficult aspect for me it's the writing so I don't hate writing I mean I was a philosophy major in undergrad and um I don't think anybody who hates writing goes and studies philosophy because you do a lot of it um and over the years I've written lots of articles for inside GMT and and written several Rule books from scratch but taking what somebody else's intent is and figuring out how to express it in plain English that is as
unambiguous as possible is never easy it doesn't matter how good you are at writing and so think that that can turn into a little bit of a slog sometimes um and so you know working with designers sometimes it's easier for them not to do the writing it's easier for them to explain sit down show you how the game works and for the developer to do the actual work of writing the rulebooks other times the designers bring you Great rule books that are really easy to publish with minimal changes those are great I like those um but no matter no matter what the circumstance is um writing is always a really big challenge so it sounds like it's not just the writing itself it's the learning how to express somebody else's intent yeah so one of the interesting things is that I've been doing some design work myself so Jason Matthews and I have a game in the Twilight Struggle family on South Asia and working on the rulebook for that has been much easier well we're not really writing rule rule book yet but writing out the rules the rule changes for that has been a lot easier because I'm not playing a middle man between the designer and the gamer I am the designer um and so my intent is much easier to express um the hard part there is getting Jason to do anything sensible because he just he just does whatever he wants he's out of control yes I I can I can see I can see that being the case so does that mean that you think it's actually easier to design than to develop I think they're apples and oranges I mean a design design is about
I think design when it's done well was taking a taking a thesis and expressing it through game so um if I was taking um if I was taking an example I'll take Gandhi as the example um the thesis of Gandhi as I understand it from Bruce is that um there's a um there's an analogy between Insurgency and non-violent resistance that can be expressed through um through a study of the similar and and the differences between the two and um he's building on the work of Eric a chenowith um and her uh Research into nonviolent movements and when he read her book he immediately said wow the coin series expresses this really well so his thesis was brought to the coin series he used the coin series to express it and that's just a very different type of mental exercise than doing development where I was asking myself questions like well these mechanisms actually reflect that thesis um would a gamer who's coming and sitting down at the table be able to understand the levers that are available to them in the game system and and play the game in a way that was an expression of the designer's intent and then there's all the other things that are on top of that like is this game learnable is it playable is it fun is it balanced and so I don't think that design development is is harder than design but
I do think that they OCC by two very different and distinct mental spaces and that can be um a bit of a challenge when designers try to do development because I think that they're used to being in a design space and moving into a development space can be hard oh that's interesting so since you moved from development to design do you think that that transition's been different for you oh absolutely I mean I I think that I have a tendency to put in my design put the cart before the horse and so I start thinking about development problems way before I've soled the design problems and there is a sequence to that you have to you have to know what your thesis is before you can refine it you know what I mean yeah no I've said that to some students about their papers in the past right so what do you think that an ideal relationship I guess at least for you I know it's everybody's different um between a developer and a designer would look like yeah so I wrote an article about this for c3i um and I think it was issue 35 and it and it my argument is that the designer brings the thesis and the designer brings the intent and the job of the developer is to refine that thesis and to make sure that its expression isn't sullied by the other elements of the game so that is to say um you might have a great thesis but the rule book is unintelligible did your thesis get communicated probably not um you might have a great thesis but the game is unbalanced well there are cases that I know of um where the imbalance is
part of the thesis the one game that comes to mind most clearly is John penis's game on uh Vietnam hearts and Minds he says right in the design notes that the game is designed in such a way that after a certain point um the blue the US is not going to win um and that that was an intentional design choice or well I don't isn't going to win it's too strong but is unlikely to win but usually imbalance in a game um and I I guess we could have a whole long conversation about what game balance actually is without without any settling on anything but at least as I think about it it doesn't necessarily mean equal win it means the model is being expressed the thesis is being expressed and so right in that world where Jon wanted his game to be more difficult for the US player to win the longer the war drug on if the game wasn't working that way um that would be a development problem that would be something where a develop ER should have pointed that out and corrected it with the designer at some point in the process um I I could think of a dozen different ways this could come through in the art in the um in the language used in the cards um you know I did I did uh competitive speech and debate when I was in college and one of the things that we would often do is argue the um argu about the language that was used in a specific uh debate case and argu the language that was used actually
went against the point that was being argued and uh that is one of the the things that I I think about a lot when we make games is like is the whole complete package forming an argument for the player uh to work with so this kind of leads me into I guess kind of where I wanted to spend a lot of our time uh which is when you find that a game is not expressing its argument well and you're in charge of development um who actually does the fixing and how do you negotiate that because at what point are you putting words in the designer's mouth versus correcting what they said yeah I mean huge challenge um and I think the answer is a is as nuanced as the problem so just as there are a hundred different ways that a game could accidentally Veer from its thesis or contradict its thesis or fail to express its thesis um there's a there's a hundred different remedies for that problem I think at its core every solution to that has to start with a relationship and I think where a lot of these games get off track is um when you find that games have been thrown over the wall uh to the publisher and some sometimes that's because that's how the publisher works
and that's their desire and sometimes that's because the designer doesn't want to be involved in development um at GMT we want our designers involved all the way until the game goes to the printer so um you know Mark Herman was involved in Rebel Fury until the day that that thing went to the printer and he and I were talking on the phone every day for the last couple weeks just making sure yes that every detail was correct but also so does this look the way that you want it to look to convey what you're trying to convey and um is this language communicating what you want to communicate about the period about the game about the time so you know Jean Likes to say that we like games but we love people and that is how we solve this problem um there are games that have been brought to me that have had a thesis we've run into problems with that thesis I've gone to the designer and said hey I don't know what to do here what do you want to do and they've said I have no idea I can't solve this problem and then it becomes a collaborative problem solving exercise where yeah maybe I'm just as involved as in design or more involved than they are in trying to solve that problem but I never take that problem and make it mine it's never my thesis it's never my game um it's always about telling the story the designer wanted to
tell because ultimately that's the thing that we agreed to publish was that designer's view and so um that is a little bit of a non-answer to your question for sure but but I think it also reflects the kind of games that we tend to make because we don't make games that that are just trinkets like our games generally speaking are trying to tell a story and that story is a particular one that the designer wants to tell and even our Euro games like take dominant species dominant species is still a particular type of experience Chad was opinionated about how that game was supposed to work and so it would never work for a third party to step in and take that away from him and make it into a house brand or a particular flavor of game um it would it would lose the essence of what made that game special so I'm not saying that can't work for other Publishers I know other Publishers that are great that have house standards and they take games and they publish them to that set of Standards there's a market for that there's a purpose for that it's just not what we do your game is a trinket you heard it yes every game that we don't publish is a trinket I'm sure that'll get I'm sure somebody will snip that out of this interview and that's going on Tik Tok yeah that's right uh no I'm playing um I might leave it in just cuz it's funny but no this is a polite rational conversation everyone
um but um so this also kind of leads to you know if you're trying to help bring somebody else's thesis to life um how do you deal with your own I guess opinions about and reactions to that thesis yeah I don't think this is any different than editing so as an editor right you can never not bring yourself to the text um to some degree and and might be that there is text that you simply can't edit because your opinion about it is is um too difficult to set aside right um and so editorial bias is real it exists it's also a good thing um that that editorial bias can sometimes help you check back some of the things that might be present in a text that would otherwise uh Mar an argument um it's where you get to look uh and find people's blind spots and I think that's 100% true in game development um the simplest example of that is a rule that seems completely clear to one person may be completely confusing to another and as an editor I want to bring that perspective as a developer I want to bring that thinking so um to that end I actually do reading when when I pick up a new game when I when I started working on fall of Saigon um I asked Mark and volco for a reading list and I said what do I need to read and I read black April by V and I read um I had never read fire in the lake by Francis Fitzgerald so I read that um and I read um max Hastings Vietnam and epic
tragedy and I didn't want to work on the game without having the base context to be able to interact with the arguments the designers were making and so um that informed the design of that game I think Mark Mark Herman's talked about this before but like he had the idea for how the Paris Peace Accords process in that game should work he knew he wanted it to be a certain process that you went through and he knew what he wanted the steps to be but the particular Rewards or punishments that happened based on the different outcomes of that were completely changed from his intent by the time the game was published and they didn't come from him they came from Joe duur and Steven razus and myself playing the game over and over and over again and going back to Mark and saying here's what we think provides the correct incentive and then he would come back and say well I agree with you about this but I disagree with you about that and so then we would take that intent back and we would internalize it we' play again play more and we come back and say okay we understand what you're intending it to do our experience is that the the reward you're giving has the opposite effect to what you want or it has an orthogonal effect to what you want or it has no effect and that's how we started to solve the problems that popped up because of this novel thing being bolted onto an existing game super hard problem space By the way um and I was talking to Mark last week and he brought this up as an example of kind of how good development is collaborative with a
designer and it's a an exchange of ideas back and forth not just him giving us something and we polish it and put it out there in the world it also sounds like development is a we sort of Affair so um how often are you the soulle dev on various projects and then how often are you working with the team because you mentioned um Joe and Stephen like you know who um who's typically working on games with you and then how do you'all negotiate that aspect of development yeah that that's a really good question and it again depends on the project but we are moving more and more towards a model where we want to have lots of eyes on every game that comes through so I don't want to assign a project to somebody and they go off with that project and disappear and then come back and say it's ready to go to the printer here we go um I much prefer that we have games with two or three people who are passing the game around and the most common way that happens is that we involve other gamers in testing so um Stephen is one of the people who who tests a lot of games um because he's good friends with some of the people who do development for us um NB non-breaking space does a lot of testing for us um a lot of the people who do that are designers in their own right because they tend to have a mind to think about games but everybody brings something different to the table so um somebody like Sten is great at thinking about models and so if I have a game that's model heavy and is really trying to make a statement about
something um I almost want his opinion like he very likely will be able to see what that Designer is doing much more quickly than other people because he's trained how to think about those those models um and I think that that's that's you know kai Jensen does a lot of that for us looks at games um thinks about them she has her own point of view and it's um definitely different than mine and that's awesome because it means that we're seeing different things we're seeing different possibilities about the game um so I try to make it much more collaborative when it comes to though like okay this rule book needs to be Rewritten that's like a oneperson job it needs to have a single Voice through it and so the writing might be done by one person and then it's edited by somebody else and then it's proof read by other people and then the game is blind tested and played and um that's where many hands make light work just to be honest and that's why that's why we're really focusing on building a team instead of getting like one person and dumping everything on them nice so you've also kind of mentioned development and play testing kind of in the same phrasing pretty often so um what is the relationship between I mean obviously a developer needs to play a game a lot in order to you know get their get to the where they feel comfortable commenting on it and developing it but um you know who are you play testing with at various stages and what does play testing mean at various points in the process yeah so I think I think of play testing as four
distinct things so um there's there's play testing as a developer where you are validating the thesis and you might see something that doesn't line up with your expectations and then you're validating alternatives for a designer so um let me think of an example of this uh one example of validating a thesis would be when we were play testing Red Dust Rebellion so um Jay the designer gave us a game he told us what he wanted it to say as we started internally testing it and I guess pressure testing his thesis um it became clear that a couple of the mechanisms did not say what he wanted them to say and so Adam uh the developer didn't just go back to him and say this doesn't say what you wanted to say he sat sat down with the game and worked through Alternatives and went back and presented a range of possibilities uh we could do it this way we could do it this way we could do it this way which one do you think suits you the best and I think in that example it's been a little while since that since we were actually doing active design on that but I'm pretty sure that Jay actually came up with like a fourth option that none of us had talked about um but that dialogue was really important to getting his thesis right and so that kind of internal development testing is one thing that I mean by play testing then there's um testing with like a broader audience Still Still for the sake of making sure that the game tells the story that we wanted to tell that it's fun that it's
playable um and that's what we do with our kind of broad play testing groups so we have something internally that we're really happy with we put a a note in the newsletter saying hey we would love to get more people to play the game um usually in that world we're testing something like a bunch of scenarios and we're testing to make sure the scenarios are complete you know they have all the instructions you need to set them up and play them we're testing to make sure they're fun they're relatively balanced things like that but at that point we're pretty confident that the core gameplay Loop that it tells the story we want it to tell that it's fun to play and what we're doing in this second phase is kind of tweaking it um the third phase of testing is really centered around polish so in this world we're doing things like okay we have a solitaire bot got to test that and make sure it's working um sometimes developing the soliter bot turns up problems with the game that's become increasingly a tool that we use is when we design a Solo System a lot of times the Solo System actually shows us stuff in the game that was not working the way it was intended to and so we can fix those things we're doing testing on any of those kinds of tweaks and changes fine-tuning balance happens here so this is where like the game a coin game the game might be almost completely done but we're still asking ourselves like should this Victory condition be at 28 or 30 and how do we decide which one to put it on um how do you decide put it
on um divination like there's no there's really not a good answer um a lot of it is feel um a lot of it is there is a math component to it because a lot of these Victory conditions are actually if you look at the condition and then you look at the and you figure out what the maximum value is you'll start to see oh all of these are 90% of the maximum value so sometimes there's math involved um sometimes it is just gut feel like we we don't we don't have the ability to play test those games to the degree that we could get statistically significant information about where the victory condition should be um that's just the reality of it so sometimes those things do need to be tweaked post publication I can only think of one game where we've changed Victory conditions post publication so that's I guess a good track record actually um and and then the last kind of testing is what we call like blind testing which is where we take the final set of components the final rules and we give them to somebody and ask them to play the game and tell us what they found and this is really kind of much more focused on AATA elimination like making sure that there are no mistakes in the game that it's playable out of the box at that point we are very very rarely finding any gameplay stuff or any kind of change in the user experience or the usability or the components themselves um I mean obviously if those things come up at
that point we fix them but we're really laser focused in that on is this a playable game is somebody going to be able to pick this up and and actually learn it and play it if they buy it because we don't the last thing we would ever wanted somebody to give us their money and then like well I feel like I got game that I can't play yeah so speaking of you mentioned you know you can't get statistically significant Victory conditions I was I was going to go this direction so let's be real GMT makes some chunky games yeah y have some very long scenarios um you know some of y'all's games are deeply intimidating in terms of how long they are it's a commitment and um you know that doesn't stop me from being a fan but how do you test that seriously like how much testing does it really get and as a developer you know are you winging it on some of those scenarios or have you really gone through every single one so as a developer I am going to make sure that every scenario is playable and so I'm taking a step back from so these bigger games I'm taking a step back and I'm asking myself how could I verify that this game is in a good State and the answer to that almost always comes back to what I said earlier that we have game we we make games that have thesis and that means that they have models that underly them right and so for us testing is very often about the model and making sure the model is good and then scenarios become a set of
inputs that generate a set of outputs and we if we've tested the model thoroughly we can predict what we think those outputs should be and as we play through the scenarios we can check and say are these outputs corresponding to what we expected them to be based on the inputs so for a game like a coin game um yes all the coin game scenarios are played by every like I played every scenario in in um fall of saon including the combined scenario um Joe played every scenario in Sovereign of Discord including the full crazy campaign now did we play those enough to get statistically significant information no but we knew that the underlying model was solid because we had done the testing on the model and also we were leveraging fire in the lake which is a known quantity for a new game that's super long and I'm gonna pick on I'm gonna pick like the worst one right so we have a monster game on p500 called battle for battle for Sicily um I don't think that game is going to get play tested the way that like a Euro game would get play tested I I I don't think I know it's not going to get tested the way that a Euro game would get tested where you have a play test form and people play test it and then they write out all this stuff instead what happens is some of the scenarios get played more often and
players look for things that don't seem right with the model so in a game like that which is a big monster hex encounter game you're looking for things like does Supply rules tend to put units out of Supply where they shouldn't be does movement let units move farther than they ought to does it make sense that this Army is able to defeat that Army um do do battles happen as frequently as I expect them to um and asking those kinds of questions and tweaking the parameters of the model so that those things line up tends to solve the balance problems with those games over time now that said nobody is playing battle for Sicily for balance right they're playing it for the sprawling narrative the story it tells the scope the ambition um so yeah that in that sense play testing has a different function and a different mode for a lot of our really like our big long sprawling games as those things scale down and you start to talk about shorter games or more um more abstract games like um you know like battle line or um welcome to Centerville or even dominant species um those get play tested a different way they are play tested for balance they are play tested for for victory outcomes and much more traditionally oh that's really interesting I always did wonder about that um
so when something goes wrong like when you have to issue replacement counters and when you know there's you know you have to do AATA on BGG um is that also something that the developer is partially taking on and also you know I'm sure it doesn't feel good but like how do you respond to that at this point it's not your first radio so yeah um so I'll tell you about my first radio because it's instructive um the first game that GMT printed that I worked on was Gandhi and Gandhi has this really awful but not that impactful AATA which is on the player aids for the Muslim League faction it lists on the operations all or sorry on the special activities all the no it's on the operations on the operations all the operations that the special activities can go with so it it has like an extra line of info that shouldn't be there and as soon as you know that that line doesn't mean anything you just ignore it and it's like it goes away so it has incredibly low impact on the game but the first time especially if somebody's never played a coin game they look at that it is so confusing until they are told oh yeah that shouldn't be there and I remember going into Jean's office um because we got an advanced copy at the weekend at the warehouse and we opened it up and somebody was playing it and they walk over to Bruce and I and they said does this look right to you and showed us the player and Bruce and I just both turned like white all the blood drained out of our face we're like What are we gonna do um and so we went and talked to Jean and Jean was like yeah well okay first of all welcome to board game publishing like you you now
are officially designer and developer because you have shipped something and look the thing you shipped is broken um but I mean it's kind of like you you've never you've never been a bartender until you've dropped a glass like it's it's that kind of thing um but he also immediately was like okay well what do we need to do to make it so that people can actually enjoy the game and it very quickly became apparent like well what we need to do is we need to post the information so that people know to ignore that line do do we need to create replacement stuff well we can put it online if people if it really bothers them we can give them them the ability to print out a replacement um but our number one priority was can people play and enjoy this game and the answer was yes like yes this should not stop someone from playing and enjoying the game now there are games that we have published where that's not true and so that's when when you start to talk about okay well well how do we fix this and make it right and and Imperial Imperial struggle would be a good example of that like there were mistakes on the cards and and some helpers on the board that were materially misleading and so we wanted to make sure that that was fixed for players so that they could actually enjoy the game and not just constantly be thinking about oh yeah I have to remember that that's wrong so it's a it's a dance there's a there's an art to it I think we've gotten better at just not shipping prod problems um that that's been one thing that's happened is is we've just seen the defect rate in our products going down um but the other
thing is when you make a mistake making it right in a way that serves your customers is important and that's why we that's why we started doing our AATA counter sheet our annual sheet this year and that that counter sheet had counters on it from games from multiple years ago because we didn't really have enough mistakes in a year to fill the whole counter sheet which is nice so um for 2024 I'm hoping it's a half sheet and then for 2025 I'm hoping it's a quarter sheet and just keep working and improving and iterating from there so that's that's how I think about it um you know we the thing at the end of the day that that I think that if I could if I could say one thing to people people about this it's that folks need to remember that if you have two components in a game you only have one relationship between those two components right they they relate to each other and that's the only relationship but as you add a every new component you add you add n minus one the relationships are n minus one right what that means is that a game like a GMT game that is twice as complex as some other game is not twice is hard to get the AATA out of it's an exponential curve harder to get the AATA out of and so the the kind of complexity that our customers enjoy is also the reason the Arata is in the game and no matter how hard we try the human brain is just not built to harness and
to control that type of complexity um you know my day job is a software developer and software developers know this to be absolutely correct like if you're a software Dev you have to write tools to help you deal with the complexity and there are bugs in your tools that help you handle the complexity of the software you're writing and so as a as a game developer I don't have the ability to harness a computer the same way that I do at my day job and that complexity can get out of control really fast so a big part of development is reducing complexity so you reduce the surface area for mistakes but our customers enjoy complex board games that's what they're buying from us and part and parcel of those complex board games is going to be that the complexity sometimes escapes the the harness that you've got it in it slips its bit you know you got to give it the Spurs and get it back in line but um but that's how that's how ARA happens that's where it really comes from it's not necessarily carelessness on the part of the developer or the or the publisher as much as it is just wow sometimes these things are really hard to think about and obvious things slip through because your attention is elsewhere or or the model had side effects that you didn't think about and um that complexity also exists in just producing the games like there's the printer the artists the editors the developers the designers there's the logistics associated with it you know there's there's more to keep track of than I would ever have guessed
when I first got into the industry so uh none of that's an excuse there shouldn't be any mistakes in the games period but that is why they're there I mean it's good to know um I get anxious now that I've started to do editing it's like oh no like what am I going to let through yeah that's how it goes I mean it's notable like I said you you'll drop a glass and then it's like okay well I didn't die so now I know and now I know what not to do next time and uh now I'm a full member of the club you know so that's how that's how it works fair enough fair enough so you know you've gone into design as well do you have a developer for your Des designs and like how does that feel for you that's a great question so for the Twilight Struggle game um Peter Evans is doing the development for that game so Peter's a a longtime Twilight Struggle player and um his insights into how the game engine actually works are really helpful because sometimes people who have played the game so often actually have more insights than the designer themselves um because as a designer what I've noticed designers pattern tends to be is they work on their game super intently they get it out into the world and then they don't want to look at it again for a while and uh that can mean that by the time they come back around to look at it again other people have become the expert on their game and Peter's one of those people he's played he's played the game a ton um he knows it very well there's also um
a a pair of guys who worked on Twilight Struggle Red Sea who have been bugging Jason and I got a copy of the new game and they played red SE hundreds of times um during during play testing so people like that those kind of like super play testers can often do a lot of development for you even though they're not your developer um so it it feels good like it's nice to not carry that burden on my own I don't know if I've ever fully really given it up and we're not at the point like it'll be interesting to ask me that question again in a year um um when when I've had to go through like maybe some of the more painful parts of development because right now we're still in the ideas like we're still doing crazy crazy stuff and trying it out to see what happens um like we have our core gameplay Loop and we know how we want that to work but it's like well how crazy can the card effects get how weird can the effects on our tracks get um how do we really like are there other ways we want to represent Chinese influence in the in South Asia um and we're experimenting with those things and that's much more design work than development work once it comes time to pin things down I bet I'm going to be like the designer from hell like I'll probably be the exact person that I hate working with the most um just you know that's the way these things tend to go um so I'll be really you know um night witch's files have gone to Kevin and you know to our artist and graphic
designer you know David and I did not have a separate developer we test but of course night wish is a small game so we tested it extensively ourselves and then had play testers give us feedback um but I mean it's okay if you feel this way do you think the games need a developer or what size do you think they do no I I think you know especially when you have a code designer um a lot of the things that a developer does are really having like a second pair of eyes and code designers can provide that um also like you kind of you kind of hinted at like there are games whose scope might be such that you don't need a developer um I think about games uh that are that are art pieces for that especially so I'm thinking about like Dan Bullock's uh the gods will have blood like I'm not sure what a game developer would have added to that um and that's less a function of the scope of the game although it is a very manageable scope and more a function of the thing the game was trying to do um at least as I understood what the game was trying to do I I do think they're probably is an inflection point where developers become less valuable in a smaller game but I think that that there might be another inflection point where they become valuable again because you've gone so lean that every moving part becomes so important that you need help to make sure they're all correct um so I'm thinking about like uh some of the micro games that are out
there like I'm thinking about a game like Love Letter like I wonder how did love letter get to be so tight was that entirely the designer I don't know the story is that entirely the designer or did somebody else step in at some point and say we're gonna like take some of these edges off and refine some of the things to make it smoother and Tighter um I would love to know but I think that that can be really hard like my experience has been that less complex games when you want to try to make a simple game that still has a high degree of um it engagement with a player that can be a really big Challenge and that's where having a team is actually a lot more helpful interesting so if you have so you're talking about kind of expressing what a designer thinks you know maybe going back to designer and telling them that something doesn't quite say what they think that they were saying um what happens when they disagree with you and who gets the final say yeah so my rule is the designer wins because we brought the designer in we wanted the designer's game so at the end of the day when we sign a contract with a designer we're saying we want your vision we want your thesis we want to tell your the story you want to tell and if we disagree on what that is um the designer gets the trump card that said my goal is not to tell them it's to persuade them so I'm not going to a designer and saying I think this tells the wrong story I'm going to the designer and saying hey I had a I had a feeling like this was wrong so here's what I did I went and I got these
people to play it and this is what they said they think this means so you know like how do we fix this perception how do we fix this experience and I've never had a I've never had a designer tell me oh 10 people thought that this said the opposite of what I wanted it to well I'm not going to change it like that's just never happened so maybe we just work with really great people um but but I think that there's I think that game designers tend to be thoughtful people and they tend to be open to ideas that's why they're doing game design design and so that means that if you come to them and say I don't think this does what you mean it to they are curious and they go well why do you why do you say that what makes you feel that way and and it opens the dialogue nice so have you ever however um been overridden on something that just really hurt and how did you handle it it's okay if you can't tell us the details but I would be interested no I haven't I have been told by a designer that was that they would go along with a change but they thought I was wrong and and that game that game came out and uh they and I'm not gonna say what game it was or who the designer was but they have since told me that I was correct so that felt good I I think I think there's definitely places where I've had development instincts and the designer has talked me
out of them but again that's much more of like a dialogue situation and and I would say those things have definitely there's definitely been cases where the designers have said no I think this is the way I want it to be and the game has come out and they've been it's been fine it's been laed um the most common case is that I point something out and the designer says no this is the way I want it to be and I say okay and then the game comes out and people point out what I said and the designer says well that's how I want it to be and then other people say yes I'm glad it's that way and there's just a difference of opinion because of taste right and at the end of the day I'm never going to push a designer to overrule something or like change something because it's not my taste um if I'm if I'm going to them and saying I think you need to make a change it's because I think there's a an outcome for the player that is not desirable right not just that well some people won't like this so this also sounds like you know you talk about being persuasive about you know wording your choosing your words carefully uh you work with a lot of different people and I feel like that makes you probably an expert at giving and receiving feedback so what are some of your personal strategies for that and tips for people who are commenting on games play testing games you know looking at each other's designs U what have you what what are some of your road tested uh rules for that that's a really cool question I was also a manager for 10 years so giving feedback was like my
and butter like every day at work um so I I think about this a lot and I'm pretty passionate about it I think as a designer learning to receive feedback is very important and so what I would say to that is like first of all like your number one job is to understand not to refute so it doesn't matter whether or not in a play test that gamer walks away from the table and says I hated that game what matters is that you understand why they felt the way they did and so if they walk away and they say I hated that game and you have no idea why then that play test was waste um so as a designer you should be curious you should be asking questions you should be understanding what kind of games they like why would they say that they didn't like this what what was it about their experience that was positive or negative and asking good questions is the difference between a great play test and an awful one and by the way I think that's why in-person play tests are so important because you can have an interactive conversation with someone and you can say okay well how did you feel about the game and they say I didn't like it you say why well because I thought that this this thing in the game was useless well I'd be interested in thinking why you think it's useless like what is it about that that made you think it was useless is there a way it could have been more useful did you think it was useless or did you not understand how to use it um and getting into that with people's really important so as a designer there's a lot to think about there
as a developer giving feedback um I think one really important thing is to remember that like you're dealing with a person and so you know you are you are not dealing with a predictable system like what I mean by that is you don't know what's going on with that person when you chose to give them that feedback so I might call you know Jean on the phone and say Jean I need to give you feedback about your game and he is in some head state where he can't can't hear it and so the first thing that I've started doing in every conversation is I've started out I first of all I always call people on the phone if I need to give them constructive feedback giving that via email is just it's completely impersonal they can't hear my voice they can't hear the tone of voice I'm using they have no human indication to go along with that feedback and I mean I learned that the hard way like there was a designer that I needed to give some negative like feedback to and I did it via email and that was an ABS abute mistake and I should never have done that because it didn't let me convey that I actually cared it just came across as like oh no I don't care about you I don't care about this um and so I've learned uh my very first manager um was an old brand guy from Proctor and Gamble he'd been there for years and he told me if you really want to communicate with someone you have to pick up the phone um and so email's great for information exchange but if you want to communicate pick up the phone so that's number one number two is I always ask at the beginning of the call is this a good for me to give you some feedback on your
game and if they say no we don't do it and even just asking helps put people in a position of being less defensive and sometimes people need that they need to prepare themselves like oh okay we're about to have a feedback conversation cool I'm gonna put my curiosity hat on instead of just being offended by being what said you know and um I think that those two things have served me super well well obviously like being sensitive to what people you know their priors might be or what else is going on in their life is always really important but sometimes you can't know and just that act of asking is this a good time can be really really powerful um so yeah those would be my big things is like curiosity is King when you're trying to get feedback so I've learned to be afraid when your name pops up on the phone and also that I would be terrible at feedback because I'm a millennial and I don't do phone calls yeah right I mean you're not wrong feedback in the 21st century is going to be an interesting thing so and everybody should be scared if my name pops up on their phone it's a bad day if that happens all right so I have one more kind of meaty question uh before we just kind of go into some fun stuff at the end um and it's that so I know that you've done um some solo modes you talked about a system for doing solo for coin I know that you did the solo for uh Twilight Struggle red c um are you a solo gamer yourself and what mindset goes into making GMT solo modes
specifically yeah that's a great question so yes I play solo games um my introduction to solitary gaming came from Mike berelli um he I was working on tank duel and I got um I got frustrated at playing it two-handed um because it's it's a it's a hand management game so it's not the most solo friendly game right and I actually dreamt about how to do a solo system for it and I woke up at 3 in the morning and I went and got my laptop and I was sitting in bed working on my wife was like would you go do that somewhere else please um but I couldn't help it it was compulsive um and I called Mike the next day and I told him here's what I want to do I have this thing figured out he's like that's great you should absolutely work on that also you should probably know what else is out there because you're working in a vacuum and it shows um so he and I got on uh got on vassel and played ceria which he had finished working on with Joel TOA and that blew my mind just absolutely blew my mind I didn't I'd never seen some of the mechanics that were in that game with with pulling cubes out of a bag and chits out of a cup and that kind of stuff just never it's not that's not that common in um in Solo games outside of wargaming yeah um and then we played we played some coin and I saw the coin Bots and I was like okay this is maybe a little more familiar with the flowcharts and everything um and I went deep down that rabbit hole
so I was just super into it for a very long time and I mean I still am I love Jerry White's games um the enemy Coast series especially um I've been play testing infernal machine at super fun um I love Joel's solo games um I really love fields of fire and John Butterfield solo games so I play I play a lot of solo stuff now and I play the modes for all of the Euro games that I can get my hands on so like Morton um Pon stuff the autama factory I love what he does I love his philosophy of solo development when I was first doing solo design um I'd done a couple things and then I ran into his blog series on BGG where he explains his kind of autama philosophy and I was like yes this is exactly what I want my games to be like so I think about that all the time when I design and I love to design solo games because of two reasons first is I just recognize that a lot of our Gamers play games for the experience of the game much more than the competitiveness they're playing for narrative Cole uh whle talks about this with root when he had the moment where he was like oh the root Bots are narrative supports for solitaire players they're not they're not primarily competitive opponents although some people play for that reason and I had the same experience when I was working on solo Bots where I had this moment of like oh really just want the satisfying experience of being able to have this game out in front of me so um so when I do a solo bot that's
what I think about when I did red flag over Paris the question was how do I make it feel as much as possible like the two-player game even though it's not going to be the two-player game um that's so that's the first reason the second reason is I truly believe that doing solitaire game development makes the multiplayer game better and I think it does that by stress testing the engine and the core core gameplay loops and helping identify what it is about the game that is core and fun and and essential and what's secondary and so at GMT with GMT 1 we've started pushing some of that solo design earlier in the process with with coin we have we do it at the end because we have a system so Bruce Mansfield designed this card-based system we call the jard system um and it it's to like anything that uses the basic Co coin mechanics um we've when you make a new coin game you're not Reinventing the coin engine so we can do this at the end because we're building on known ground but when you have a game um there's a game that that we're gonna we're gonna announce this month um and it's uh it's from Matias Kramer and the game is super fun and we're going to add solo to it and we want solo development to start now because it's going to help inform and polish the game as we go through development we don't want to wait until development is done and then have solo
come in and see oh actually this is this isn't working the way that we thought it was and solo revealed that um so now we have to go back and restart some part of development right we don't we don't want to do that so and that happens that happened with red dust Rebellion we were we were working on the coin Bots for Red Dust re Rebellion at the end and some balance issues came out through the co through the bot development and we thought we had fixed that problem we hadn't so we had to go through another round of play testing and balance checking to make sure that it was good and get it done and then it just you know it takes time oh man I feel like this might be a whole separate conversation but I know you have a hard stop today so uh just um first off the question what have you been playing recently this bringing you personally a lot of Joy uh the Imperium classics Imperium Legends game I have just absolutely had a blast with that I love how asymmetrical everything is and the solo mode and that's a lot of fun fantastic and if people want to follow your activities online where can you be found so I'm on Twitter uh my Twitter handle is mty Norms which is uh the most ridiculous High School joke that has never gone away uh mty Norms was a homecoming queen at the Ohio State University I grew up in Columbus Ohio um she was also a cow and when I was 12 years old I thought this was the funniest thing in the universe and so it became my handle everywhere and it has never gone away so yep moding Ormsby on your platform of
choice and you have found me fantastic uh Jason thank you so much for coming on this has been an awesome conversation and I hope we have another one when you're a few games deep so we can see how you're feeling about the development yeah absolutely uh thank you so much again and then everybody out there please like subscribe comment ask question questions and most of all happy gaming