Dex

Seems (according to #2 ) that the first error is because none of the files are not documented. Gonna document at least one file to see if was something that...

@hiulit Seems like the npm install creates two files to execute your module, a kind of bash file (cmd) and a script file (ps1). Being not able to call `gdscriptify`...

Anyway, gdscriptify is unable to create documentation. I include my console log with the folder files: ```Powershell PS C:\Users\Lenovo-pc\Documents\Godot-EventSystem> gdscriptify node:internal/fs/utils:344 throw err; ^ Error: ENOENT: no such file or...

@hiulit `gdscript` is being executed in the folder (as you can see in the first line in the previous reply) No idea why is using that path, I just ran...

@hiulit If it's there anything that I can do to help to track this and solve it, let me know. If you had discord and need me to do some...

Just tried, still getting the weird error ```cmd C:\Users\Lenovo-pc>gdscriptify -v v1.1.0 C:\Users\Lenovo-pc>cd Documents/Godot-EventSystem C:\Users\Lenovo-pc\Documents\Godot-EventSystem>gdscriptify C:\Users\Lenovo-pc\AppData\Roaming\nvm\v17.1.0\node_modules\gdscriptify\src\core\parsers\parseFile.js:326 return word[0].toUpperCase() + word.substring(1) ^ TypeError: Cannot read properties of undefined (reading 'toUpperCase') at C:\Users\Lenovo-pc\AppData\Roaming\nvm\v17.1.0\node_modules\gdscriptify\src\core\parsers\parseFile.js:326:28...

Update: Experimenting a little, setting the directory path for the plugin did the trick to generate documentation ```cmd C:\Users\Lenovo-pc\Documents\Godot-DialogPlugin>gdscriptify --directory "./addons/textalog/" GDScriptify ----------- Markdown files created: 6 out of 11....

Now with #42 , maybe an editor `Preset` event can be created, wich stores a timeline, and events in that timeline are spawn as subevents (not in a subtimeline)? Need...

Seems pretty complex for now, but is a good idea.

This is interesting but we'll need A kind of UI prototype for it