search

klembot / chapbook

A simple, readable story format for Twine 2.
https://klembot.github.io/chapbook
MIT License
80 stars 25 forks source link

Twine 2.8.1, Chapbook 2.0.0, style and links got broken #194

Closed antemaion closed 5 months ago

antemaion commented 5 months ago

I updated Twine to version 2.8.1 today and noticed that the Chapbook format within it hadn't automatically updated to 2.0.0, so I added it. Later, upon launching a story I've been working on to test it, some things were immediately wrong. I've had my style section set in the starting passage for ages, but even though I have config.style.page.style set to "none", the border around the story appeared with a shadow. Then, clicking a link didn't move the story forward, unless the window containing the story was closed and reopened; otherwise the link appeared as though clicked and could no longer be interacted with. If the window was reopened, the story would appear with default style, and the link issue would persist. Upon testing the story, it seems like the default style is present somehow in the backstage tab, underneath my custom style variables. I've no idea how to get rid of it. None of these problems were present before today.

Attached a copy of the settings and link present in the intro of my story. Also screenshots: the problem before and after reopening the story in browser, as well as secret default style in backstage. TEST.html.zip

Screen Shot 2024-06-12 at 1 40 24 AM Screen Shot 2024-06-12 at 1 40 42 AM Screen Shot 2024-06-12 at 1 41 38 AM

Expected behavior: custom style variables are implemented universally in a story when present in the vars section of its first passage, links behave as they ought to.

I'm using MacOS and Firefox. It seems like greyelf had a similar, probably related, but separate issue recently.

klembot commented 5 months ago

I tried the story you attached with the development version of Chapbook and the styling/clicking issues aren't present there, but I saw them in 2.0.0. So I think that things will work better in 2.1.0. 2.0.0 doesn't add any new features, so you can safely downgrade to a 1.x version until 2.1.0 arrives.