Greasy Fork镜像

Thank you for this awesome script, unfortunately it doesn't seem to work with stuff made by 2.0 version of interactive CYOA creator. Please, if possible, could you update it?
Here is some of the CYOAs: https://kagamicrescent.neocities.org/CYOA's/Fate%20NSFW%20cyoa/
https://accuratevariety.github.io/Project-/

Well. That would be quite tricky, considering that it no longer exposes its engine to the page. (Dunno if it's intentional or a coincidence…)

It might be possible to do something (emphasis on might), but only if I get really invasive with the modding (think modifying app code as it's being downloaded by the browser). …That is, if such a hack is actually doable with this implementation in the first place.

Well. That would be quite tricky, considering that it no longer exposes its engine to the page. (Dunno if it's intentional or a coincidence…)

It might be possible to do something (emphasis on might), but only if I get really invasive with the modding (think modifying app code as it's being downloaded by the browser). …That is, if such a hack is actually doable with this implementation in the first place.

Dang, that's a shame, I came here to suggest the same thing, but if it's not possible then it's not possible. It seems most of the new ones are being created using the new 2.0 version, and a lot of old ones are even being updated and replaced using the 2.0 version too. Oh well, I appreciate the mileage I got out of the script already, so thank you for making it.

…I've pocked around a bit; apparently it's been rewritten from Vue to Svelte (for whatever reason).

It also seems to expose a proxy object of its app state; so it might be possible to do something with that – though it's likely going to be much more inefficient than what I can do with the Vue version (e.g. I'd have to recalculate the active choices list every second or so, by individually checking the state of every choice card).

The proxy object proved less helpful than I expected it to be… though at the very least it became possible to do something to begin with.

The implementation for ICCP2 is workaround-ish at best, and loading from an URL state requires literally imitating user input 🥲
(For that reason, Creator app and Full Scan mode are completely unsupported for ICCP2)
…Also the row buttons in that E.S.P.E.R thing (linked in OP) gave me a lot of trouble, because the exposed app state does not indicate if they're toggled on or off 🫠

Still, it appears to be usable… If you encounter any major issues with it, inform me so that I can try figuring out if there's anything I can do about those.