You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: WIKI/ESOTERIC-CHATSCRIPT/ChatScript-Control-Scripts.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,9 +201,11 @@ u: () # whatever normal processing you do for user sentences
201
201
The primary rule for output OOB is that it is within [] and is the first thing in the output. You can write rules that directly embed OOB with the user message like this:
202
202
```
203
203
u: () \[ action=wave \] How are you?
204
+
```
204
205
205
206
But that gets messy and if you output multiple messages, you cannot easily combine distinct OOB messages into a single composite OOB. Therefore the usual technique is to
206
207
define a macro that holds OOB data and use a postprocessing topic to output it at the end.
@@ -213,12 +215,14 @@ u: () ^OOB(action=wave ) How are you?
213
215
topic: ~postprocess system repeat()
214
216
t: ( $oob ) ^postprintbefore( \[ $oob \] )
215
217
```
218
+
216
219
In the above code use $$oob instead of $oob (pdf converter didnt like it)
217
220
218
221
# Changing input token processing
219
222
220
223
There are times you may want to alter input processing by changing $cs_token. For example if you ask the user their name, on the next user input you probably don't want spell checking
221
224
happening which could make a mess of foreign names (or even normal English ones CS is not aware of). So you want a convenient way to temporarily change $cs_token. Here is how:
225
+
222
226
```
223
227
# in your bot definition make a copy of your normal $cs_token
224
228
outputmacro: yourbot()
@@ -236,6 +240,4 @@ topic: ~postprocess system repeat()
0 commit comments