#undum

Let’s keep this simple:

Ink [image] is the core narrative engine itself, written in C#. It includes the code for the compiler. If you’re not technical, you don’t need to worry about this. Inky [image] is our ink editor, which is a text editor with support for playing as you write. If you’re just starting out with ink, this is all you need. inkle is the game development studio that created ink (x)

So it’s “a narrative scripting language for games” and yet another CYOA maker. Why do I bring them up? Well, Inkle (the company) “was founded in 2011 by two Cambridge game developers [Joseph Humfrey & Jon Ingold] with a passion for storytelling and beautiful design” (x). They started off with their unique “inklebook” format, which had an early prototype game in ~2008 that Jon described as

an iPad-based choice-driven story made of ‘pages’ which stitched together into a single flow via frequent choice points. It was a lovely UI for a choice-based game, even in prototype form, and we had a strong scripting language underneath it – the first version of ink. (x)

In January of 2012, they released “a web-tool for writing and reading simple interactive stories” called inklewriter. Joseph described it as “a simpler subset of the inklebook format” (x) and admitted “inklewriter was partly born out of the surprise that there isn’t anything out there for quickly and easily writing non-linearly.” (x)

After already having “moved away from developing inklewriter for a long time,” it went “permanent beta” in September of 2017 due to “increasing frequency of persistent bug-reports.” Sad news considering the statement “we’ve had hundreds of thousands of stories created by hundreds of thousands of users; we’ve won awards from school and library associations; and hopefully we’ve helped kickstart a few interactive writers careers” (x). And since writers (who became aware in time) were able to “rescue” their story from the bugs and potential wipeout with a simple Save Page As, it was probably a bit less heartbreaking when inkle revealed less than a year later that inklewriter would be shutting down completely in August of 2018. Seemingly because “it’s real work to fix the issues that arise” with the constant browser changes. 😐

Only 7 months later, it returned in March of 2019. Stable, still free, and now open-source after developers in the open-source community “produced a full port of inklewriter to modern web-tech.” 🥳 Writers needed to make new accounts and import their stories to the new database, but that was it. And since the legacy version was (and is) still around, they could do it pretty quickly. (x)

But where dahell was I going with this? Let me tell you about the original connection first: Unity Integration.

The [ink-unity-integration] plugin provides you with everything you need to get started with ink in Unity. It automatically recompiles ink files as you edit them, and even comes with a simple previewer that lets you play stories directly within the Editor, without writing a line of code. (x)

Remember Ian Millington’s statement from awhile ago? “But the best benefit, and in some ways the one least exploited in practice, is the ability to use Undum as part of a bigger game. I imagined a strategy game with CYOA elements, or a piece of interactive fiction using natural language generation to be different each time.” (x)

Well,… Stoic Studio (announced that they) did it in January 2013 when they used inklewriter for The Banner Saga. Though, inkle recommends you use their ink scripting language instead for Unity projects. 🤷🏿‍♀️ A scripting language that was ported to JavaScript in May of 2016, btw. The port (inkjs) having its latest release just 6 freaking days ago while Undum and Raconteur had their last GitHub edits in 2018 & 2020 respectively.

Either way, Ian’s imagination of “a strategy game with CYOA elements” happened… with another mofo’s software. 😐

And what’s that? I left something out?

I left working on Undum to develop Varytale, a short lived commercial IF endeavour that shared a lot of the same aesthetic and narrative structure. And then I retired, and it lay fallow, aside from email help requests that still drip into my inbox. -Ian Millington (x)

Let’s see what IFWiki says about this endeavor:

Varytale was a platform for authoring and publishing browser-based CYOA, created by Ian Millington and Alexis Kennedy; it occupied a point somewhere between Undum and StoryNexus [a comparatively mostly defunct endeavor from 2012]. The Varytale website was live from approximately 2011 to 2015. The first posts on Varytale’s blog appeared in June 2011. On March 7, 2014, Varytale posted a comment on the Varytale Facebook page saying, “The project is stalled, due to key people leaving the project. So there’s no news, and I’m not sure if or when there will be.” The last Wayback Machine snapshot of www.varytale.com/books was taken in September 2015. (x)

On its May of 2012 public beta announcement on FailbetterGames website, something slightly poignant was said.

But the technology is great [seriously] - it’s easily the most flexible and powerful tool of its kind, and it’ll be fascinating to see what people can do with it once the writers’ programme opens up. And as it happens, Jon Ingold / Joseph Humfrey’s very elegant inklewriter has also just gone live [4 months prior]. (…) …[inklewriter] covers some of the same territory as Varytale, but it’s (by design) simpler in concept and execution. (x)

Life is truly cruel.

If you check the archive from possibly days before its shut down in September of 2015, you’ll see 4 official books (Bee, Fighting, How To Read, Hymn & Shanty) and 3 User Published Books (London Road, Sixth Tower, Tillinghast). That’s 7… 7 books. 😐

