2014: 80 Days

80 Days
by Inkle
Script by Meghna Jayanth; directed by Jon Ingold and Joseph Humfrey
First Published: July 31, 2014 (App Store)
Language: Ink
Launch Platform: iOS (iPad/iPhone)

Opening Text:

London, 1872

I have entered into the service of a new gentleman.

It would seem he is a gambling man.


“A question that we got repeatedly asked,” the speaker noted about his studio’s first game, “was ‘yeah, but like, do my choices really matter?’”

People say, “well, I’m pressing this button, but it doesn’t really matter, does it? You don’t really make any difference.” And that is the canonical problem of branching narrative. That’s the one that every single purveyor of branching narrative is constantly, desperately trying to solve: convincing you that the choices they make you agonize over have any impact on the game at all.

The talk was on choices in interactive stories: what they’re good for and how to design them. The speaker was Cambridge-based Jon Ingold, and the studio was called inkle. He had co-founded it in 2011 with Joseph Humfrey: the two had both worked on briefly-hot motion-control games for Kinect and PlayStation Move. The tiny company’s goal was to “explore what new narrative experiences were possible on tablets and phones.” Motion tracking had started to feel like a gimmick, but ubiquitous touchscreen devices like Apple’s iPhone (and especially the larger iPad that launched in 2010) seemed an intriguing platform ripe for experimentation.

Ingold had grown up reading gamebooks and playing Infocom text adventures, seeds of a lifelong love for the pleasures of mingling reading and play. In his late teens and twenties he’d written parser IF in Inform, including acclaimed titles like The Mulldoon Legacy (1999), All Roads (2001), and Make It Good (2009). But he’d grown frustrated with the limitations of the parser. Telling stories that centered characters and dialogue was hard with a verb-noun interface (though some had tried anyway); and parser games could be inscrutable to outsiders, severely limiting their audience. “Whenever I showed one of my games to someone who hadn’t played a text adventure,” Ingold recalled, “they would be completely stumped. ‘You’re meant to type in what to do? But what should you type? What should I do?’”

The inkle founders hoped the shift to a new platform could offer an excuse to challenge longstanding norms of interactive narrative design. One of their first precepts was that “text is a visual medium”: rather than dumping it to standard output to let a terminal window or OS handle its rendering, taking charge of typesetting and presenting text beautifully would go a long way toward encouraging players to actually read it. inkle’s first release was an interactive adaptation of Frankenstein (2012) with gorgeous typography, presented like a traditional gamebook: long passages of text interrupted only occasionally by choice points, and no stats or other game-like elements to distract from the reading experience. The reaction was mixed. Ingold would dryly recall: “Gamers generally didn’t like it because it was a book. Book people generally didn’t like it because it wasn’t a book.”

The studio found more success with their next release: Sorcery! (2013) adapted a fondly remembered 1980s gamebook into an extended digital edition. The design iterated in several major ways on Frankenstein. It added visible stats which might go up or down in response to events or choices, useful “to help reassure readers that what they’re choosing is definitely being noticed.” Another insight was to break long passages of prose into short, snappy sentences with frequent choices, even if they had no lasting consequence. A faster interaction cycle kept players engaged and let authors use choice more for pacing than exclusively for big, weighty decisions. “Instead of just ‘should I kiss them or turn away,’” a writer for inkle noted, “alright, do I move up my chair? Do I meet their eye? Do I sit a little bit closer? Do I lean forward?”

The writer was Meghna Jayanth, contracted for an unrelated project in the wake of Sorcery!’s success. While Ingold and Humfrey cranked away at a sequel, they hoped that Jayanth could start researching and writing material for a new game originally planned as a smaller-scale experiment. The plan would change. At first contracted to write perhaps ten or twenty thousand words, Jayanth and Ingold together would ultimately write closer to three-quarters of a million.

The new game was to be based on Jules Verne’s 1872 novel Around the World in 80 Days, in which English gentleman Phileas Fogg makes a wager that he and his valet Passepartout can circumnavigate the globe at a speed only recently become possible. Having partnered with a book publisher for Frankenstein, the inkle team had considered what other well-known stories in the public domain might make good foundations for game adaptations. In particular, they were looking for stories based around maps. Another key innovation from Sorcery! had been realizing how critical it was to help players understand the relationship between their choices and the story. Ingold recalls that in Frankenstein,

