Pixel Crushers Forum

My pleasure! Version 1.4.1 is now also on the Asset Store.

That recipe describes how to use a conversation to select characters and enable/disable their player control scripts. To use plyBlox on a button press, try this: 1. Add player controllers and NPC controllers to the character. Disable one or the other. For example, keep the player controllers active ...

Hi!



I'm working on video tutorials for plyGame, SALSA, and the new Unity UI. I hope to get them out by the end of the week.



What kind of character switching are you interested in doing? I'm not sure exactly which part of the documentation you're referring to.

If your own interactable/interaction classes work the way you want, it's probably easiest to use them and hand-send OnUse. The Dialogue System's triggers accept three forms of OnUse: OnUse(transform), OnUse(string), and OnUse(). When possible, use OnUse(transform) so you can pass the transform of th...

Hi, Thanks for using the Dialogue System! Many developers are still using Unity 4.5, and a couple are platform locked on 4.3 until their games ship, so Unity 4.6 and 5.0 features have been isolated to maintain compatibility. Version 1.4.1 (just released) will be the last version to support Unity 4.3...

Version 1.4.1 is now available on the Pixel Crushers customer download site. It includes TextMesh Pro support. If anyone needs access to the site, please email your Dialogue System for Unity Asset Store invoice number to tony (at) pixelcrushers.com. Version 1.4.1 should be on the Unity Asset Store i...

Version 1.4.1 (with an image color option) is now available on the Pixel Crushers customer download site, and should be on the Unity Asset Store in a few days.

I'm glad it's working now! If any other issues pop up, please feel free to send me an example project.

It's on the Sequence Trigger. It's a fairly recent addition. If you don't see the checkbox, please update to the latest version on the Asset Store.



Edit: There was also an intermittent timing issue that's fixed in v1.4.1.

Make sure the conversation participant with the behavior tree has a "Dialogue System Callback" component. Try setting the Dialogue Manager's Debug Level to Info. This will log a lot to the console. Look for 'Dialogue System: Starting conversation...' when you start the conversation, and 'D...