Re: About Dialogue Actor component
Posted: Mon Mar 15, 2021 9:45 pm
Please feel free to rest after your work hour Actually this frees me from refresh the forum before 10 hours later
Setting empty conversant will cost the reuse feature, so I don't want to use it. Perhaps it will be much more useful when more than 2 Conversants are supported
I may had a great misunderstanding. Is it able to get an existing List of all Entries of the conversation in StartConversation() method of DialogueSystemController? Not a new generate one, but already exists before call StartConversation(). If there is not, then It's difficlut to modify the Entries, and my suggest's benefit becomes little.
And Response object should have it, too.
------------
But this could be another over request of mine. I havn't thought it very deep. For now the specific result I want from this is to have a Fields only belong to the running conversation, and is able to be used in the Condition and Script of entry.
Setting empty conversant will cost the reuse feature, so I don't want to use it. Perhaps it will be much more useful when more than 2 Conversants are supported
I may had a great misunderstanding. Is it able to get an existing List of all Entries of the conversation in StartConversation() method of DialogueSystemController? Not a new generate one, but already exists before call StartConversation(). If there is not, then It's difficlut to modify the Entries, and my suggest's benefit becomes little.
Yes, This is a great help! Even better than my request. It even solves the "same conversationID conversations" problem.Subtitle object had a reference to its ActiveConversationRecord?
And Response object should have it, too.
That's why I request this. For resuable conversations, duplicate it to a new one, In this way editing Entry's Fields will not affect the original one, and multiple conversations based on the same origin could have much more variety. It's not to change all the conversation into this way, but have an option when StartConversation.Quest Machine creates instances of quests, but the Dialogue System works differently. All conversations in the Dialogue System share the same dialogue database.
------------
But this could be another over request of mine. I havn't thought it very deep. For now the specific result I want from this is to have a Fields only belong to the running conversation, and is able to be used in the Condition and Script of entry.