Updating scripts from ArcWeave
Posted: Thu Sep 15, 2022 9:04 pm
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.
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.