Greetings all.
Just an update on the progress of Chronicler 2.0.
Yes, I have started a new project from scratch, and am currently in the process of setting up the framework so that Chronicler runs 10 times faster, and has a //commented codebase that doesn’t fall into the same traps that Chronicler 1.0 did.
I feel I have worked out a new coding style / naming convention that will be more practical down the line, as well as accounting for cross-platform development from the beginning.
Sadly, I don’t have the Linux or Mac modules for GM:S yet, and that is not likely to change unless they go on a 70% off sale. (or I suddenly receive a massive influx of donations) 
Chronicler 1.0 was essentially a playground for hacking together new systems. I was constantly confounded by the sheer amount of bloat this introduced and had to navigate bewildering uncommented scripts trying to figure out how on earth I had solved each problem.
Chronicler 2.0 will, hopefully, suffer significantly less from such problems.
I plan on making sure every bit of code is commented so that I don’t have to scratch my aching head when I have to modify it 6 months down the line.
I also plan on taking more time on each system, ensuring their stability, conciseness, and compatibility with each other.
Furthermore, rather than hacking together a system in Chronicler itself, I plan on having a sandbox project wherein I can test my ideas and iron them out before implementing them.
I will also finally get around to rewriting my CS parser from scratch. The one I have now is an absolute mess, and I’m sure there’s more than a couple memory leaks. I believe that in doing so, I can also fix the issue with *fake_choice’s not connecting properly.
I intend to write a weekly progress report every Thursday documenting what I’m currently working on. This will help keep me motivated to get stuff done.
Right now, I am writing my own Textbox scripts rather than using one that I found on the internet. The one I had was a ridiculous 865 lines of code, and it was run for every textbox every frame. The reason Chronicler was set to run at 500 FPS was to account for the lag this introduced, which led to typing faster than 40wpm meant that some characters you typed were skipped.
there was also a bug where text would suddenly become invisible. The text was still there, and still saved, but was impossible to edit or delete. I was never able to determine the cause of this even though I searched for several hours trying to understand his code.
I also had major difficulty with the code completion inserting text into the box. It was just far too complex for its own good.
So far I have come up with a solution that buffers all keyboard input to ensure that no matter how fast one types, all characters will be received.
I have also made it way simpler. Like 30 lines of code instead of 800.
I am also developing an improved save system that uses JSON (Java Script Object Notation) rather than serializing the data into bytes.
This means that save files can be edited by hand if something becomes corrupted, and they will be more portable if I ever choose to implement a cloud save feature.
However it may or may not increase the file size of .chron projects. I have yet to see if this is the case.
I also have an idea to (optionally) “encrypt” a .chron project so that one must provide a password to open it. The only problem with this is that Chronicler is open source, so anybody who wanted to could dig through the code, find the encryption algorithm, and reverse engineer your password. I would have to exclude that part from the uploaded source code (while providing a dummy function so it still compiles). That will make maintenance a chore, so I will not implement this feature unless someone REALLY wants it.
While I do like Chronicler’s current UI, I’m considering changing it, or, at least, the way scenes are handled. The carousel menu is kind of cool, but I feel that a series of tabs at the top of the screen would be much better for navigation. Also, developing the tab system now would help greatly with my idea for the new Stats Screen editor.
When 2.0 is released, I will also release a new version of the launcher. As it is, I don’t feel it is as aesthetically pleasing as it could be.
So, to sum things up, now is the perfect time to submit suggestions and bugs so that I can deal with them now rather than later.
Thanks for your support and encouragement! The CS community really makes all this work worth it. (: