Pixel Crushers Forum

ah I've might write this a little bit too soon :) Since I don't know the correct way to "see" the state of ink story I am using: PersistentDataManager.GetSaveData() to preview it. When I play my game it outputs correct values for my variables. Then I save it manually and after that, I'm ca...

Great! Thanks for the explanation and sorry about missing the well-documented feature.

It seems that (again) I am set for now. In the meantime, I've checked that PersistentDataManager also handles Ink integration! Awesome!

Oh my, of course. Sorry for bothering you, that makes perfect sense. One more question tho - is it possible to set ink variable value via dialogue manager? The context is I want to restore state of the conversation (variables, etc) after loading a save in my game. What is the correct way of doing th...

no, I am working with my database that exists way before I've added ink integration. So those 2 entries in a popup are from the regular Dialogue System database. The weird thing is that the story from ink file shows up in the popup sometimes, but it isn't for most of the time. let me know If that le...

yes, the story is assigned to the Dialogue System Ink Integration as it is displayed on the left side of the screen (inside the second inspector). Unfortunately, I cannot find a way to refresh the cached data. I am unable to make it to do a refresh and show ink stories in the conversation popup

Ah, right! That is indeed the way

One more thing - the conversation popup doesn't always list Ink stories. I am attaching an example screenshot from my project.

Thanks, Tony!
But let me ask you a question Is it compatible with `SetConversationStartingPoint`? Because I don't think that it will work with the output from this picker (I mean with the story name prepended)

Sorry for the radio silence here Tony. I think it was something on my side. Currently, I am able to do everything that I want so that is great.

How it is going with the Attributes for conversation and entry points? I would really make use of those

The Sequence() call was indeed in a separate line (it is a lot easier to write ink that way) and moving it to the actual dialogue line resolved the issue of Sequence() being called two times. Despite that there's still something off, look at the screenshot: https://i.imgur.com/DcJna3e.png You see th...

Hi Tony, I've checked the updated integration package and it seems that there is still something going on. I mean it is a lot better, but sequencer commands are still giving me a headache :) Look at my console output below: https://i.imgur.com/yi1MGpU.png Three things can be noticed here: 1. I've go...