the common reaction was, ‘My choices don’t make any difference; they don’t matter; they don’t affect anything.’ And we’d say, well, actually they do. There’s a system under the hood and it’s got these options—but there’s no UI to show you that. It just looks like a book that writes itself.

But then we found that when we showed people a story graph of Frankenstein, and then they read it, they said, ‘Wow! I just feel so on edge and every choice matters.’ It was all about creating that expectation of branching first. So we spent a long time thinking, how do we put a flow chart in an interactive book without it looking like a flow chart?

The solution was to frame the Sorcery! interface around its map, with major choices tied to decisions about which paths to take or places to visit. Suddenly players had an implicit understanding of their position within the narrative possibility space. They could see how far along they were on the journey, how near they were to its end, and understand that because they’d decided to go left, they were missing out on any stories that might have been to the right. Maps “proved” branching, Ingold realized, and they had any number of other benefits besides: they demonstrated cause and effect, they showed off the existence of unexplored content, they lent visual interest for an otherwise textual story, and they let players strategize about future moves—how do I get over there? So Verne’s story had seemed a natural fit, based around the familiar yet intriguing map of the world. On a mobile touch screen, you could even satisfyingly twirl the globe beneath your fingers while planning a route.

Verne’s novel also provided other useful structure. First, its episodic nature worked well for a player-directed narrative. Each stopping point on the journey could hold a self-contained story that didn’t need to appear in strict sequence, giving players more agency over their route. And Verne’s novel offered another useful constraint. A key plot point is that heading east means gaining a day by crossing the international date line; the extra time proves crucial to securing the wager. Eastward-only travel would allow “narrative structure that occurs without forcing users into choke points”: introductory material and story arc setups could be placed in Europe, with advanced content and conclusions showing up in the Americas.

While Ingold and Humfrey began designing UI and mechanics with an aim to keep iterating on the successes of Sorcery!, Jayanth began wrestling with the problems of how to update a nineteenth-century novel to work in the twenty-first. Her game Samsara, written for the StoryNexus platform, had caught the inkle team’s eye not only for its beautiful prose but because it had taken a historically grounded setting and added a dose of the fantastic. It seemed clear a similar approach was needed here. To give players the same sense of wonder felt by readers of the original novel, the game ought to offer something modern readers would find equally fantastic. “A steam train isn’t wondrous anymore,” Jayanth noted: “It was at the time.”

Sticking to a historical 1872 also presented a game design problem. Verne’s novel had been inspired by the recent openings of the Suez Canal and transcontinental railways across both India and the United States; the only sensible route at the time would connect those three conveyances. To give players the chance to chart their own unique journeys there would need to be equally speedy and compelling routes available all across the globe. So Jayanth and the inkle team decided to set the game in an alternate history, where technological innovations of a kind modern readers would still find intriguing were happening on every continent. The game establishes this change from its very first sentences:

Monsieur Phileas Fogg returned home early from the Reform Club, and in a new-fangled steam-carriage, besides!

I helped him down... [tap], and the iron-lunged, steam-driven horses clattered away.

“Passepartout,” said he. “We are going around the world!”

80 Days would go steampunk. But Jayanth hoped the project could avoid the kinds of uncritical pastiche that genre had been increasingly criticized for. It’s a style where “we keep the victoriana,” she wrote:

the bustles, the elaborate upper-class courting rituals, the arranged marriages and the stiff upper-lips—and elide away all the dirt and muck. The class politics are blunted in favour of a nostalgic enjoyment of silk dresses and soirees.

It’s a nostalgic, escapist vision—I am quite happy to go so far as to call it a fetishistic one. It’s a vision that has very little room for people of colour (who very much existed in Victorian Britain!), for queer people, for poor people. If they exist, they exist as victims. That seems dangerous and broken, that this is escapism, that this is fantastical. That glittering world of adventure and courtesy is built on oppression and suffering.

Instead, she began to imagine an alternate world where the astonishing innovations of Verne’s imagined futures had been distributed more evenly around the globe. An 1872 took shape where “the automaton armies of the Zulu Federation turn away the depredations of European colonists scrambling for Africa—where the technology that built the British Raj is being used to dismantle its foundations—where the Panama Canal is dug using Haitian ingenuity, tipping the balance of power away from the United States—and where the stories usually told in the margins spill over into the text.” Steampunk, she wrote, “is often written as a modern fantasy of an imagined past. We wanted to create something a bit different: a historical fantasy of an imagined future.”

