Whether or not to accept commands whose origin channel is the subchannel of an event.
Whether or not he terminal has a bright background.
Enables callgrind dumps for profiling.
Whether or not to add colours to outgoing messages.
Terminal output colour setting.
Non-version Colours version defaults to false.
Path to configuration directory.
Main configuration file.
Whether to eagerly and exhaustively WHOIS all participants in home channels, or to do a just-in-time lookup when needed.
Whether or not to display a connection summary on program exit.
Whether or not the bot should output text using extended ANSI sequences.
Whether or not to add extended colours to outgoing messages.
Whether or not to explicitly set stdout to flush after writing a linebreak to it.
Whether or not to force connecting, skipping some sanity checks.
Whether or not to be "headless", disabling all terminal output.
Whether or not to hide outgoing messages, not printing them to screen.
Whether to print addresses as IPs or as hostnames (where applicable).
Enables observer mode, which makes the bot ignore all commands (but process other events).
Whether or not hostmasks should be used instead of accounts to authenticate users.
Character(s) that prefix a bot chat command.
Re-executes the program instead of reconnecting hot.
Path to resource directory.
Whether or not we should save configuration changes to file on exit.
Whether or not *all* outgoing messages should be echoed to the terminal.
Aggregate struct containing runtime bot setting variables.
Kept inside one struct, they're nicely gathered and easy to pass around. Some defaults are hardcoded here.