Jotting Notes on Red Byer's GC Summit 2009 Talk "Run More Games"
OK, jotting some notes about Red Byer's GC Summit 2009 talk "Run More Games". Yes, the talk was months ago; my notes are not timely. Oh, before I even start, I should link to Red's own notes about the talk--some hindsightish notes and clarifications. Are you back? OK. I'll mostly try to paraphrase here, but I'm injecting some thoughts [in square brackets]
- Talking about the Bay Area Game only. Which doesn't include Shinteki, BATH. Talking about 1992-present.
- Defining what counts as a Game. Site + Theme + Clue + Travel
- Difficult enough: any GC can RSA-128 encrypt a message and give it to a team to slow them down. That's what we're gonna do to the lead teams in Muppet Movie Game, so beware. [hee hee]
- Typical game is ~20 teams. Run only once. It's like a wedding. [don't scale well; e.g., "this site's parking lot can only handle 20 vans". replay value is there--but GC is probably too exhausted to do it.]
- Community. You have to give back. Give back your time. Playtesting, GCing.
- The formula. The basic idea: For the game community to survive, folks need to contribute, not just take. It's not enough to contribute just as much as you take. Because lots of teams drop out after just a few games, you need to contribute more than you take or else the community's going to asymptotically go to zero.
- The formula, ctd. You need to give back one Game every Five Years. You might think, 20 teams play in a game, my team plays 2 games a year, so we'll just run a game in 10 years. But because of attrition, because teams stop playing, you'd better run a game every five years.
- running games is big effort, expense, stressful
- Folks worry about inadequacy. Don't do that. you're not gonna do the _______ aspect as well as ________ GC. That's OK. Doesn't have to be the same as everybody else's. My game is going to have my style, my flavor.
- Running a game: warm fuzzies; giving back to community; try new things, e.g., industrial design; influence community direction; Higher Probability of Future Play
- History. Captains list, so you knew teams were good--and not too many of them.
- Feedback loops: a team will "try out" a player. Players they get along with get invited back.
- Feedback loops: teams want to play, but also trust GC to run good Game. GC needs an audience that can handle 30 hours of Morse code and driving. There's mutual trust.
- In the past, there was an understanding that teams who were more likely to run games would be invited to more games ??!? [Not sure how this worked. If a team played too much w/out running a game, were they removed from the Captains List?] Number of teams was pretty stable through the 90s. [Oh, maybe teams not-running games has always been a potential problem--but the explosion of # of teams in the aughts exacerbated said problem?]
- Nowadays, there are still teams and games--but game community is larger. There's been crossover with other communities. No more Captains List.
- Application process--takes team effort. Doesn't necessarily reward what you want. E.g., first-come first-served just rewards folks who wake up early. [Ideally, application includes a resume of games run, and you'd consider that. (But that requires GC folks to be judgmental, and not everyone is comfy with that.)]
- Crossover has been good and bad thing. (Here crossover is with things like MSPH, Seattle Game, Shinteki, BATH.) We're more popular now! But we haven't seen a contribution from these folks back to the Game community. [So they should have run Moonraker's in San Jose instead of Seattle? WTF? (...and SBlom touches on this later)]
- So there's a lot of teams that want to play, but the number of Games hasn't scaled to meet demand. Most games run by repeat GC. Not enough new GCs
- Linda Holman points out: You don't have to run a BANG before you run a weekend game. Red says: Yeah, firmly believe in rookie GCs; ratrace was messy... but it still worked out. XX-Rated's Paparazzi game was awesome. Goonies was awesome.
- Possible solutions:
- close the Game Community 20 teams [reinstate something like the captains list].
- we can "redefine and branch the community" [???] try to stop the crossover
- reinvigorate the feedback loops. Even if you don't like a team, if they've run a game, let them play: they've given back to the community.
- Don't expect to play in every Game.
- Run More Games
- Melinda Owens: Gee, if people ran more BANGs instead of more Games, that might help more: BANGs can handle more teams.
Red: That wouldn't help reduce the demand for Games, though.
[if your goal is max# of happy players, run a BANG. But if your goal is to get invited to more Games, run a Game]
- Jennifer Novakoski: Ghost Patrol was team LowKey's first game. It was a full-length game. In hindsight, a few LowKeyers would rather have run a small game first. It's really hard to devote a year of your life to something that you're not even sure it's going to be successful. Just to learn the logistics.
- Sean Gugler: not a rebuttal, just a contribution to the discussion. I have run full games, I have run half-games. The half-games were not significantly easier to run.
- Red: Yeah, we spent as much time on overnightmare, a half-game, as on ???
- Sean Gugler: then again, as I get older and need more sleep, I find the half-games more appealing. [This old fart says, yes, by jiminy.]
- Brent Holman: As a prospective GC, you should push yourself a little bit. Try doing something that is more than you thought you could do. Try a half-Game instead of a few-hours BANG. Some things... taking the overnight aspect out helps the logistics a lot.
- Scott Blomquist: I'm in one of those not-in-scope groups [Scott is from Seattle game community, though he lives in Portland as of 2009. It's complicated.] How are we "invaders from the north" perceived by the Bay Area community? You know, it's really hard to run a remote Game. Alaska Air is cheap. If we run a Game in Seattle and you're invited, does that kinda count as "repaying the community"? Or do we need to put a cell membrane around each city and figure out what the equilibrium equation looks like?
- Someone: I'd love to go to Seattle
- Greg deBeer: I've never played a Seattle Game, but I think it would be really fun, so do it. But there's also a trend we're seeing more of: simultaneous running a game in multiple cities. No, nobody's tried to "simulcast" a long Game game, just BANG/SNAP/MSPH-like things.
- Linda Holman: Another barrier to entry [and thus a way to control demand] is money. If you run a game in NYC or Chicago, that will limit your demand down to 20 teams--the 20 teams enthused enough to fly to NYC for a game. But right now, with demand the way it is--you would get 20 teams who are willing to fly to NYC.
- Red: But do we really want do limit demand for each game? Or do we want to run more games? Most teams don't want to play in 6 games per year.
- Corey Anderson: If I'm GC figuring who has game-running karma, that's hard if I'm a brand-new team. I might not know. And also--what have you done for me lately? [Is Red disappointed w/Desert Taxi and LowKey because Orange Snood didn't get in to Ghost Patrol? Orange Snood hasn't run a game since those teams have been around. Then again, the Orange-ites and the Snoodites ran more than there share of Games... but years ago. Maybe it was Red's contemplation of all this that led him to wonder how often a team should GC?] So do you tell a new team: well, you have to let this "old guard" in? I don't know what the solution is here.
- Red: Yeah, been on both sides of that. Been rejected by GCs. As a GC, have rejected teams because I didn't think they'd be a match for our game. "It happens." But we try to favor teams that have bled for the game. As a community, to survive, you have to reward folks who contribute to the community. Otherwise, folks who have run games will disappear. We've seen GCs, where it just obliterated their team. The BioHazard game, the Espionage game, there have been several examples. Anyhow. I'm not saying I have all the answers, I'm just saying this might be a key to get more GCs to step up.
- Crowd chatter: Hey, if we obliterate more teams, that will reduce the demand :-)
- Jesse Morris: so we're new GCs. Of the teams that applied [to Ghost Patrol], about 15 were past GCs. We don't know what they did, but we know they did something.
- David Mendenhall: We were trying to bring in new blood, folks who will maybe contribute more in the future.
- Red: Yeah. And honestly, the folks on the "old guard" are pretty adept at landing on teams. In Ghost Patrol, I landed on my sister's rookie team and had a great time.
- David Mendenhall: We were trying to bring in new blood, folks who will maybe contribute more in the future.
- Chris Dunphy: If a team is cohesive, a team can go on to run a game. But what if it's a ragtag mob that gets together to play a Game--but not a great group of folks to run a Game? Like, say, RadiKS. I'd like to get advice on how to build a Game-Control centered team to run a game.
- Red: You know how when you're playing and your team says "Hey we could run something sort of like this but--" that's the spark. [Uhm, and if your team doesn't ever say that?]
- Teresa Torres: Orange Crush played in 5-7 games with no team dynamic problems. Friends from college, got along really well. Running a game destroyed our team. The reason why: half of our team had no idea what they were getting into. I mean, they knew: we had a plan of building clues and finding sites; and it didn't happen. 2-3 of us bore the brunt of the entire game. Fortunately, at the end we were all still friends--but we will never play in a Game again. Yeah, your Game team is not necessarily your Game Control team. But you might have two teams together like Desert Taxi and and LowKey [and the Snout/Drunken Spider combo springs to mind]
- Red: Yeah. There's a few Orange Snood folks who are running the Muppet Movie Game. But not all of Orange Snood is running the Muppet Movie Game. I know Snout likes a big "core" GC, but I like a small core. Less effort on updates, reminders, the effort to keep so many people working towards the same vision.
- Scott Blomquist: quick remark, for some reason in Seattle, 12-person "cores" work really well. Insert your favorite Microsoft joke here :-)
- Corey Anderson: Huh, so in the Bay Area, part of the reason a lot of "teams" have a tough time GC'ing is that it's basically one serious person and their four "friends of the week". So is the MSPH tradition different?
- Scott Blomquist: Yeah. Actually, some Seattle non-MSPH have chosen team sizes relatively prime to the MSPH team size, just to force folks to mix a little. I'm affiliated with a 12-person entity, a 6-person entity whose population is made up entirely differently, and when I was a Microsoftie I was on a 4-person MS Puzzle Safari team. Seattle has its own Venn diagram of puzzle communities.
- Rich Bragg: so why just The Game? I think the community today is the big thing [Bay Area Game + BANG + Seattle + etc] I almost feel--
- Red: Is it, though? They serve very different expectations. Some people may go between them but I personally only play in Games.
- Rich Bragg: I think a lot of people would consider a Shinteki a Game. [Yes] So you almost have to make a choice of where to contribute: if I contribute to that circle, am I excluded from that circle?
- I have no answer for you.
- Me: The MSPH is coming up. It's not the kind of event I like to play in--too many puzzles, not enough other stuff. So since I don't want to play in it, I volunteered to help run it. Maybe there's enough overlap of interest so that people will remember that I helped do that.
So... how to choose teams? I'm DIY-minded enough to think: Yes, you should consider whether a team has run events lately. If a team's members play a lot but never run events, pass them over for newcomers.
But... you know how Red mentioned "crossover" from other communities into The Game community? I'm one of those "crossover" people. So, as you might guess, I hope when you're tally up events a team has run--I don't think you just count The Game events. I'm biased that way by preference... but of course you should also take what I say with a grain of salt--I'm probably biased that way out of self-interest, too.
And yet... and yet...
Even if The Game were the only thing I cared about, I'd still check for BANGs on a team's resume. Desert Taxi, XX-Rated, coed astronomy: they ran Games; I think they ran BANGs first? (Probably other teams did, too; those were just the first that sprang to mind.) Some folks are happy to just consume. Some folks create. You probably want the creative folks to be "in your neighborhood" even if they're not making exactly what you want.
So what should count? If you're a Bay Area puzzle freak, how much do you care about Mooncurser's? Does Shinteki count, if they're both a Game-like thing and a business that lets in just anybody? What about someone helped run the Microsoft Intern game? What about the guy who lives in Emeryville who runs treasure hunts for his kids for birthday parties? Me, I would count Mooncurser's and Shinteki. I'd probably not count the intern game, not Emeryville... I'm not sure why I wouldn't count those. Maybe because I wasn't invited to those events. But... maybe they'd count for something--because someone who ran such a thing might be tricked into other events later. Oh man, Thomas Snyder wrote a book of sudoku puzzles. How should that count? I mean, I was "invited" to it. I could go buy the book. On the other hand, it's not exactly a hunt. On the other hand, he's obviously of the mindset to make stuff. On the other hand...
There's going to be judgement calls. It's not going to be 100% fair. Not everyone on your GC committee will agree on what the criteria are. It would be easier and more straightforward to make your game first-come-first-served.
But you know? Red is right. Oh, I quibble on details; I would count "karma" from related-but-not-quite-what-I-had-in-mind events. But that's a quibble. It's a good idea to show appreciation for folks who run games, especially if you want to trick more folks into doing it. Slots in Games are darned precious; they're a great way to show appreciation.
When you ask teams to include a resume with their application, you remind them that running a game is important, that you care about it.
Oh yeah, and: Run More Games.