Pixel Crushers Forum

So, I just updated the Quest Machine, the Dialogue System, and More Mountains' Top Down Engine.

Everything works great, except I am now unable to do an exploration quest (which is an exact copy of your tutorial on youtube -

I have tried to recreate the quest twice by going over your youtube videos in the most meticulous amount of detail but it still is unable to work. It seems (though I could be super extra wrong) that the Trigger Event component isn't working properly. So, I start the quest (I have it set up so you have to press the interact button to talk to an NPC and get the quest as opposed to entering their trigger box), which works fine, but when I go and explore another NPC (he's sick so we need to check up on him by entering his trigger box), the quest doesn't update.

I have looked at an older build of my project, I have compared all game objects and components with each other, I checked the debug system, I made sure that the NPC that I am checking has the correct message that is sending to the system but I just cannot seem to fix it.

Do you have any idea what it possibly could be?

I should mention that I've linked the Quest Machine and Dialogue System together. I'm using Top Down Engine v 1.4, Quest Machine v 1.1.12, and Dialogue System v 2.1.10

Hi,

TopDown Engine is a complete project, which means it overwrites project settings, including the Physics 2D collision matrix. Select Edit > Project Settings and check Physics 2D settings. Make sure that the layers you're using are configured to register collisions.

Also double-check that Edit > Project Settings > Player -> Other Settings > Scripting Define Symbols includes USE_PHYSICS2D.

To confirm that the Trigger Event is firing off, you can temporarily add something else to the OnTriggerEnter() event that's very obvious, such as pointing it to the Quest Machine GameObject to play an alert message, or activating a GameObject.

You can download the tutorial assets from the Quest Machine Extras page. If you download them and import them into your project, does Scene 02 Final work correctly?

Holy beanbags, it was just making sure that USE_PHYSICS2D was in the settings! Thank you so much Tony!

Glad to help!

Whenever you update TDE, it will overwrite your project settings, including the Scripting Define Symbols. To add back PHYSICS_2D, you can select menu item Tools > Pixel Crushers > Common > Misc > Enable Physics2D Support.