Small hitch with AC integration

[rairun]

I really like the AC integration and how easy it is to run conversations via AC actions. Being able to navigate a nested menu to pick conversation titles is great. The one issue I have here is that changing the conversation titles in the dialogue database breaks the actions, which makes organising it very painful once you've already created your AC actions.

If it is feasible, I would suggest keeping the menu as a way of picking a conversation, but only as a user-facing interface. Under the hood, the custom action would save the conversation ID so that if the title was edited, the action would still call the correct conversation.

[Tony Li]

This was a choice between the least of two non-ideal options. When importing from external sources such as articy:draft, Arcweave, Chat Mapper, etc., conversation IDs may change, but titles are much more likely to remain the same. So we went with titles. The Dialogue System's Asset Renamer tool can rename conversation titles and update references to the conversation in most places, including Dialogue System Triggers, scenes, prefabs, etc., but unfortunately it doesn't update titles in AC actions.

This isn't helpful right now, but version 3 (no release date yet) will do some magic to use Unity GUID references for conversations but allow import/export from external sources that don't know anything about Unity GUID references. This means you won't have to worry about conversation IDs or titles.

[rairun]

Thanks for the explanation! I didn't know importing from external sources could change the ID. That makes sense.

[Tony Li]

Glad to help clarify.