Pixel Crushers Forum

Hey there, I've made some quests for my game with Dialogue System and I'm planning on trying Quest Machine as well. My question is, can both systems share the same Quest HUD and Quest Log UI? I looked at some tutorials and it looks like the quest machine UI is a different prefab. I'm wondering if I should just transition everything to Quest Machine since it looks like it supercedes the functionality of Dialogue System quests? I don't know if I really need any of the functionality Quest Machine offers but it would be nice if I can define different quest descriptions per quest state since I didn't find a way to do that with the Dialogue System but it's a relatively minor feature and I'm not sure if transitioning over is worth it. Any tips with this?

Hi,

They use different UIs. A DS + QM setup typically uses Quest Machine's HUD & quest journal (log) UIs, and the Dialogue System's dialogue UI.

Feel free to give Quest Machine's evaluation version a try.

If you decide to stick with the Dialogue System's quests, you can show different descriptions in different quest entries. It's not quite the same, since you'd be additively showing certain quest entries' text instead of changing the quest's main description text, but you can get a similar effect.

Yea I tried adding different quest entries for different states but all the entries show up in the HUD regardless of their quest state. So I'm not really sure what the use case is for the quest entries other than if you have multiple goals in one quest. I guess that's what the documentation means by subtasks. I expected it to only show the entries that match the current quest state. So for example I was hoping to change the HUD to display 3/3 items obtained (complete) when the state is returnToNPC but it doesn't work like that apparently. The entry quest state doesn't seem to do anything.

Each quest entry has its own state. If the quest is active, then the quest's main Description field will appear in the HUD. In addition, each quest entry whose quest entry state is active will also appear in the HUD. So you'll want to make sure to update quest entry states as the quest goes through its stages. When setting up a quest that has quest entries, you'll usually set entry 1's state to active and the rest to unassigned. When the requirements for entry 1 are met, set entry 1 to success and entry 2 to active, and so on.

You can also change the behavior of what appears in the HUD. For example, you may want to include completed quest tasks, but with a different appearance such as in a strikethrough font.