The shaba-meli was a rigid, helium-filled metal balloon; an African invented-and-produced form of air-travel.

The balloon itself was made of thin, interleaving layers of copper... [tap]

It seemed impossible that it could hang in the air...

...and tin mined in Katanga and constructed by the Nyamwezi chieftains.

We were accompanied on our journey to Ulundi by the strange, macabre sight of wheeling squadrons of wood-and-copper birds with diamond shards spinning in their hollow chests.

...Their eyes were bright...

...I was captivated by their beauty... [tap]

...Their purpose in the sky seemed clear enough...

...their bright-beaded wings beat against the air, and their diamond shards glittered like stars in the endless blue of the sky.

The Zulu Federation crew waved and called out to them respectfully.

“I have never seen such automata.”...

“Why do you speak to them?”... [tap]

“Because they are emissaries of our Emperor,” one of the navigators explained, amused by my question. “We must treat the Emperor’s automata with great deference.”

The new setting provided a clue to another problem Jayanth was grappling with: how to address the white savior tropes in the original story, where two Europeans charge uncritically through a world still filled with the radical injustices of European empire. A chief insight was to realize that the story need not always be about Fogg and Passepartout. “Is it possible to write a game in which your protagonist isn’t the hero?” Jayanth wondered. “Or maybe, less provocatively: can you write a game in which your protagonist isn’t the only hero?” She began to rethink the role of NPCs, typically passive characters who follow the player’s orders or wait for them to come save the day: “quintessential victims,” she realized. Instead, she decided to write characters actively solving their own problems and telling their own stories, which yours would only briefly intersect. “You are a tourist,” she wrote: “you do not get to be as important as the people that live there [in the places you visit]. You may be able to touch and nudge at a revolution, or participate in one—but it is not yours.” In short, “the world of the game turns—but it doesn’t turn around you.”

The Nefertiti was a tall-masted Egyptian clipper that sailed around the coast-line from Antalya all the way to Alexandria.

I asked the skipper if he had considered longer voyages... [tap]

I was content to enjoy the ride...

...via the Suez Canal, but he only laughed. “The fees, young man, are quite extortionate.”

I could not argue with that...

“How extortionate?” [tap]

...I asked.

He gave me a pointed look. “You will not buy me or my boat,” he replied, “if that is your intention. My liberty is worth more coin than you have.”

I nodded, and we did not pursue the conversation further.

In one sequence at an Australian hotel, Passepartout meets a Murri maid who has written a letter protesting the white settlers’ treatment of Aboriginal peoples. She wants to bring it to the local newspaper, but doubts they would ever print it. The game presents you with a choice offering to deliver it for her, Jayanth explains:

to use your whiteness and maleness and your protagonism, basically, to help her. But she refuses. She doesn’t trust you—because of all those things, because you’re an outsider, because you’re white and male. You’re closer to the oppressor than you are to her, and all the good intentions in the world can’t change that.

It might feel unfair to present the player with a problem they can’t solve, Jayanth notes, “but maybe unfair isn’t the worst thing a game can be.”

Rethinking the foundational assumptions of both story and systems continued, in a highly collaborative process that “grew and grew until it encompassed first every working hour, and then every waking one.” The game that emerged nine months later would be quite different from Sorcery! or anything else on the market, with a unique structure that Ingold later described as “self-narrating board game.” The game’s mechanical spine is essentially a just-in-time trip planning simulator, where the player must chart a round-the-world course one departure at a time while making trade-offs between money, time, and Fogg’s well-being—as a valet, the health of your employer is a prime concern. Markets in most cities let you buy and sell goods which can help fund your journey, ease the stress of travel, or lubricate friendships along the way: “Having a box of snuff to hand might get a train guard on the Siberian Express to tell you what she knows about links between Yokohama and San Francisco,” one reviewer noted. But another observed that “choosing the next leg of your journey isn’t as simple a booking passage on the fastest mode of transport”:

This gyrocopter might not be leaving for three days, a nearly unbearable delay, but it’ll take you to a city where you could sell one of the items in your suitcase for a hefty sum. ...Traveling by car might be quick, but it’s also tiring, and Fogg can only put up with so much discomfort.

