You know, for a game development blog I don’t post about game design nearly often enough. This week is an exception. Let’s start with Gamasutra’s case study of good first levels — an important part of any game, if by no means the hardest. (Ultimately, the first level is also the easiest to make.) More specifically, we have an article about prefabricated sections in procedurally generated levels and another on powerful uses of color in game graphics. Plenty of things to learn from both!
Going on, Polygon is running a long-form feature about the making of Final Fantasy VII (warning: really long read!) And you know, it would be a much more interesting story if it didn’t sound exactly like most other such stories. Politics, money, technology, ambition, cockiness… stop me when you grow tired of the drinking game. Is the industry ever going to learn any better?
Last but not least, fans of interactive fiction will be happy to hear that textadventures.co.uk is saved! A new team stepped up to take over, and the transition is ongoing as of this writing. Can’t wait to see what happens next.
Speaking of which, stay creative, and stay tuned. See you!
It’s not easy to keep up with new developments in IT, especially when you work long hours, or for that matter when you no longer learn quite as easily as you used to when you were twenty. So far I was lucky to pick my technologies well: expertise in Python, HTML5 and even Java (for now) has only grown more marketable in recent years. It still felt like falling into a rut as of late, and moreover I kept stumbling across projects written in the Go programming language. After some hesitation, I decided to take the plunge, and it turns out I can still learn a new programming language in a couple of days. Go me!
And what a language it is.
Go is mostly targeted at server-side software, which makes it less relevant for games unless you’re doing multiplayer. Then again, it’s just as good for command-line apps (think tools), and there’s a healthy choice of libraries for text-based user interfaces that don’t require separate DLLs.
But what’s it like, exactly?
- It compiles to native code like C++;
- has garbage collection like Java;
- the package system resembles Python modules;
- the object system resembles the one in Haskell;
- control structure syntax is like in Perl 6.
I’d say Go is an odd duck of a language, except it’s more of a platypus. Good to see programming language designers having some guts, after decades of slavishly imitating C.
Hello, everyone! We’re having a slow week again, and most of it dedicated to interactive fiction as usual (sorry). For one thing, PC Gamer puts the recent IFComp in the spotlight, thus further cementing the genre’s return to the mainstream. And via K.D. we learn that Douglas Adams was working on a modern Hitchhiker’s Guide game right before his untimely death in 2001. It’s a bit of non-news, really, as the assets being lost means there’s no chance of reviving the project after all these years. Doubly so as those assets were likely made for VGA displays back in the day, which would make them unusable in the 4K era.
And that, of course, highlights yet again the folly of obsoleting perfectly good technology at the drop of a hat. Imagine if vinyl had been completely abandoned within the year from CDs hitting the market. No more support for turntables, nothing. Entire collections of old, rare music becoming completely useless unless people worked hard to maintain failing hardware until there were just no more dead units left to scavenge for parts. That’s what we’re doing with computer games, and before you ask why we should bother preserving some piece of shovelware, the answer is that you can only know a classic in retrospect. If you didn’t take care of it on time, sixteen years down the road — when you finally realize it wasn’t just another piece of shovelware after all — you can only weep for the loss. And that’s terrible.
Last but not least, my friend Kris is at it again with a batch of capsule reviews for tabletop RPGs and board games. Enjoy, and see you next time.
Happy New Year 2017! Things picked up noticeably the week after Christmas, so we can begin anew with aplomb. For one, a very good friend bought me a Pico-8 license, and of course I couldn’t resist playing with it. It’s an incredibly polished experience for such a restricted platform, one that immediately inspired me to start remaking one of my early games. I’m not sure quite what makes it feel so good, but it’s one of those systems that feel designed, not just thrown together, and that’s rare today.
Given that, it’s especially appropriate that Rock, Paper, Shotgun just published a series of articles about working with the Pico-8. I do have one quibble: ideas, my friend, are a dime a dozen. If you have to go around hunting for ideas, maybe you don’t have anything to say right now. Go out and live some more.
On a similar note, Kotaku is running the story of a game journalist turned developer. And it sounds not so much like someone who learned just how hard it is to actually make those games they used to criticize, as someone who grew up and learned to assume good faith. A win, either way. Can’t even blame them: I used to have my troll-ish moments as a delayed teenager. Haven’t we all? So it’s all good.
To end with a couple of actual releases, here’s Roguelike One, a quick, simple game that could be played with a NES controller (in the sense that it only uses arrow keys and two action buttons). No prize for guessing what it’s a fan game of. 😛 And in the retro department, Prime Mover is a Construct 2 title carefully made to resemble a ZX Spectrum game, down to the way controls are responding. Which, of course, is a lot more work than making it for the Speccy like my own two attempts. Nice!
On that note, I wish you the best until next time. Thanks for reading.
It’s 2016, and for the first time (in over two decades) a game with no parser won the Interactive Fiction Competition. Not only that, but in spring a game made in Twine swept the XYZZY Awards for 2015. And two-thirds of the Spring Thing entrants, including one of two winners, were choice-based.
Why does it matter? Because no earlier than 2014 there was a huge dispute over parser-less games raising to prominence in the IFComp. And doubts about the future of the parser stretch all the way back to 2010 — not coincidentally, the year Twine started getting notice.
How ironic that just a few months before that it was hard to find an interactive fiction piece made with anything except Inform 7.
No wonder that fans of the parser can get defensive. Not that parser-based games are going anywhere, but, you know. Down from the top of their game, and all that. (Pun not intended.) Worse, there’s a simmering dread that the parser failed to keep up with the times and appeal to new players even as interactive fiction slowly became mainstream again. And not for lack of trying.
Maybe I write too much about text-based games, but in my defense the written word is awesome. It’s the closest you get to a digital medium without actual computers (what, with letters and words being discrete symbols by definition), and one of the most flexible as well. Communication doesn’t get more pure than a stream of symbols flowing back and forth; you can write them down on paper, ticker tape, or walls, going left or right, up or down, and even lay them out in three dimensions, as the Ancient Egyptians amply demonstrated. You do have to pick one path when reading, but hey, that’s what we call hypertext nowadays.
Early computer games, from Hamurabi (Doug Dyment, 1968) to Adventure (Will Crowther, 1976) were limited to a linear stream of text, simply because they had to run on teletypes. For the same reason, input was also limited to typing words on a keyboard. But that limitation also meant you exchanged words with the computer from equal footing — what people in the real world call a chat.
And so, a command line remained the defining way to interact with text adventures, helpers like a clickable compass rose notwithstanding. Oh, there were always a few games that tried to emulate the pick-a-choice interface popularized by gamebooks in the 1980s. But those were hardly on anyone’s radar until 2009, when Twine swooped in. At which point it became impossible to ignore all the people shouting that the emperor is naked.
Hello, everyone, and welcome to my last newsletter for 2016; after this one, I’m taking a holiday break. It occurs to me that I’ve been posting this thing for three years now — half the time that No Time To Play has been around — and I’m yet to miss an update, though many have been late or else not very interesting.
Speaking of which, after failing to sell for a year, even after a fire sale, this autumn I made Tales of Space and Magic free. And it still failed to attract any views, let alone money. So for the past few days I’ve been trying something new, namely to turn the original PDF into a Twine. Which works quite well, if far from perfect, courtesy of all the implicit cross-references (now made explicit). Let’s see if this new edition will fare any better.
In the way of community updates, Vintage Is the New Old has a new face, that makes it look a lot more readable and modern, if a bit same-y. Not as good is the news that textadventures.co.uk will close down unless a new owner can be found before March 1st. We’re talking an order of magnitude more people than there are on IFDB, many of them students using interactive fiction as a learning tool. To ask what famous games have been made with Quest misses the point. This will be a loss no matter how you look at it, and I know from experience that once broken apart, a community can’t simply reform elsewhere: it’s gone for good.
Moving on to game design, Mark Johnson of Ultima Ratio Regum fame posted an article on the private lives of NPCs, while Jimmy Maher concludes his series on Wings (the classic flight simulator) with an excellent lesson for game designers:
Those other flight simulators define realism as getting all the knobs and switches right, making sure all the engines and airfoils and weaponry are in place and accounted for. (…) Wings was a reaction against that aesthetic. Instead of building a game out of exhaustive technical detail, with no thought whatsoever given to the fragile human being ensconced there in the cockpit in the midst of it all, John Cutter asked what it was like to really be there as a pilot on the Western Front during World War I — asked what, speaking more generally, it really means to be a soldier at war. Michael Bate, a game designer for Accolade during the 1980s, called this approach “aesthetic simulation” — i.e., historical realism achieved not through technical minutiae but through texture and verisimilitude.
In other words: dear developers, games are for people. Get a life first.
Happy new year and see you in 2017.
Hello, everyone. Today, for only the second or third time in three years, this newsletter contains no actual links. Apologies. In my defense, I did keep working on Adventure Prompt, after coming up with a game idea that can properly showcase the engine’s specific features. A big selling point of the system is the ability for authors to employ many text adventure tropes just by setting some properties on objects. And it’s surprising how much can be done that way. Scenery/portal objects (they can double as doors that lead elsewhere) were trivial — just another application of exits. Vehicles took only 100 lines of extra code in the interpreter (though that was a 20-25% increase), and the only recent addition to the editor, apart from more documentation. I could have crammed a minimal scripting language in that much space… but that would have shifted the burden on authors. Which is the opposite of what an authoring system is for.
Easy stuff will be easy no matter what. The trick is making the hard stuff easier as well.
Next: to do some more refactoring before adding what little is left (reading material and hidden object reveal, mainly), and then to see about fleshing out that demo game, because while the map and puzzle structure came easily, I had a hard time thinking of descriptions. And that’s supposed to be my specialty.
See you next time, hopefully with more exciting news. Be well!