Index signature for looping through attributes
Define a condition or intent that executes the bit.
Define a condition or intent that executes the bit.
A subsequent bit can even lead back to its own parent or any other bit, creating a mesh of possible conversational pathways.
A bit without a condition or intent can still be executed by calling
doBit with its id. This could be useful for defining integration logic
that does something outside chat, but can be triggered by chat scripts.
A subsequent bit can even lead back to its own parent or any other bit, creating a mesh of possible conversational pathways.
A bit without a condition or intent can still be executed by calling
doBit with its id. This could be useful for defining integration logic
that does something outside chat, but can be triggered by chat scripts.
Function to call when executing bit (after any defined sends)
To send if response unmatched by branch
Function to call when response unmatched by branch
Regex or string converted to regex for branch to trigger bit
For scene and/or dialogue, branch running the bit (required)
Key for language processed intent to match for execution
Key/s (strings) for consecutive bits (implicitly creates scene)
Key/val options for scene and/or dialogue config
String/s to send when doing bit (must have this or callback)
Execute with current state (e.g. send replies and/or call callbacks).
Generated using TypeDoc
A single interaction between user and bot. Could be a command to trigger a callback, a request for data or just a connecting line of dialogue.