Updates config docs to reflect new values

Author: JujuAdams

docs/3.0/concept-actions-functions.md

@@ -199,12 +199,9 @@ What a beautiful evening, Amelia.
 In this example, both `<<HideTheMoon>>` and `<<FlickerStars>>` are custom actions. 
 
 There are three ways that custom actions can be used in Chatterbox; to swap between the different implementations set [`CHATTERBOX_ACTION_MODE`](reference-configuration?id=chatterbox_action_mode) to one of the following (the default is option `1`):
-- `0` Pass ChatterScript actions as a raw string to a function, defined by `CHATTERBOX_ACTION_FUNCTION`
 - `1` Treat actions as expressions
 - `2` Treat actions as they were in version 1 (Python-esque function calls)
 
-Mode `0` is provided for compatibility with YarnScript. This mode instructs a chatter to actions as a strings into the game engine for manual interpretation. Chatterbox's implementation is that the function defined by `CHATTERBOX_ACTION_FUNCTION` is called when Chatterbox encounters an action, the first argument (`argument0`) for the function call being the text inside the action as a string. The intention is that you'd then parse that text and execute behaviour accordingly but... this sucks, it's a ton of work to actually do this, let's move on.
-
 Mode `1` is the default Chatterbox behaviour:
 1. Every custom action is expected to use GML-like syntax: functions are executed using their name followed by a comma-separated list of arguments e.g. `<<CustomFunction("string", "string with spaces", 3.14, true)>>`
 2. Variables are referenced by using the standard dollar-prefixed token e.g. `<<TransmutateLead("Gold", $lead)>>`

docs/3.0/reference-configuration.md

@@ -24,9 +24,9 @@ Whether to allow scripts to be added as Chatterbox functions.
 
 ## `CHATTERBOX_FUNCTION_ARRAY_ARGUMENTS`
 
-_Typical value:_ `true`
+_Typical value:_ `false`
 
-Whether to execute callbacks with an array of arguments. Setting this to `false` will execute callbacks with individual arguments.
+Whether to execute callbacks with an array of arguments. Setting this to `false` will execute callbacks with individual arguments, setting this to `true` will execute callbacks with a single array that contains the arguments.
 
  
 
@@ -108,16 +108,11 @@ Whether nodes without an explicit `<<stop>>` or `<<hopback>>` instruct at the en
 
 _Typical value:_ `1`
 
-`CHATTERBOX_ACTION_MODE` should be either 0, 1, or 2:
+`CHATTERBOX_ACTION_MODE` should be either 1 or 2:
 
-- `0` Pass ChatterScript actions as a raw string to a function, defined by `CHATTERBOX_ACTION_FUNCTION`
 - `1` Treat actions as expressions
 - `2` Treat actions as they were in version 1 (Python-esque function calls)
 
-### `CHATTERBOX_ACTION_MODE` = 0
-
-This is the officially recommended behaviour. The full contents of the direction (everything between `<<` and `>>`) are passed as a string to a function for parsing and execution by the developer (you). I think this behaviour is stupid but I've included it here because technically that is what the ChatterScript specification says. You can set the function that receives the direction string by setting `CHATTERBOX_ACTION_FUNCTION`. Exactly what syntax you use for actions is therefore completely up to you.
-
 ### `CHATTERBOX_ACTION_MODE` = 1
 
 Chatterbox will treat actions as expressions to be executed in a similar manner to in-line expressions. This is covenient if you want to treat actions as little snippets of code that Chatterbox can run. Syntax for actions becomes the same as in-line expressions, which is broadly similar to "standard" GML syntax. Functions that you wish to execute must be added by calling ChatterboxAddFunction(). An example would be: `<<giveItem("amulet", 1)>>`
@@ -128,14 +123,6 @@ Chatterbox will treat actions as expressions with a greatly simplified syntax. T
 
 &nbsp;
 
-## `CHATTERBOX_DIRECTION_FUNCTION`
-
-_Typical value:_ `ExampleActionFunction`
-
-Function to use to handle actions. This only applies in mode `0` (see below).
-
-&nbsp;
-
 ## `CHATTERBOX_END_OF_NODE_HOPBACK`
 
 _Typical value:_ `true`
@@ -208,20 +195,6 @@ Directory inside Included Files that holds all external ChatterScript files. Use
 
 &nbsp;
 
-## `CHATTERBOX_DECLARE_ON_COMPILE`
-
-_Typical value:_ `true`
-
-Whether to declare variables when Chatterbox script is compiled. Set to `false` for legacy (2.1 and earlier) behaviour.
-
-&nbsp;
-
-## `CHATTERBOX_LEGACY_WEIRD_OPERATOR_PRECEDENCE`
-
-_Typical value:_ `false`
-
-&nbsp;
-
 ## `CHATTERBOX_INDENT_TAB_SIZE`
 
 _Typical value:_ `4`