Hi Tony
Can you make a simple example that demonstrates the same issue?
Is it possible that your code is advancing the conversation too far?
You write that the conversation goes to the node after the response node. Does this mean the conversation is moving past the response menu?
Yes, conversation is moving past the response menu, it looks like this:
- Start Game
- Start Conversation
- Node 1: One click -> to finish type writer, Second click -> shows response menu
- Response menu: Click on Response 2 -> It's going to next node, Node 3
- Node 3: One click -> to finish type writer, Second click -> go to Node 5
- Node 5: One click -> to finish type writer, Second click -> shows response for split second and go to Node 6
- Response Menu: is skiped via problem
- Node 6: One click -> to finish type writer, Second click -> go to END
- Start Conversation
- Node 1: One click -> to finish type writer, Second click -> shows response for split second and go to Node 2
- Response Menu: is skiped via problem
- Node 2: One click -> to finish type writer, Second click -> go to Node 5
- Node 5: One click -> to finish type writer, Second click -> shows response for split second and go to Node 6
- Response Menu: is skiped via problem
- Node 6: One click -> to finish type writer, Second click -> go to END
We found the cause of the problem, it was my configuration of Standard Dialogue UI.
Response Menu wasn't under MainPanel. That's why when Input was blocked for Main Panel the Input on Response menu wasn't
Solution to my problem
- I created new MainUIPanel object
- I add Canvas Renderer, Canvas Group, and UI Panel components to new MainUIPanel
- Put all my dialogue box objects under new MainUIPanel
- Setup new MainUIPanel as Main Panel in Standard Dialogue UI