Pixel Crushers Forum

Hi Tony,
All of my conversation trees and logic are planned in ArcWeave. It's importing like a dream.
I set up my Quests in DS, the arcweave logic that references them works a dream as well.

I'm trying to keep my chapters separated, so that if I'm importing updated convos for chapter 1 no chapter 2 stuff is touched, etc.
My workflow is importing the ArcWeave chapter into a "forMerge" DB, that has a baseID of 10,000. This way I can merge it into the primary DB (with variables and quests set up) no problem.
The issue I've realised is that the baseID also effects Actors, but my characters are all recurring, so I need them to be consistent.

Please tell me if my workflow is missing the point, but atm I'm finding that it'd be simpler if we could merge by string not ID. Actors would always merge, conversations would replace each other, etc.
The IDs seem to be causing me more drama than benefits. Am I missing the point?

Another example is that if I've added more dialogue to a tree in ArcWeave the IDs may shift in the next import so my direct references in DialogueTriggers no longer point to the correct line. Another example of string or title being more helpful to me than IDs are.

Or perhaps if we could add a line of code to our ArcWeave units that force an ID on import? That'd work as well.

I hope this makes sense, thank you so much for this AW import. It really is fantastic.

Pete.

Hi Pete,

The Arcweave import was designed with the thinking that you'd have everything (all chapters) in a single Arcweave project.

To support keeping your chapters in separate Arcweave projects, I'll see if I can add a merge option that merges by name instead of ID.

That's also a good idea to add an option to the Dialogue System Trigger component to jump to entries by Title.

That would be amazing.
And tbh I'd probably consider putting everything back into a single Arcweave project if it did merge by name. The only reason I started breaking it up is because a selective import reset all the IDs.

Yubaba wrote: ↑Thu Sep 15, 2022 10:49 pmAnd tbh I'd probably consider putting everything back into a single Arcweave project if it did merge by name. The only reason I started breaking it up is because a selective import reset all the IDs.

Instead of adding Dialogue Editor > Database > Merge Database by Title, would it work to let you set a Dialogue System Trigger's Jump To Entry by Title (instead of ID) and put everything back into a single Arcweave project?

Yeah, I think so. Because then both parts of the trigger component are looking for strings, rather than IDs, right? (Conversation is already using string values, I believe?)

And that skips the whole multi database problem. I guess I'll have to re-import the whole project every time if I'm not doing merges, but I'll get used to that.

I think the workflow will be more pleasant with a single database anyway. In the next update (2.2.33), I'll also add Arcweave to the "Reconvert" button in the upper right of the dialogue database inspector so you'll be able to just click that one button to import your Arcweave json into the dialogue database.

That sounds great.
Thanks!

Hi Tony, not meaning to rush you, but any news on the 2.2.33 update?

Coming out tomorrow!

WOW <3