Open torbenvanassche opened 1 month ago
Adding that I can work around the issue by just calling next() and checking the string for empty. Either I am missing something or this is a solution to the problem :)
Haha thanks for filing this. It is actually very tricky issue I've been messing with. Personally, I've been using empty string AND choice as end signal, but also I've added a new flag called eod_reached in the response that you can use to read as final dialogue.. ill keep this open and continue documenting/fixing so that it's more intuitive.
I looked at the code in the
dialogue_reader
and may have found a potential bug that I don't quite know how to work around. I have a simple setup with a single node for testing and the signal is firing after everynext()
call.This result makes sense given the
_process
function saidsI print the first line, call
next()
and theend_of_dialogue_reached
is emitted. I would expect it to only fire after the next line is printed (which also happens)Am I using this plugin wrong? Could you point out how I can fix this code so I can properly use the signal?