The mechanics interact in ways that encourage constant decision-making from the player. Depleted funds can be restored by visiting a bank, but this wastes precious time while waiting for the money to transfer. A clock that visibly advances while in a city adds pressure: if you visit the bank or take too long dithering in the market, you might miss your next connection. Exploring a city, if you can afford the delay, unlocks new stories and new routes—though not always to places you want (or can afford) to visit. This decision-making mirrors and complements many of the narrative choices in the stories found in each city: impressing a mayor might unlock a seat on a faster conveyance, while a lapse in judgment could result in Passepartout parting with too much of Fogg’s cash. More stories unfold on each possible route between stopping points—and in the final game, there are over four hundred possible connections.

5:00 PM
Hover-ship to Antananarivo
£110
(💼 2/2) The hold has space for two suitcases, which will suffice.
(❤️ -18+9) Baking Sunshine and Mild Seas: This looks like a wearisome route, but the Panama Hat from our Warm Climate Gear set should see us to rights

“The fiddly bits of making the trip work wouldn’t be nearly as much fun if the writing in 80 Days wasn’t so good,” a reviewer noted. The vast library of content—with potential stories including teeth-rattling road trips, Arctic catastrophes, submarine kidnappings, high-stakes poker games, and even a trip to the moon—was written using a language called ink. A custom scripting tool created early on by inkle, ink was designed to minimize markup and let writers “quickly and robustly create heavily branching flow that runs naturally from beginning to end—as most interactive stories do.” While hypertext editors like Twine and StorySpace often used flow charts to visualize story nodes, Ingold felt this approach was overkill for works that centered forward momentum with no wrong choices or dead ends. Rather than force authors to spend time manually repositioning boxes or dealing with the headaches of adding or removing them from the middle of a chain, ink let you author with a plain text markup:

weave:neworleans
- I met Death in a smoke-wreathed red-lit bar in New Orleans, as the jazz band struck up another tune. He offered to buy me a bourbon.
  *"Holy mother of Heaven."," I blasphemed succinctly, -->
  *"Perhaps in twenty or thirty years?"[] I replied archly, -->
  *(wet)I threw my drink in his face[] in an automatic gesture of defence, -->
- as some of the other patrons snickered.
Death pulled off his mask to reveal handsome café-au-lait features and dark green eyes, and then extended a {-->wet:dripping} skeletal hand to me.
  *"A fine costume[."]," I remarked.
  "/Merci, mon cher/, -->
  *"You gave me a fright[."]," I admitted.
  "My deepest apologies, /mon cher/, -->
- I am Death at our neighborhood Mardi Gras, and I am practising my role." He took my proffered hand and brought the back of it to his lips for a gallant kiss; he flicked me a rather unmistakable look under his dark lashes.
  *I returned his look[] with one of my own, and he let my fingers slip slowly through his {raise(style)} -->
  *I pretended not to see [it] his look, or the sensuous tilt to his mouth, and he laughed. -->
  [...]

In this sequence the story flows forward, with player choices indicated by asterisks and the right arrow showing a jump to the next “gather” point (dash) where the story continues. Text up to and including bracketed content is shown to the player in a menu of choices, and reprinted without the bracketed portion when the story continues, flowing it into a seamless transcript: after clicking “You gave me a fright” in the second choice point above, the text in 80 Days appears like this:

I met Death in a smoke-wreathed red-lit bar in New Orleans, as the jazz band struck up another tune. He offered to buy me a bourbon. I threw my drink in his face in an automatic gesture of defence, as some of the other patrons snickered.

Death pulled off his mask to reveal handsome café-au-lait features and dark green eyes, and then extended a dripping skeletal hand to me. “You gave me a fright,” I admitted.

“My deepest apologies, mon cher, I am Death at our neighborhood Mardi Gras[...]”

Other commands let authors redirect the story to different named nodes; a compiler automatically finds situations where the story would stall out. As players progress, they might accumulate changes to stats (such as Passepartout’s “style” above) and visited nodes are automatically tracked so later text can contextually vary (as when “Death” gets soaked by a drink). Sub-choices can be nested under parents to arbitrary depth, letting authors easily build complex branches within individual choices without worrying about labels and jumping. Designed specifically to allow easy creation of the kinds of interactive stories inkle wanted to tell, the company also took pains to keep the language simple:

