Post by baj in Integrating Dialogue Data

Viewing post in Integrating Dialogue Data

Hello there! The implementation is really up to you! I would parse the graph.nodes array, locate the “start” node (or any other useful node) and start crawling from there.

Some useful props:

In the extras property you have the type, and the scriptID associated with that node.
Inside each node you have a ports array which you can use to get all in and “out” ports (1 for script nodes) so you can build your flow with that.
Once you reach a choice node, you can query its “out” ports to show the different options to the player, the link array associated with that port will give you the id of each connection the port has, so you can navigate to the next node.

Basically what you have there is the whole graph serialized. The dialogue player is a (super simple) example on how to implement.

Hope it helps!

bojjenclon1 year ago

Hey thanks for the info! I’ve got basically everything working, I just have one follow up question: how to find a given actor’s info in the Director from a Dialogue? In the export, the actor seems to just be the name supplied between the colons. However, it’s theoretically possible for there to be multiple actors with the same name, so just doing a naive name match on actors in the Director data seems wrong. How is this mapping meant to occur without the ID supplied to the Dialogue for the line’s corresponding actor?

baj1 year ago

Well the ::ActorName:: tag Is supposed to be unique, meaning, the app would autodetect and group the same string into the same actor. It is, in practice, an ID. I think the “real name” should be inside the properties, but again, is up to your implementation. Hope it makes sense!

itch.io

Viewing post in Integrating Dialogue Data