Pixel Crushers Forum

Ah yes. I actually ended up writing almost exactly that method, however I _did_ modify the source so as to keep it alongside the other similarly named methods, and just made a note of it for if I ever perform an update to the plugin for this project.

Thanks for the info!

Our game has a system in place where a player can basically "fail" a conversation, and will be reset back to the beginning of the conversation. However, after this "reset", the SimStatus values for all of the dialog nodes previously visited are now set to "WasDisplayed"...

Great- thanks for all of your help!

I just got to implementing that patch- it works great! Thanks for the changes~ As a side note about the patch: It appears that a warning was put in when the actor and conversant are the same, so now we get these annoying warnings whenever one of our characters has a monologue -- is there a "mor...

Awesome, thanks!  I'll look forward to that patch~

That's not exactly what's going on, but it's close enough that it doesn't matter, heh ^^ Ah- that snippet looks like it's exactly what I need, except in the version I've got here, ConversationModel doesn't derive from MonoBehaviour-- is this something that changed recently? As a side note: is the li...

I did actually look into this myself, briefly. Right now, I have things configured to not use "reminder" subtitles, so that parameter comes thru as null; however with my current implementation, it should be safe for me to change things so that I can use it. The big problem, however, is tha...

Hi there~! Thanks for the response, but I think you might misunderstand my question-- the problem isn't with the displaying of individual subtitle lines (I've already got that working), but with the displaying of the responses. More specifically, what I'm doing, is providing "dialogue settings&...

I'm trying to perform some custom actions when the responses are shown, but these actions differ depending on who the "responding actor" is, as I need to call GetComponent<>() on their GameObject and use some of those MonoBehaviours. It seems that all of the existing events and overridable...