Every feature you add to a tool changes the way the tool presents itself to new users, and changes a user’s perception of what the tool is for. So add five cool niche features and your tool might start to look like it’s for making fiddly, avant-garde things only. ...as tool creators we have to keep returning to our users and saying, what are these people like? What do these people care about, and what don’t they care about? What message do we want to send them about what they should be doing?

Working with ink, Jayanth and Ingold were able to write an incredible amount of content for 80 Days: more than 700,000 words, 150 cities, and 16,000 individual choices. While the episodes at each destination and along each journey are largely independent, certain characters and events recur, and each playthrough reveals only portions of the stories the world’s countries and peoples are playing out on a global stage. Jayanth has called this “worldbuilding instead of plot,” letting players piece together for themselves the story of the Artificer’s Guild, or the Sisters of Didacus, or the Imperial Kriegorchester—an army of automatons controlled by music and “Mozart-Haydn devices.” The big-picture stories contrast with the game’s hundreds of smaller vignettes: stunning vistas or memorable characters who cross your path only for moments, before you inevitably move on.

I drank shots of homebrew liquor with a Dutch sailor... [tap] who was mourning the loss of his third finger to frostbite. “Got seven left, I s’pose,” he said, with admirable aplomb.

High player agency, compelling stories, and real replayability—most round-the-world journeys reveal less than ten percent of the possible text—led to a play experience that felt thrilling to many jaded players and reviewers, too used to games where choices rarely seemed to matter. One wrote that the game had “taken the long-ignored strengths of Interactive Fiction... and applied them in the right way on the right platform to give the player an experience that feels wholly unique, and more importantly, wholly their own.” Another felt that “each decision feels less like straying from the intended path... and more like letting the fiction take you new, exciting places. ...The difference between 80 Days and many other narrative games for me is that each path feels like the intended one.”

When Jayanth first joined the project, one of her concerns had been Verne’s character Aouda, who eventually becomes Fogg’s bride. “Aouda is not just Indian,” she has written:

she is an imperialist’s vision of India: rescued from savagery and ignorance by the cool-headed rationality of an Englishman; a grateful bounty that delivers itself willingly into the hands of the benign master.

My problem with Aouda’s—India’s—mistreatment in the original text is personal—as I happen to be Indian, and a woman. But thinking about Aouda was a spur to me to start thinking in more general terms: what kind of shape and structure would be required to create a game that included people like her?

Thinking about how to address Aouda’s story became one of several spurs for the radical rethinking of the game’s world that gave its characters back their agency. And as the stories changed, the writers found a surprising undercurrent in Verne that felt more resonant with the twenty-first century: the allure of a barely hoped-for possibility that change might sometimes be for the better. Jayanth noted the anti-colonialist themes of 20,000 Leagues Under the Sea, in which brown antihero Captain Nemo fights the imperialist oppressors who murdered his family. Ingold observed that Aouda was “a trophy wife by definition, [but] on the other hand, that’s a mixed race marriage in 1872.” Jayanth adds:

Aouda is deracinated and it’s problematic but that’s the thing, if Verne could go so far, if we are trying to write Verne today, we have a responsibility to go even further and write something that’s progressive for our time. As progressive for our time as Verne was for his.

“Peeling back the layers of nostalgia and assumption is the right thing to do,” Jayanth has said, “but it is also a gift to the writer and reader/player: there is such an opportunity here, to tell unknown and surprising and challenging stories.” Reviewers and players overwhelmingly agreed, praising the game both for its reimagined history and its rethinking of interactive narrative conventions. Among other accolades, TIME Magazine named it Game of the Year for 2014—across all games, not just mobile titles. It helped establish Jayanth as a leading voice in games writing (later contributing to games like Horizon Zero Dawn and recent indie open-world game Sable), and provided runway for inkle to keep innovating with titles like the acclaimed Heaven’s Vault (2019), continuing to find new audiences for interactive stories by figuring out the reasons most folks don’t like to play them.

The creators of 80 Days took the time to question the foundations of both their source material and the medium they were working in. Sometimes that’s what it takes to find something new worth building.

Next week: [incoming communication] … [establishing connection] … [receiving message] …Hello? …Is this thing working? …Can anyone read me?


You can find links to buy 80 Days for various platforms on the inkle website; the company’s latest release as of this writing is Overboard! Find Meghna Jayanth on Twitter @betterthemask or megjayanth.com; Jon Ingold is @joningold and Joseph Humfrey @joethephish. You can find out more about the free ink scripting language and its tools and community on its official site.