Sponsored By

Road To The IGF: Star Guard's Loren Schmidt

In the latest Road to the IGF interview with 2010 IGF finalists, Gamasutra speaks with Star Guard's Loren Schmidt, who explains why "retro" isn't always the best term for a "low-fi" game.

Kris Graft, Contributor

February 9, 2010

10 Min Read

[In the latest Road to the IGF interview with 2010 IGF finalists, Gamasutra speaks with Star Guard's Loren Schmidt, who explains why "retro" isn't always the best term for a "low-fi" game.] Loren Schmidt's Independent Games Festival finalist Star Guard resembles an Atari 2600 game, but don't call it "retro." The side-scrolling platform shooter is up for the Excellence In Design award for IGF 2010. It might appeal to a gamer's innate sense of nostalgia with its pixelated graphics, but from a design and artistic standpoint, creator Schmidt is living in the present. Here, Schmidt explains why the term "retro game" makes him "uncomfortable," the inspirations for Star Guard, and expressing narrative within the confines of "low-fi." What kind of background do you have making games? My family didn't have a computer when I was younger, so I spent a lot of time playing with Lego, building castles out of blocks, and making up board games. I was always entranced with things that had moving parts or were interactive in some way. I remember that when I was six or so, there was one block castle which I made over and over. It opened up and had a hidden slime pit inside. See, you'd put a little plastic knight right on the seam, and then you'd open it up and he'd fall into the slime pit below. The slime was made of green wooden blocks. The first chance I had to make actual computer games was much later, in high school. And even then I didn't know how to program well. I was only allowed to take one elective, so I chose art instead of programming. I'm still playing catch-up in the code department. What development tools did you use? I used FlashDevelop to make Star Guard. I quite like it. If anyone out there is using Windows and is interested in Flash game development, I'd definitely recommend giving it a go. There's also one tool which I really should have used, but didn't: an in-game level editor. Switching back and forth between an external editor and the game is unnecessarily awkward. In hindsight it would have been a really good idea to have taken a little time to make a simple real time editor for the game. I think it would have saved a lot of time and made level design a much more fluid process. How long have you been working on the game? About 16 months, though during that period I was only able to develop games part time due to school and other obligations. How did you come up with the concept for the game? What were its influences? I was making a large puzzle adventure game at the time. I didn't know how to organize myself, and though I still believed in the game, it wasn't going well. I had an urge to run away and make an extremely simple action game. I originally told myself it was just going to be a side project, but I had so much more fun developing Star Guard that it ended up becoming my main project. As influences, I'd list Another World, The Pit, Flywrench, Lode Runner, and Shotgun Ninja. I'm not advocating abandoning projects- actually I think abandoning the other project was really unproductive and painful. I felt really guilty, and for the longest time I wouldn't admit to myself that I'd stopped development of the original game. In hindsight, I think the problem was that I charged into making a large game too quickly. I was enthusiastic, but I didn't know how to develop a large project in a way that would stay fun and productive. (I'm still trying to improve my skills in that area.) I should have made one or two tiny games before beginning anything so large. Why did you choose to go with such a retro-inspired style? Personally, and this may sound strange coming from me, I feel rather uncomfortable with the word "retro." I'll try to explain where I'm coming from. I feel that both high and low fidelity art can be effective, each in its own way. It's totally possible to make a stylish, self-consistent game in either category. Generally, I think working with higher fidelity assets allows a lot more freedom, and ultimately I think that's where most of our effort should go. But low fidelity art also has certain things to offer. Firstly, I think that pixel art (and other restricted art styles) are a great fit for solo or small team game development. By working within constraints, it's possible to make a visually polished game without needing an army of specialists. Another thing that I like about pixel art is its cleanliness. It naturally encourages an even detail level, and it lends itself well to an uncluttered, readable style. Low-fidelity art is also appealingly open to interpretation. If a character is only eight pixels tall, a large part of what we see is within our own imagination. Is he wearing a hat, or does he have a big nose? Are those tentacles or jointed legs? I played with that a lot in Star Guard. A lot of the art is deliberately ambiguous. Why do you think the game was so successful in its design? IGF judges aren't the only ones to recognize the game for its tight design. I haven't developed very many games, so if anyone else has a different way of going about things, by all means listen to them. I don't think there's a single right way to go about designing things. So far I find it helps me to begin with a clear idea of the feel and activities I'd like to aim for. I try to start with a clean slate and develop the particulars with those goals in mind. I think you end up with games that are more internally consistent when all the ingredients have been hand crafted to work well together, rather than borrowed wholesale from existing games and jury rigged to work together. You run into trouble when you assume a borrowed mechanic has the same role in an entirely new context. Recharging health is a decent example of what I mean. Right now, a large number of action games have Halo-style recharging health. This kind of health system is a fairly good fit for cover based, stop and go firefights. It reinforces the feeling that cover is safe and taking the offensive is risky. Is someone shooting? Find cover. Is my health low? Find cover. There's also a fun risk/reward mechanic built in- it's possible to stay out in the open and keep dealing damage, but only if you can successfully dodge enemy fire for long enough to allow the shields to recharge. But while this mechanic works well in Halo, many of the other games that use it don't do so with as much attention to detail- they simply borrow the Halo system wholesale instead of creating a health system which is tailored to the game at hand. Do you think the "retro" graphics could turn off potential players, or does that even concern you? Definitely. It's hard to see a game that fits a preconceived category like that and not read a lot into it. For instance, I think I harbor certain prejudices against Flash games: I'm probably inclined to assume they're rushed, have low quality standards, and contain tedious drawn out tutorials. It's really not fair at all, and I consciously try to be as objective as I can, but that's the prejudice I carry with me. I think one of the burdens of choosing a low fidelity look is that some people assume the game is small, rushed, or all about evoking a particular era of history. Some people tend to dismiss the visual side of a game entirely if it's low fidelity. I hear statements like "it must be really refreshing to be able to spend so little time on visuals" or "this designer obviously chose to focus on design instead of art." The truth of the matter is that a lot of people who do low fidelity games are very visually focused. I spent a huge portion of the development time tweaking animation, adding special effects, and obsessively redrawing things, but it's not necessarily visible to people who aren't used to looking at crunchy low fidelity games from that perspective. The narrative pulls you in too. Do you think people are surprised when such a minimalist game can create a compelling narrative? What's the key? Personally, I think there are a lot of different effective ways of telling stories in games. Some games work perfectly with pages and pages of dialog, and others feel complete to me without any story at all. Both are right. In this game, I want to use a pretty unobtrusive method of delivery. I want the story to reinforce the atmosphere of the game without impeding the act of playing it. Replay is a big part of what I'm going for here, and I also don't want to force the story on anyone who doesn't feel like reading it. That's why the story is delivered through short messages on the walls. They're self-paced. It's possible to just run by them without pausing. It's also possible to stop and take them in at a slower pace if we prefer. Another choice I'm making here is to tell the story in a fragmented way and leave a lot up to the imagination, rather than explicitly spell out all the details. Were there any elements that you experimented with that just flat out didn't work with your vision? Yes; for instance, I implemented (but did not use) a type of alien with a reflecting shield. I really like them, but they don't fit with the pace of the game well. They encourage a slower, more defensive style of play. Also the structure of the game wasn't at all set in stone. The core ideas stayed- the feel, the general way combat works, the pace- but there were some other pretty large things about the game that gradually shifted over time. It wasn't a pure process of designing everything in detail, then executing it. Have you played any of the other IGF finalists' games? Any games you particularly enjoyed? I haven't had a chance to play most of the entries. I'm really looking forward to seeing them on the show floor. The idea behind Miegakure is really appealing to me. (Meigakure involves the three dimensional projections of objects with more than three spatial dimensions.) I'm interested in seeing how well this implementation works. Can many people really model that sort of thing mentally, or do most people end up playing via guesswork? It's a neat idea, and I'm looking forward to seeing it in action. What do you think of the current state of the indie scene? It excites me that it's becoming easier and easier to make things. Tools like Game Maker, Construct, and MMF2 [Multimedia Fusion 2] are great, and I think that's only the tip of the iceberg. We still tend to make digital art like games in a very technical way, which is fine I think... but I think there's potential for other more expressive styles of creation too, things more analogous to performing a piece of music or drawing a picture. It's exciting to see new possibilities opening up. I also want to say that I love how open and supportive the community is. It's really wonderful to see people teaching each other things, sharing techniques, and discussing ideas with each other. That's a constant source of inspiration for me. [Previous 'Road To The IGF' interview subjects have included Enviro-Bear 2000 developer Justin Smith, Rocketbirds: Revolution's co-creators Sian Yue Tan and Teck Lee Tan, Vessel co-creator John Krajewski, Trauma creator Krystian Majewski, Super Meat Boy co-creators Edmund McMillen and Tommy Refenes, Sidhe's Mario Wynands, who worked on Shatter, Daniel Benmergui, creator of Today I Die, and Klei Entertainment's Jamie Cheng, executive producer on Shank]

About the Author(s)

Kris Graft


Kris Graft is publisher at Game Developer.

Daily news, dev blogs, and stories from Game Developer straight to your inbox

You May Also Like