🎮 I made a Twine game. Or: It is illegal to serve Hot Sauce to a Dragon in Granada.

It is illegal to serve Hot Sauce to a Dragon in Granada | mirrored on Philome.la | hosted on my site

This is my first time using Twine, and the first interactive fiction (IF) game I’ve ever made. So I welcome any and all feedback and opinions on Project Dragonsauce! (Because that title is a mouthful.)


It all began with this writing challenge on Chuck Wendig’s blog, where everyone commented with a title for another commenter to “adopt” for a flash-fiction piece. Someone had posted this exact title, “It is illegal to serve hot sauce to a dragon in Grenada [sic]”, and my imagination instantly latched onto it. I originally wanted to write flash-fiction/short story as per Wendig’s challenge, but after a few abortive attempts, gave up, filed the title away, and didn’t do anything with it for a couple years. But a few months ago, when I was examining Twine and idly contemplating a foray into IF game creation, this title prompt came instantly to mind, and the entire storytelling/game structure resolved itself in that moment of inspiration.

And there: I had a story all ready to create in Twine. So I did. It took roughly 2-3 months of dabbling, in total probably less than a week of real-time work, to make a 5-minute IF game.


It took an afternoon to storyboard and write the text for Dragonsauce, and get accustomed to the Twine interface, which was very user-friendly. This was the easy part. After that, I spent several months on-and-off learning the basics of Harlowe (the scripting language beneath the Twine interface) and then scripting it to do what I wanted. I solely used the Harlowe manual to learn; somehow it never crossed my mind to look for YouTube tutorials, but reading instructions and then doing them has always been my default way of learning.

Lots of referencing the manual and trial-and-error: circling back and forth between things I knew how to script, and things I wanted to script but hadn’t reached that level of mastery yet. Rather tedious, but I’m glad I persevered through beginner’s frustration. At the end of this game, I think I’ve mastered enough of Twine scripting to know which references to look up, but will need to keep experimenting and iterating to get a real handle on Twine’s full capabilities. Solidly beginner, starting to move into the intermediate levels.

Being a gamer, particularly an avid player of text-based games, helped a lot with Dragonsauce’s design. I’ve played enough of Fallen London, Open Sorcery, Choice of Games games, and MU*s (the progenitor of both parser IF and MMOs) over time, to have internalized the infrastructure of interactive storytelling. The structure of Dragonsauce literally crystallized out of this melting pot. I knew what story I wanted to tell, and immediately knew how to organize it. I didn’t have to consciously “figure it out”.

Gameplay and story presentation.

Having written only novellas before, interactivity is the aspect of IF that I find most intriguing. How does one present stats to a reader and give them a way of tracking progress and change, while maintaining the integrity of a narrative? How to avoiding making this too explicitly game-y?

Dragonsauce was a particularly good story for learning Twine because it had a modular structure, and each module allowed me to experiment with different ways for a reader/player to progress through the story, and how I might present it narratively. There were only two fundamental stats for me (and the player) to manage, which made it easy to keep track of in the scripting, but still interesting as I got a taste of what additional variables can spin out from two stats (answer: a LOT if you don’t keep yourself in check), and what “balancing gameplay” means and involves. I think the three game endings are well balanced and hope they satisfy the player.

I got sucked into playing around with the scripting, to the point where I had to pull back and ask myself how this served the narrative, and how I can effectively present this as a story, and use storytelling to elegantly cover up the bones of gameplay mechanics. (And how much time I wanted to spend just dickering with an unfinished project!) All this experimentation meant that the narrative of Dragonsauce supports a core gameplay style, instead of vice versa. More game-y and less story-esque than I’d hoped, but I was using this story to learn Twine and its capabilities.

I’m pleased with what I’ve made, and like to think I succeeded with keeping the storytelling vibe while also effectively communicating game/stat changes through narrative. But I wonder what players think. (I would appreciate your feedback very much!)

What’s next?

IF and text-based games are the convergence of reading and gaming, two activities I enjoy, and any place of boundary crossing and convergence that stimulates creativity, tension and new ideas attracts me. I thoroughly enjoyed making Dragonsauce, and found balancing this tension between game and story very engaging. This is my first IF game, but I’m confident it won’t be the last.

Now that I’ve gotten a handle on Twine scripting, I would like to focus more on narrative and less on mechanics. So the next project is to develop a story and keep narrative as the main objective, and see how the Twine medium can support it.

I already have an idea kicking in my head, but it’ll have to incubate a bit longer as other writing projects are taking priority. (NaNoWriMo cometh!)  This will surely be a major project for 2019.

🎨🎮📝No-screen all-creative weekend. Scripted the IF game that’s been kicking in my head for a while. Wrote about half the story text. All done in about two hours, and the weekend is still young.

To do:

  • Finish writing the other half of story text. (completed)
  • Learn Twine – surely it can do what I want it to do.
  • Tweak stat/game balance.
  • Publish by September (next weekend) and get playtesting feedback.
  • Prove to myself that yes, I am capable of finishing creative projects.