Pixel Crushers Forum

Have been trying some different configurations, but am still trying to reproduce the setup used by us in a clean project. In the meantime, I can relay that RandomizeNextEntry() has a hard time being used with the None() node too, which causes it to be a text field that gets shown even if there is no...

We don't use that many PC nodes, they are mostly NPC ones. The place that I seem to always get an empty dialogue seems to be if I jump before any text has been shown.

Might be possible, but it would take some time cleaning out what I can send from what I can't. In the meantime, do you have any other advice?

Tested both with and without dialogue text in the node where I use Goto(). It seems like the chat box opens either way but if there isn't any text it just sits empty for a while, and if there is any text in that node it writes it out before moving on to the jump location.

As per the thread that I linked, direct lua scripts used in the dialogue node that wants to jump away doesn't work for some reason. It seems to jump away for one message, but returns to the original conversation after one message. This problem was also seen with using a scriptable object event in th...

Hi! I'm using a sequence to jump between databases at runtime, and it mostly works except for the fact that an empty dialogue panel is showing up during the jumps. I've tried using my sequence in combination with others like Continue() and HidePanel(0) to try and make the Dialogue System skip showin...

Thanks for the proposed solution! I found that if I call the code I used above directly in a script Lua field, it only shows the field that I want to jump to, and then keeps running the previous dialogue. The same thing happened if I used a scene-independent event that called the code through a scri...

Hi, colleague of Tom here. We've tried both the paths given in the other thread, and while the first hacky link-to path works, the setup cost and the fact that the cross-database links break every time you need to use the Unique ID Tool makes it a no-go. The second method of calling another database...