harlowe-audio VS sugarcube-2

https://twinelab.net/harlowe-audio/#/v2?id=configuration

Following all the instructions given on the Official HAL Guide I was able to get it working with Absolute URLS. They are placed inside an isolated passage titled "hal.tracks" and work fine. However, for compatibility's sake, I want to use Relative URLS. So currently my sound effects look like this:

You may want to try copying in the code again, since unless the code you're copying from has an issue (and do make sure it's the latest release from the source), that errors suggests you're missing something causing the brackets not to close. The guide might be of help, if you haven't already followed it.

Harlowe 3.2.1 Harlowe Audio Library (twinelab.net) and Configuration (twinelab.net).

This chunk of the HAL documentationhas some excellent examples of snippets showing pause and play commands for a given track using Harlowe macros. I hope this helps!

The Installing HAL in Twine 2 section of the above linked documentation site explains how to add the required JavaScript to the Story JavaScript area of a Twine 2.x application project. It also explains how to add the required CSS to your project's Story Stylesheet area.

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.