It looks like the tool assumes all scene names will be valid folder/directory names on the host OS.
Specifically, on Windows 10 and Python 3.7 on my Yurivania 1 project, I get the following errors:
NotADirectoryError: [WinError 267]

A number of my Scene Names are not valid Windows directory names.

I haven't used python in a while, but I will try to fix this if I have time later today.

Thanks for making this cool tool! 😄

Currently, the universal __comment argument in events is not preserved either way when converting projects. FIXME before release!

There are tons of events in GB Studio that need to be reimplemented for GBS Toolkit in order for it to convert projects correctly. There are about a hundred, and here are the ones we still need implemented in the V2 beta:

• All control flow events
• All input events
• All sound & music events
• All overlay events
• All scene events
• All text events, except for EVENT_TEXT
• All timer events
• All variable events

I'll write out a full specific list later, but this is a general guideline for folks who want to contribute. Be sure to follow the format for events, and contact me if you have any questions!

switch [var] {
    case [number value] { //true0
        <list of events>
    }
    case [number value] __collapse=true { //true1
        <list of events>
    }
    default { //false
        <list of events>
    }
}

Gonna take some weird messing around with Nodes but it should work just fine, we can assume choices and fill in the default values for unused ones (though this might break expectations? TODO: figure out)

Currently there aren't any unit tests for GBS Toolkit. To implement these I need a project that uses every event and option in GB Studio at least once, as well as something to check order-agnostic JSON contents diffs. This is necessary before release so I don't put out something broken!

Right now, everything in GBS Toolkit is assuming a standard install with no plugins or changes to the engine. If possible, there should be a way to support third-party plugins and engine fields without the plugin/engine devs having to write Python bridge code. Fallback can theoretically work for most custom events, but I don't have anything for something that provides different engine fields. slimit might work for grabbing fields out of custom events automatically, but that feels excessive for what is effectively grabbing a (hopefully!!!) static export. The only real issue with engine fields is that GBS Toolkit converts the names into a more readable format based on purely my own personal preference. I'll need to look at custom engines to see if there's anything I should keep in mind for a more dynamic system.

This may also require specifying a location to load plugins from on the GBSToolkit side.

I should figure out a good way to transfer line info through to the parser, if there is one. Right now, if someone malforms data in a kdl file, GBS Toolkit can't really detect it and will just throw a KeyError if it tries to access something wrong or make a bad .gbsproj file if it slurps up the wrong data. Validation is important!!!

This might be a tkinter issue - I just use the default ttk theme and it might be having trouble with how to draw the dark theme right. It's got the dark-mode text (which is white) but the light mode interface (which is also white). TODO: how do I fix this?

The timestamp entry in music.kdl song entries is accidentally spelled timesamp instead. This does not cause any crashes or errors, and may be irrelevant anyway due to how timestamp numbers are used in GB Studio, but it should be noted.