This is a spin-off from the post about Jon Blow’s remarks on the IF parser, but it goes in a different direction, so I wanted to take it back to the front page.
I’ve been having a comment exchange with a commenter named Veridical Driver, who suggested a number of possible improvements to the IF interface (automapping, journaling events as they happen, bolded words to show what’s interactive, etc.). I pointed out that there are games that try most of those things; Veridical Driver responded that it’s not enough because IF should be standardized on those features.
So this post started as a response to Veridical Driver’s last comments, especially these bits:
These are things that the IF community may have experimented with, but not things that are any way standardized in the IF interface. The standard IF interface has barely changed from the Infocom days.
Adrift may have mapping, but Inform and z-machine is the standard for IF and do not. Some games might have custom note systems, but this is really something that should be standard, just inventory is standard in all IF. Sure, there is a keyword interface extension… but this kind of functionality should be a standard part of all modern IF.
…The problem is, you are thinking as an IF author, not as a gamer. You don’t like the ideas/features I mentioned, or suggestions other have made, because they constrain your artistic vision. But as a gamer, I don’t care, I just want some fun.
Nnno, I don’t think that’s quite it. Two of the examples I pointed to (Floatpoint, Bronze) are my own games; other projects of mine (especially Alabaster and City of Secrets) include graphical sidebar content that’s nonstandard but is designed to ease player experience and communicate game state better. So it’s not that I dislike these features categorically.
Where I’m pushing back is on the idea that we can or should enforce these features as a standard.
There I’m speaking not just as an artist, though I can think of several of my works for which the features you describe would be a bizarre and awkward prosthesis on the text — what’s automapping for in a one-room conversation game? what’s journaling for, in a game that runs for five minutes and is designed to be replayed?
But setting that aside, I’m also coming to this as someone who’s handled a lot of feedback on one of the most-used tools in the IF community for the last five or six years. People want to do a lot of different things with their interactive fiction, and they should have the opportunity to try their various visions. Some specific use cases, other than the artistic concerns I already mentioned, where your suggestions might be an active hindrance include
- games intended for mobile platforms or small screens, where screen real estate is at a premium
- works for the visually impaired, which need to be simply accessible with a screen reader
- works written with a heavy narrative focus, which may put aside the concept of “rooms” entirely in favor of a different style of presentation; these aren’t always even intended for a gaming audience at all
These aren’t hypothetical; they’re things that people are actually working on and are the basis of real support requests.
So the issue is, tools that force too many features run a big risk of narrowing the creative range to just the projects that work well with those features. Inform has tried to err on the side of making a lot of things optional — through extensions — while not imposing too many constraints through core library decisions. This is always an area of compromise, and there are some features we’ve added that have made Inform games larger, to the chagrin of those optimizing for very small, low-processing-power machines. So these things are always on our minds.
I’m happy to say that a lot of progress has been happening, and continues to happen, on the extensions and interpreters side. The desire to foster collaboration, conversation, and creative thinking about IF interfaces is a major part of the impetus for the IF Demo Fair we’re putting together for PAX East.
Still, this opt-in stuff is obviously more work, and it’s not going to force authors to include the features you’re looking for — and the novice authors are the ones least likely to put in the extra work if the tool doesn’t make them do so. I typically consider it a good sign — not always but often — if I start up a competition game and find that it has cover art, a splash screen, a non-standard status bar, etc. That’s not because I think those are universally important, but because it means the author put some time into generating non-default content. Which means he thought about it. Which is good.
From a game consumer’s point of view, I think what would help the most is curated collections and branding.