@xedur I look forward to seeing your plugin! I started noodling a bit with my own (non-plugin-ized) parsing tool specifically for Twine 2, whose interface I prefer to Twine 1.4 as well as Yarn - but Twine 2 doesn’t support JSON exports, and only kicks out HTML, even for the source file. So the parsing is a little trickier, but so far it’s working. One thing I like is that instead of simply pointing to a Twine text file inside of my project folder, I can optionally specify a path to the HTML file outside of my project that Twine reads/writes - if I’m opening the project in the simulator, it compares the current text file against the Twine HTML original, and overwrites it if there is a delta, enabling me to simply make edits in Twine, refresh the simulator, and have a new text file with the changes ready to go in my project folder. I imagine making that feature “one size fits all” might become a bit of a nightmare, but it’s working well for me in my Mac-only environment.
Looking forward to seeing how you approached things!