RogueForge

Talks

Glenn Wichman talks to Slashie, 2016

Interview
July 2016
Interview with Glenn Wichman
Santiago Zapata (Slashie), Colombia · video, 14:07

Glenn Wichman talks to Santiago Zapata (Slashie), of Temple of the Roguelike, on a trip to the coffee region of Colombia in July 2016: where roguelikes are going, why technology does not make a game better (Rogue's own challenges were fitting in 60K of memory and building a world from ASCII characters), roguelites, app stores and distribution, game design as a discipline, and a plea for simple games. It is the second of their interviews; the first, in May 2007, was written (Glenn Wichman talks to Slashie, 2007).

See also the 2016 panel with Michael Toy and Ken Arnold and the 2021 interview with Glenn Wichman.

About this transcript. Made from YouTube's automatic captions, checked against Santiago Zapata's own transcript on Temple of the Roguelike, and lightly edited for readability: punctuation added, false starts, repetitions and filler words removed, and mishearings corrected (Wichman, roguelike, virtual reality, ASCII). The wording is otherwise as spoken. Zapata asks the questions and Wichman answers; each answer starts a new paragraph. Section titles are YouTube's; each timestamp links to that point in the video.

Introduction

0:00 Hello Internet, I am Santiago Zapata and I am here in the coffee area of Colombia with Mr. Glenn Wichman, one of the original creators of Rogue. So we are going to do a short talk about some game design topics and some Rogue-related topics and roguelikes. Okay, so thank you for accepting this small interview, Mr. Glenn.

0:24 So where do you think the roguelike genre is heading to? What's going to be in the future for roguelikes?

Future of roguelikes

0:31 Hard to say. I think it's going to be the same things that are in the future for all different games. I think virtual reality is one of the next big waves on the horizon, and so I'm sure there will be a virtual reality roguelike, and I think that will be really interesting. There probably already is one out there, I just don't know about it yet: a procedurally generated environment that you can actually walk inside. But yeah, who knows what the next innovation is going to be.

1:20 What do you think are the challenges for game design with all these new technologies, especially virtual reality and everything that's coming?

Technology vs. game quality

1:28 It's a good question, and it'd probably be better answered by someone who's got a degree in game design, but I'll give it my best shot. I think technology is not going to make your game any better. I think that's the main thing you have to have in your mind: the technology is a channel, it's a means to an end, and maybe it will open up some new doors for you to make some games possible that weren't possible before.

2:09 But if you look at what made Rogue good, none of it was the technology. Certainly not from today's point of view, but it was cutting-edge technology at the time that we were creating the game. The challenges that we faced were how to make a game run in 60K of memory, how to make a game engaging, and how to build a fantasy world when all you had were ASCII characters to use. So those were our technical challenges, but that wasn't what made Rogue fun or not fun. So you need to look at the technology that you have and figure out how you're going to make use of it, but the fun and the engagement are not based on the technology.

3:07 What do you think about roguelites, or games that have some design elements from Rogue but are not really roguelikes? Have you seen them?

Evolution of game design

3:15 I've seen a few, yeah. I think the more different ways that people use elements from different games and mix them together, the more diversity we get, and I think that's always good. Rogue introduced a few really interesting innovations for its time, and everybody ought to introduce their own innovations when they make their own game. And so of course it's going to evolve and it's going to change, and that's what makes the new games interesting.

4:07 What do you think about the current distribution channels, like the App Store or Google Play, and Steam for PC, versus other ways of distributing, like the traditional one or some online methods? What do you think are the pros and the cons?

Challenges in distribution

4:22 I think the App Store sucks. I understand why Apple did it the way they did, and it makes sense, but with all of the unintended side effects, it's a terrible distribution channel, especially for a small independent game. Unless you just happen to have lightning strike, you're not going to get any visibility for your game.

4:56 Back when the internet was first beginning to catch on outside of computer science realms, I was advocating from the very beginning that it makes no sense to be distributing software in those days on floppy disks or on CD-ROMs, when you could just have the game live on the internet, and you just go to a site with a URL and you always get the latest version of the game. And I loved when web-based games started to come out, and web-based applications, where you always have the latest version, everybody always sees the same version, and you don't have to worry about distribution. And I feel like with a lot of these new ways of distributing we've lost that.

5:53 Steam seems to be better, although I'm not really familiar with it; I haven't used it a lot. It seems to be a more effective way for an independent developer to put something where it's going to get noticed, especially by the gamer community. But I would like to see internet-based distribution of games, where you just go to a website and play the game there. I still think that's a good way to go.

6:35 It's just a difficult problem in general, since the gaming community is a thousand times the size that it was when I started out. There's a huge population to reach, but there are so many games being created, and that's a wonderful thing: the more the better. But it's a hard problem to solve, for a person who's got an idea for a game or a small company that's got an idea for a game, how you're going to get it in front of all of the people who might want to play it. And for a gamer there are just so many choices now. Again, when I was starting out there were literally maybe 15 games to play, at all. And then there were hundreds and thousands, and now there's millions. So how do you choose which one to play? You've just got so many choices.

7:38 Let's talk a bit about game design. How has the role of the game designer changed throughout the years?

Role of the game designer

7:53 So when I went to college in 1979 I wanted to major in game design, and to me that didn't mean computer game design, because I didn't really even understand about computers until I got to college. But of course there was no such thing as a game design major. So when we designed Rogue, we were just figuring out how to have fun. We didn't have a language to use like we do now. We didn't talk about game mechanics or friction points or core loops or any of those things.

8:39 As my career went on, there weren't game design positions you could apply for or anything like that yet, or very few. It wasn't a discipline. And over the 30 years since I started doing this, it has become a discipline, and now there's a lot of really good schools that have dedicated programs that are specifically about game design, and that's such an exciting thing to see. But I missed out on it. So I might have ended up with a career as a game designer; instead I have a career, a really nice career, as a game engineer, and when I am fortunate my work allows me to have some design input, but I'm paid for my engineering skills, not for my game design skills.

9:42 Okay. Do you think the game designer should code? How far should he get into the code, or should he stop at a game design document or something like that?

Importance of multidiscipline

9:50 People should do what they love. I love game design and I love programming, so when I can do both I will do both. But I think if you love game design and you don't like programming, then you're lucky, because you live in a world where you can make a career designing games without having to program. And if you love writing code — if you're going to be a game coder you should at least have an appreciation for game design, and if you're going to be a game designer you should have an appreciation for engineering. I think even if you never intend to write a line of code, you should at least learn what coding is, how it works.

10:32 And it's not just those two disciplines. There's user interaction design, and there's graphic design, and there's sound design, and production and quality assurance, and you should have at least a feel and appreciation for all of those disciplines, and how a good game is not possible without all of them working together. But you should do what you love.

11:02 Let's finish up the same way that we did on the first interview. Do you have any message for the roguelike community, the independent developers out there doing their games on their own or in small teams?

Advice for indie developers

11:18 Yes. I am so glad that this is still a thing, because again, I have worked on games where there have been a hundred people working on the game, and it's great, it's like making a movie; it's really neat to see so many people coming together to create something. But I think that we always need to have room for the individual visionary who has an idea and they want to see it come to life, and for people like me who like game design and graphic design and engineering to have a space where you can bring all of your loves together in one place.

12:08 So I've been excited to see just how vibrant — and I don't keep up with things as well as I should. There are, again, millions of games out there; it's overwhelming to try to have an understanding of everything that's going on, and I'm really busy creating new ones, so I don't have time to look at everybody. But I'm excited that there continues to be space in this industry for small teams and individuals to create games.

12:51 And again, a game does not have to be technologically on the edge in order for it to be fun. Simple games can be fun. I love simple games. So if you want to make stuff for me, make them simple. This is just a personal taste, but for me a lot of roguelikes got way too complicated. I like to have a game that you can wrap your head around in just a few minutes, and that's not difficult because it's complicated but it's difficult because it's challenging. That's where I would like to make sure people are focusing. Don't just throw in lots and lots of stuff and overload your game with too many features. Make sure that you've got a game that, while it's still simple, is fun.

13:50 All right, thank you, Mr. Glenn, and I hope we can meet again, maybe in 10 years, for the third iteration of this interview. And thank you again.

13:58 All right, thank you.