sugarcube-2 VS tweego

I'm currently using Twine 2.3.9 with Sugarcube 2.36.1 and trying to run the numberpool macro. I've posted the CSS and JS files into the "Edit Story Stylesheet" and "Edit Story JavaScript" text boxes, respectively. But when I try to run the numberpool macro, I wind up with the error code:

SugarCube is a little more barebones, but this also means more freedom. If you are a little more experienced with HTML, CSS and JavaScript (or plan to learn some by making a Twine game), I'd recommend learning SugarCube rather than Harlowe. Documentation: https://www.motoslave.net/sugarcube/2/

You can go without it and feel fine. But if you have custom stuff, you'll use some macros and scripts. What are they? Imagine Twine as a core, but it has various engines that do things differently. It supports four such engines(story formats) to make the creation process more accessible. Each of them varies in complexity. In this article, I'll be using SugarCube.

I strongly suggest you consider changing your project to using the 2.x series of SugarCube instead.

As for examples, I would suggest looking at the source code of SugarCube's own built-in macros, because they use the same APIs as you would to create your own custom macros.

I'd recommend switching to the SugarCube story format, if it's not too late for you to do that. It has an approach which is far more open and amenable to creating your own custom inputs, such as sliding bars.

I strongly recommend using the SugarCube story format, since it's flexible and has the most built-in tools of any of the default Twine story formats. In the SugarCube "CSS" documentation section, it shows you how you can change backgrounds using tags you set in your passages and CSS you put in your Stylesheet section. Also, if you really want to have your own UI in SugarCube, you can use the StoryInterface special passage to change the layout however you want (though this will take knowing a bit of HTML and CSS).

This means that you just need to update your version of SugarCube to get your code to work. The easiest way to do that is to just update to the latest stable release of the Twine editor. If you're not using the Twine editor, then you can download the latest version of the SugarCube story format from the SugarCube site.

I'm not quite sure what you mean by a "full list of selectors". I'd recommend checking out the SugarCube "CSS" documentation, especially the "Built-in Stylesheets" section. You might also check out the "Bleached" stylesheet, from the SugarCube 2 page.

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.