But it’s not that sad. According to the Varytale blog’s 2nd to last post (in June of 2012), “we passed 50,000 reads across the seven books currently on our reader’s beta.” This was perhaps a full week after they released the floodgates and actually allowed people to start readin’. Das alot to me. They clearly succeeded in “building a platform for authors to write great books, and for publishers to publish them.” Even built a whole-ass “system that does generative design,” creating “artwork based on the author’s choice of patterned design or photograph” (x). Or, as we’d quickly say 12 years later, some AI shit.

So wut 👏🏿 in da fuq 👏🏿

Why’d they never get past the 7 book mark in the 2 years between Reader’s Beta and project stallation? Well,… there’s a hint at the end of that 2012 blog post: “We have a queue of people wanting to write content, who are been added a few at a time. So lots of hard work in the beta still to go.” hm~ 🤔

If The Way Back Machine had archives past January of 2013, we’d definitely know more, but this is it (i ain’t diggin’ a wider hole at this point). And what is it? I think it’s a matter of workload. Too much for too few people who had however much goin’ on in their lives. Remember much earlier this bit from IFWiki?

On March 7, 2014, Varytale posted a comment on the Varytale Facebook page saying, “The project is stalled, due to key people leaving the project. (x)

Maybe things weren’t smooth enough for awhile. Maybe it was something else for those 2 years prior. 🤷🏿‍♂️ And you know… the end of Emily Short’s blog post Writing for Varytale might hold the answer.

There are still some challenges about using the Varytale system, though it’s evolved tremendously over the course of beta. One of the biggest authorial challenges is that, while there’s the awesome structure tool shown above for looking at branching structure inside a storylet, it can be considerably more challenging to get a view of what’s going on at the macro level. And I’m not even sure what the tool for this ought to look like. The strength of storylets is that they can affect which other ones pop up in a fairly freeform way, and one can affect another (via their shared stat use) without explicit logic in either. But that’s also what makes it really hard to graph how they will act. Most of the bugs that arose in Bee were related to this issue of envisioning the total structure of the work and detecting storylets that were going to break that structure. (x)

So in this case aswell, the innovations of Ian’s Varytale make it… (a bit) intimidating to work with. 😑Whether or not this difficulty was ever ironed out post-beta is unknown to me, especially considering the end of Ian’s thankful response to Tom H.’s suggestion for fixing the macro level problem: “When will I get chance to code it? That’s a whole other matter!”

…hm~

And on the same post lies magnus4444’s statement that “There isn’t a lot of documentation out there yet on the implementation of more advanced effects but, on the plus side, Ian is generous with advice and tips.”

🤷🏿‍♀️

So wtf do we have here. Effectively two developers (i’m simplifying it; fight me) who 1) made a CYOA maker (Undum & inklewriter) for very similar reasons, 2) put development aside to focus on other CYOA makers (Varytale & Inky), 3) had their neglected work taken up by open-source developers for the good of everyone, and 4) reaped the benefit of the other’s labor in some way. Now, here’s where we’re back to the sad part. Inkle’s version of the tale is the American Dream ™. Inklewriter was beloved by many and had mainstream success. Ian’s version is the harsh American Reality. Undum only bore 24+ games over the course of its 13 year existence on the internet and in the world of IF. And if a single person’s opinion is to be taken as fact… then the reason was simple: shit wasn’t easy to pickup. And thus, regardless of Ian & Bruno’s efforts, it (at this rate) is bound to become an obscure software regardless of its potential. All while Varytale remains gone and Inky (released in June of 2016) is still goin’ strong with 160+ games released using its Ink language/engine.

Which brings me back to the matter…

For as long as she could remember, she had been stuck in this endless white void, where pain and permanence didn't exist. She didn't know about the wonderful outside world, so she was happy in there. But still, she was human, so she got bored. So bored that she decided to hurt herself to pass the time. Mind you, there were no blades or anything dangerous in there, just them, so she just decided to break her fingers. There was no pain, and the fingers got back together again, as if nothing happened. She decided to pull he hair out, and every time she blinked, their hair would appear again, but she still held the strands she pulled out, so she started to pull out her hair indefinitely, making piles and piles with it, with no consequences

Then, she pulled out her fingernails, then skin, then bones. It was just normal. Nothing happened, and now she had plenty of things to play with

Still, from time to time, she would learn random things out of the blue, like how to walk, or speak, or what the name of those hard things at the end of her fingers were. It was just normal

Sometimes, the white void would dissappear, and instead she would be in an unknown place with colors and things she had never seen before, she later learned those were called fields. After a few seconds, the void would come back. A bit weird, but they got used to it over time

One day, another person appeared. It looked just like her, but she had colors instead of Sora's blacks, whites, and shades of grey. They became friends :D

Later, she learned that those weird things she saw sometimes were the real world, and that the person she met sometimes was the one who sent her into that white void

She wanted to punish the other person for taking away her normal human life, with fields and colors and family, so with a sword made of teeth and bone she killed the other