Pixel Crushers Forum

Okay, so this might not sound like a problem based solely on the title, but allow me to elaborate.
So here is my issue.
I have a node that plays a timeline (the second one): Here are it's sequence commands: Currently, the way my team has set up Dialogue System clicking anywhere on the screen while the dialog box is on the screen advances dialog. That alone might be our issue, but here is what is happening. Usually, while a timeline is playing and the dialog box is off the screen the player can click all they want and the timeline will just play out. However, if while the player is still on the first node pictured above and quickly clicks twice, the timeline starts to play but then is immediately skipped. For clarity,

be on the first node
click once
timeline plays
player can click as much as they want

vs

be on the first node
double click quickly
timeline starts then is skipped
player misses timeline

I've tried using the "required" before the timeline sequence command but that hasn't changed anything. To elaborate, I am having this issue wherever timelines play with the exception of when a timeline appears in a conversation before any dialogue is displayed.

We have a way of skipping the timeline intentionally already by pressing esc and we'd prefer that that would be the only way so that the timeline isn't skipped unintentionally.
If any additional info is needed I will gladly provide it, thanks to any who take the time to read and comment!

Hi,

Here are two things to try:

1. Change SetDialoguePanel(false) to SetDialoguePanel(false,immediate). This will immediately hide the dialogue UI instead of playing the hide animation. Otherwise the player could click the (whole-screen) continue button while the hide animation is playing.

2. Or add this sequencer command to the top of the Sequence: SetContinueMode(false). This will disable the continue button so it can't be clicked.

Also, add "required" in front of the final SetDialoguePanel(true)@Message(Continue), as well as SetContinueMode(true)@Message(Continue) if you use SetContinueMode(). Otherwise it's possible that Continue()@Message(Continue) could run before them, causing them to not run.

Thanks Tony! I went with the second option and it works like a charm! Much appreciated!

Also, thanks for catching the missing required, that is a great point. I've made sure to include it on the SetContinueMode(true)@Message(Continue) like you also recommended.

Glad to help!