Releases: JujuAdams/Chatterbox
Releases · JujuAdams/Chatterbox
3.0.0 (Beta)
CHATTERBOX_FUNCTION_ARRAY_ARGUMENTS
now defaults tofalse
. Please be careful to adjust this config macro if you are updating from version 2.x of Chatterbox- Removes legacy macro
CHATTERBOX_DECLARE_ON_COMPILE
. It is now hardcoded totrue
- Removes legacy macro
CHATTERBOX_LEGACY_WEIRD_OPERATOR_PRECEDENCE
. It is now hardcoded tofalse
- Use of
CHATTERBOX_ACTION_MODE = 0
is now discouraged and no longer documented - Removes support for returning
"<<wait>>"
,"<<forcewait>>"
, and"<<fastforward>>"
from ChatterScript action functions to control chatterbox flow. Instead please callChatterboxWait()
orChatterboxFastForward()
from your action functions
2.18.0
- Adds support for named
<<wait>>
actions e.g.<<wait timer>>
.ChatterboxContinue()
now takes an optional name argument. A chatterbox will only continue if the name of the wait action is the same as the name passed into the continue function. This is useful to help control chatterboxes asynchronously - In aid of the above,
ChatterboxContinue()
can now take the string"all"
as an argument. This will instruct all extant chatterboxes to continue which is useful to "broadcast" asynchronous events to a chatterbox without having a specific reference - Adds
<<jumpback>>
to jump back to the top of the previous node. This doesn't use a stack so calling this multiple times will loop between two nodes. ChatterboxVariableDefault()
is now friendlier to use and won't shout at you unless you try to redefine a variable with a different value to before- Adds
ChatterboxGetPrevious()
to return the name of the previously visited node - Adds an instruction type parameter to the callback set up by
ChatterboxNodeChangeCallback()
. This allows you to differentiate betweenjump
,hop
, andhopback
node changes. When setting up an autosave system you will likely want to save only on ajump
type node change
2.17.0
- Adds support for named
<<wait>>
actions e.g.<<wait timer>>
.ChatterboxContinue()
now takes an optional name argument. A chatterbox will only continue if the name of the wait action is the same as the name passed into the continue function. This is useful to help control chatterboxes asynchronously - In aid of the above,
ChatterboxContinue()
can now take the string"all"
as an argument. This will instruct all extant chatterboxes to continue which is useful to "broadcast" asynchronous events to a chatterbox without having a specific reference ChatterboxVariableDefault()
is now friendlier to use and won't shout at you unless you try to redefine a variable with a different value to before- Adds
ChatterboxGetPrevious()
to return the name of the previously visited node - Adds an instruction type parameter to the callback set up by
ChatterboxNodeChangeCallback()
. This allows you to differentiate betweenjump
,hop
, andhopback
node changes. When setting up an autosave system you will likely want to save only on ajump
type node change
2.16.0
2.15.1
2.15.0
- Adds
ChatterboxGetOptionSpeaker()
,ChatterboxGetOptionSpeakerData()
, andChatterboxGetOptionSpeech()
- Adds
ChatterboxVariableSetCallback()
. This allows you to specify a function to call when a Chatterbox value is set - Adds separate script for Chatterbox constants
- Evacuates global namespace so no more Chatterbox variables clogging up your global variable debug view
2.14.0
- Adds
<<random option>>
action. See documentation for more information.