huge bug in chapbook 2.3.0 ??

Authoring Twine
1

Twine Version: 2.12.0 and 2.11.1
Chapbook version 2.3.1 and 2.3.0
Firefox version 128.13.0esr (64 bit)
NoScript version 13.6.16

EDIT: just updated to the newest version (april '26) of Twine and chapbook, the bug is still here, so the versions above got accordingly edited.

EDIT 2: added the noscript version in the light of the mystery described in a subsequent post.

I have just discovered that EVERY work in Chapbook I have around has suddenly ceased to respond to clicking on links, always stuck on the start page, either in test or release mode.

I don’t know how and why this happened, and when: the last Chapbok edit is November 24, 2025.

The Harlowe and Sugarcube works are fine, though: so I guess is a Chapbook-related bug, and a serious one.

someone has an idea on this huge bug ?

Perplexed regards from Italy,
dott. Piergiorgio.

1 Like
2

Are you about to supply an example project (Story HTML file) that includes the code you used to produce the bug.

Because I created a new Chapbook project and was able to use a Markup based Link in the 1st Passage shown by the project to transition to a 2nd Passage.

1 Like
3

tried build a new chapbook work; the bug is still there.

but I noted a strange reporting in the debug window, in the State tab:

config.random.privateState	{"i":92,"j":9,"S":[123,28,5,54,243,93,245,71,94,41,175,27,190,130,37,164,72,13,6,238,211,214,240,8,103,39,127,144,86,209,159,137,21,201,207,186,81,98,48,110,4,2,129,223,151,35,60,140,220,44,171,113,215,10,150,109,102,219,217,89,133,30,40,228,147,42,126,195,237,83,0,131,146,114,23,45,188,174,80,204,199,213,221,177,143,222,85,95,165,132,20,78,248,12,178,193,96,116,239,138,200,168,224,115,18,172,161,192,53,232,119,82,249,212,99,120,108,216,173,36,149,16,250,69,187,87,106,76,38,26,107,160,66,74,11,117,100,125,154,242,184,51,141,56,189,231,202,128,135,75,251,88,67,62,84,142,49,139,15,22,163,183,19,246,254,241,134,169,180,156,97,55,203,33,253,205,176,152,218,236,145,91,235,225,197,104,229,255,227,64,25,24,77,155,191,226,52,65,196,179,43,7,162,31,111,234,244,185,252,73,208,101,158,148,34,182,47,198,247,57,46,61,32,118,157,233,136,121,181,230,50,29,1,153,206,210,9,166,92,14,59,122,63,68,112,70,105,124,3,58,17,79,194,170,90,167]}

Dunno what means, but I highly suspect that is related to the issue.

anyway, there’s the HTML and twee zipped together:

test_chap_bug.zip (44.2 KB)

thanks for the help, and
Best regards from Italy,
dott. Piergiorgio.

4

config.random.privateState shouldn’t cause any bugs whatsoever, it appears on every Chapbook game I have made and all of them are working as intended.

1 Like
5

image

The example seems to work for me, at least just running the .html and not trying to do anything with the .twee file.

I guess to eliminate some possibilities, have you tried different browsers? Incognito mode? Disabling extensions?

1 Like
6

different browsers: not possible, only firefox+adblock+noscript is trusted (chrome is well known for its “nosyness”…) and the “armoured configuration” seems to have a role in the issue, see below for a very strange behaviour.

in incognito mode the problem is still here, but the real mystery came from disabling noscript: if I click (w/o results) the “this link will work” with noscript enabled, when disabling it, the displayed passage automagically became the second, and the most curious thing is the same happens in the reverse, that is, if I click “this link will work ?” with noscript disabled, then enable back it, the very same happens, the displayed passage automagically became the 2nd, and this is what mystify me.

Someone can figure this mystery ?

(noscript version added to the original post in the light of the deepening of the mystery)

Perplexed regards from Italy,
dott. Piergiorgio.

7

Regarding web-browser extensions / addons (like Firefox’s noscript) that either fully or partially disable JavaScript from running within a web page or that restrict access to the web-browser’s LocalStorage area,

The Story HTML file(s) that the Twine 2.x application generates are a Single File Web-application (SFWA), that contains a JavaScript base runtime engine that’s responsible for processing the embedded Passage definitions to generate the page content the end-user sees.

And this Single File Web-application stores its Progress History (passages visited & related Story Variable states) within the web-browser’s LocalStorage area.

So enabling an extension / addon that disables JavaScript will likely affect the Story HTML file’s runtime engine’s ability to work, and enable the web-browser’s “incognito” like mode (or enabling an extension / addon that preforms a similar action) will likely affect the runtime engine’s ability to store information in LocalStorage.

2 Likes