ChatScript
diff --git a/‎BINARIES/ChatScriptMssql.exe
60 KB b/‎BINARIES/ChatScriptMssql.exe
60 KB
diff --git a/‎BINARIES/ChatScriptMysql.exe
8.5 KB b/‎BINARIES/ChatScriptMysql.exe
8.5 KB
diff --git a/‎BINARIES/ChatScriptmongo.exe
7 KB b/‎BINARIES/ChatScriptmongo.exe
7 KB
diff --git a/‎BINARIES/ChatScriptpg.exe
7 KB b/‎BINARIES/ChatScriptpg.exe
7 KB
diff --git a/‎BINARIES/LinuxChatScript64
617 KB b/‎BINARIES/LinuxChatScript64
617 KB
diff --git a/‎BINARIES/chatscript.dll
7 KB b/‎BINARIES/chatscript.dll
7 KB
diff --git a/‎BINARIES/chatscript.exe
7 KB b/‎BINARIES/chatscript.exe
7 KB
diff --git a/‎BINARIES/zlib.lib
14.4 KB b/‎BINARIES/zlib.lib
14.4 KB
diff --git a/‎BINARIES/zlib1.dll
73.5 KB b/‎BINARIES/zlib1.dll
73.5 KB
diff --git a/‎HTMLDOCUMENTATION/ChatScript-Advanced-Layers-Manual.html
Lines changed: 1 addition & 0 deletions b/‎HTMLDOCUMENTATION/ChatScript-Advanced-Layers-Manual.html
Lines changed: 1 addition & 0 deletions
@@ -24,6 +24,7 @@ <h3 id="csboot"><code>^CSBOOT()</code></h3>
 <p>If you create JSON data, you should probably use ^jsonlabel() to create unique names separate from the normal json naming space.</p>
 <p>Changing the content of boot json facts (e.g. <code>$data.value += 1</code>) may create abandoned data in the boot layer (the old value of $data.value) and do this often enough and you may run out of memory since there is no way to reclaim it.</p>
 <p>All permanent facts created during the boot process will reside in this layer while the server remains operational. If you restart the server, whatever was stored here is gone, presumably recreated by a new call to ^CSBOOT.</p>
+<p>Note: In a multi-bot system, you need to define this function ONCE in a common area (like a botmacro file) which is visible to all bots.</p>
 <p>HOW DOES GC WORK HERE if you create transient facts?</p>
 <p>You can also add facts to the boot layer from execution of user scripts. Just create facts from a user script using ^createFact(s v o #FACTBOOT) and when layer 1 is being removed at the end of the volley, these facts will migrate to the boot layer.</p>
 <p>You may define any number of ^CSBOOT functions. This allows both multibot and standalone environments to compile without triggering a complaint about already defined functions, though only the first will ever execute.</p>