Pixel Crushers Forum

Hi,

I wasn't able to identify any issues from that log output. Here's an updated example scene that demonstrates a quest state listener with a conversation:

TPC_MountHorseExample_2018-03-19.unitypackage

I appreciate that you checked it. I will give this scene a try.

The dialogue did prompt quest status indicator change to green when I tried the new mount scene, and that was inside the same project as my game. I will try to make simpler quest / dialogue and try again in my scene.

Thank you for going out of your way to put that together. It was really helpful

I also checked the horse scene with the updated DS-TPC integration package. The mount also triggers the quest status indicator now. I will try it in my scene.

Ok, I seem to have found the source of the issue with the quest state indicators not changing in my scene on the particular NPC...

I created a different conversation and a simple test quest similar to the example scene you shared. I changed the conversation in both the listener and the conversation trigger to the test quest/conversation. And this did work.

When I went back to the original conversation and quest, I realized that the listener changes the quest from the original quest (Report to Colonel) to Test by itself... Therefore the indicators do not get updated.

Then I deleted the test quest and conversation and tried again. And apparently the listener changes the quest name to null... I choose it from the drop down itself, so I do not think I am entering the quest name wrong. Any idea what would cause this?

The quest name goes back to null even for the test quest now as soon as I hit play. If I change the quest name to any quest name in runtime then it goes back to null as soon as I enter the NPC's trigger area.

Hi,

Is it possible that the Quest State Listener is using a different dialogue database than what's assigned to your Dialogue Manager? (Check the database that shows up in the Quest State Listener's Quest Name section.)

Ultimately that's fine, but the Dialogue Manager needs to know to load both of them. To do this, add an Extra Databases component to the Dialogue Manager, and assign the extra database to its Databases list.

If you'd rather keep all your info in one database for simplicity, you can merge the contents of one database into another. To do this, open the database in the Dialogue Editor window. On the Database tab, expand the Merge Database foldout.

If that's not the issue, please feel free to send a copy of your project to tony (at) pixelcrushers.com. I'll be happy to take a look. (All files are handled confidentially.)

I just double checked and they both refer to the same database. I will give it a try with a fresh mind one more time, and if I cannot figure it out I can send the project over to you for checking. Thank you.