Pixel Crushers Forum

Hello!

First of all, thanks for providing this helpful tool! Our team is using Dialogue System for Unity with CeltxGem and those were great tools to handle content.

We also would like to know, if possible, what future plans exist for importing content from CeltxGem since we plan to use the breakdown for writers to define some custom behaviors.

Hi,

We're working on adding import for breakdowns and multi-breakdowns. The current plan is to add them to their conversations as empty dialogue entry nodes -- but I'm open to any suggestions for how you'd like to see them imported into the Dialogue System.

Hi!

Our strategy is to add breakdowns as fields in the dialogue entries and also import gameplay content as empty dialogue entries. We understand of course if that's not the most convenient solution for all cases.

cbrito wrote: ↑Thu Oct 27, 2022 7:12 amOur strategy is to add breakdowns as fields in the dialogue entries and also import gameplay content as empty dialogue entries. We understand of course if that's not the most convenient solution for all cases.

That was my first impulse, and it was an entirely arbitrary thought to add breakdowns as separate empty dialogue entries. Since no one has specifically asked for breakdowns to be empty dialogue entries, we'll go ahead and implement them as fields in the dialogue entries. The plan is to get these changes into version 2.2.34, with a Celtx import patch out soon after version 2.2.33 releases on November 5 so you can import breakdowns and gameplay content before 2.2.34.

That would be awesome, please let me know when that patch is up. Many thanks for your support!

This patch, which is in version 2.2.33, adds support for breakdowns and multitag breakdowns, which will be added as fields in the corresponding dialogue entry.

DS_CeltxGem3Patch_2022-11-08.unitypackage

• Characters will be imported as references to actors in the dialogue database, using the field title "BreakdownActor", "BreakdownActor2", ...
• Items will be imported as references to items in the database, using the field title "BreakdownItem", "BreakdownItem2", ...
• Locations will be imported as references to actors in the database, using the field title "BreakdownLocation", "BreakdownLocation2", ...
• Custom breakdown items will be imported as text fields, using the field title "BreakdownCustom", "BreakdownCustom2", ...

Hey Tony! Thanks for the update!

If you have any suggestions for handling breakdowns better, please let me know. When going from one system to another (e.g., Celtx to Unity), these things are always up to interpretation, so writer feedback is really helpful.

Hey Tony!

We were extremely busy last month so only now we got time to get back to this. Everything works fine and we are able to progress in our project thanks to the last update!

However, our lives would be easier if there was an option to import gameplay as empty nodes with its own breakdown items (I noticed that they will appear in next dialogue anyway, so it's not a huge deal) and if you could add the type of breakdown as the field key instead of "CustomBreakdown".

Thanks again for the support, we are very happy with it and with the tool!

Hi,

Yes, I think we can accommodate that. I'll try to get it into version 2.2.35.