String references is a limitation
String references is a limitation
Hello! I ve recently purchased the asset. Great with many powerful features! Some of them work with string references and if I change the string the reference is lost and it doesn't work anymore. Isn't there a better way e.g object reference?
Re: String references is a limitation
Hi,
Thanks for using the Dialogue System!
What object references are you trying to get?
The primary one that can be a challenge is changing conversation titles (e.g., in Dialogue System Triggers). However, this needs to be a string reference because the Dialogue System can import and export from external formats, and other types of internal references such as GUIDs may not be maintained by the external application, so string references are the only way to keep them consistent.
Thanks for using the Dialogue System!
What object references are you trying to get?
The primary one that can be a challenge is changing conversation titles (e.g., in Dialogue System Triggers). However, this needs to be a string reference because the Dialogue System can import and export from external formats, and other types of internal references such as GUIDs may not be maintained by the external application, so string references are the only way to keep them consistent.
Re: String references is a limitation
Hello again . I am referring exactly to what you are saying. Every string that I create to quest, conversations, variables etc which are assigned to a Dialogue System trigger. When I change a string, the reference is lost. Couldn't be a way that the dialogue system, find and change the strings automatically?
Re: String references is a limitation
I can look into that for the future. For actors and quests, keep the Name field the name, but change the Display Name.