i decided to split my database into chunks for ordination and manage it, i have one database per Chapter and a global one. in the global i have the main characters that appears along the game and in each Chapter db I sync with that global db to have all the characters and add the exclusive ones of that chapter.
the problem is if i unfold one actor i only have 1 image in the portrait (the global has 9)
I'm thinking of upgrading as database exported to csv to xml, but first I would like to ask a couple of questions.
1. As an asset developer, you recommend csv or xml (I think once you said xml but I'm not sure).
2. I have been looking a bit xml, but when I export in chatmapper (is the only one that gives me the option to xml) tells me that I generated a template and amending something that is not reversible in the database, which is exactly what changed me in the database?
CSV import/export is much improved, especially in version 1.5.8. But I still think Chat Mapper XML is the most robust format. It works best with Chat Mapper Indie or Commercial (not Chat Mapper Free), though. Otherwise you just have an XML text file that isn't easy to edit in a text editor.
You can import the XML into Chat Mapper and then export it to Excel format. This is a much nicer format than the Dialogue System's CSV because it uses multiple worksheets.
The only catch is that all dialogue entries must have the same field definitions. Chat Mapper requires this. So, for example, if you've defined a custom field "Emotion" in one dialogue entry, the Dialogue Editor's Chat Mapper exporter will add the field "Emotion" to all dialogue entries.
(p.s. - I emailed you a patch for the Sync Actors bug.)
Thanks for the replay as you say xml isnt easy to edit in a text editor, are you thinking to add more options in the export method like pure xml or json?
Maybe JSON in the future. No text formats are easy to edit because dialogue data is complicated. I chose CSV and Chat Mapper because they provide the best editing environments (Excel/Google Sheets and Chat Mapper). articy:draft is also a good editing environment, but it only allows export to XML. It can't import back from XML.
