Hello @harrymfa, wow! thanks for the time for providing a very detailed feedback, I really appreciate it!
About the pain points:
The database-centric collaboration.
I agree 100% that there should be another method of collaboration that doesn’t involve setting up a server. Especially git. But I don’t want to be involved in conflict resolutions/merges etc. What I could provide is some sort of “work from file” setting that would let the user use a json file as database (essentially a backup) and concurrency/conflict resolutions should be handle by the user and would be out of the scope of the app. I’m open to suggestions of any type on this subject!
There are sections that are in the app, Quests, Items, Misc, that serve no purpose but text data entry.
Well, the main focus of the app is to provide different ways for data entry, it is not necesary to use them all or to split it as presented. I agree Misc and Items might be redundant. However, I’m planning to add an option to enable/disable modules so you could theoretically remove “misc” db from showing up if you want to.
Merging scripts with dialogues might not be a good idea as they serve different purposes. (a dialogue might have a script, a script might not be a dialogue)
The UI is not particularly intuitive.
YES! I can see a major pain point in the workflow you just described, and should be refined. It’s not much but here’s a tip. If you double click in a script for example it locks for editing.
**Now, the documentation, to put it kindly, it needs work. ** No need to put it kindly, the docs are lacking and are quite useless.
And finally, here’s a feature suggestion…
This is on my radar, and it will be definitely be spreadsheet based!. I just have some issues refining the process (how to keep a “linked” translated version that updates with the original)
Thank you very much for the feedack, it is really useful!