tweego VS ink

This game was made originally with Tweego for the Twine interactive fiction engine (which is where you should start).

Anyway, I eventually tried using TweeGo instead of the web editor, and I have found it to be a huge boon to my workflow!

Second, (and this one probably IS relevant), I moved out of the Twine editor and into the waiting arms of Tweego And oh my word, it has helped so much.

There are a number of modern TWEE (Notation) command line "compilers" that are in use today, TweeGo being the most popular of them in my opinion.

You'll need to install Tweego, a tool that can parse stories as files in any preferred text editor. Be aware of its limitations, though:

I have to edit an archive that is full of HTML character representations such as '. It is not an actual HTML file, though, but rather a file generated by Tweego. The HTML representations are not pleasant to read, but I wouldn't change the file. Would it be possible to simply make they appear rendered, for my own sake?

There's a text-based representation called twee. You can use tweego (https://github.com/tmedwards/tweego) to convert between twee and html/twine.

Good set of feedback. The Twine UI could definitely use some improvements, but you may want to consider looking into a Twee-based workflow for better control over your experience. Tools like Tweego let you write Twine stories in raw text files, which you can lay out and edit however you want in an editor of your choice. You can find past discussions about how to get started on this subreddit.

In general, though, standard workflow is to use Tweego as your compiler and VS Code as your editor with the Twee3 Language Tools extension. There are plenty of other extensions for spellcheck or JS/CSS linting, but T3LT is the essential one. All of those are available for free, though there's resources online and elsewhere on the sub that'll explain how to get them running better than I can.

While not JSON specifically, twine index.html files can be parsed into (or natively written in) Twee with tools like Tweego, which is a fairly easy-to-parse file format. Certainly an option if you have existing Twine stories you'd like to transfer.

What does this have to do with Inkle's Ink? Well, Ink is a form of engine-agnostic game data creation. At heart, Ink is a narrative scripting language but because it was conceived as middleware, it can be used by many game development stacks. The primary integration is Unity which supports many platforms on its own but Ink scripts can also be run in the browser, Defold, Godot, Unreal and more. You can write Ink once, test it using Inky or Inklecate and deploy it using your desired framework. I can personally attest to running the same Ink script in the browser with ink.js and in the Defold, Godot and Unity game engines.

That's awesome, thanks!

I am aware of Inform 7, I think it is awesome. A few months ago I made a quick demo using Inklescript[1], which I found simpler and more suitable to my project (a Star Trek adventure). Inform 7 remains something I wish to explore in the future when I need something more complex.

Thanks! ;)

---

[1] https://www.inklestudios.com/ink/

As others have said, Twine is really a great starting point for text or choice-based games. If you'd like to get into the weeds a little more, I'd also shout out Ink, which is incredibly flexible and really fun imo, altho it def requires a bit more coding experience.

On the technology side, you might want to check out Inkle: https://www.inklestudios.com/ink/

Start writing in ink or twine.

Otherwise, Inkle is also quite good. (and people have made players for it in Unreal and Unity, so it's not hard to attach to existing game projects.) I don't think it has the nifty visual flowchart though, if that's a piece you care about.

I really like Ink. The developers made tons of games with it like the Sorcery! series, so it has a good foundation, and it's quite easy to write and organize, more than twine in my opinion.