Pixel Crushers Forum

Hi!

That's what we intended given the Celtx project I showed you in the first message

Hi Tony! We tested the lastest Dialogue System version with the patch and we have the celtx dialogue id in each node and conditions are fixed. Although the breakdown field issue in the example, we replicated the issue in a different situation. We were able to fix the issue ourselves. See if the foll...

Hi again!

We updated Dialogue System for version 2.2.35 (we were on 2.2.33) to test the patch and apparently the importer is not importing conditions anymore. Is this issue known?

I've added a JSON with an example.

Hi Tony!

The patch fixed the Field key issue, but unfortunately the first node Field valeu is wrong. The second is correct.

Hey Tony, We've found a bug, or unexpected behavior in the celtx import related to shared breakdown fields with different custom types. Here's the steps to reproduce Create two different Custom Types Add a first breakdown of the first custom type Add a second breakdown field of the second custom typ...

Great, thanks for the help!

Thanks Tony!

Can you give us an estimation for when we can expect the next update?

Hi Tony! We were wondering if we could suggest a change in the celtx import. Right now, when we import, all dialogue nodes from the same celtx script are populated with the same script ID in the Celtx ID field. We would like that each node could have the ID of the celtx dialogue node. Best regards, ...

Works perfectly, thanks a bunch for all the help!

Hi,

I don't care too much about the order, so the order they appear in the JSON file is ok.

Grouping the items seems like a better idea than mine, you can go for it.