···19192020Minimal needed is an env var called `TOKEN` that contains the bot's token.
21212222-Cogs may have additional options, these variables **should** be prefix with the
2323-cog's name
2424-2525-ex: Cog `Math` may have `Math.TEMP_UNIT=fahrenheit`.
2626-2722## Cog Docs
28232924### [Markov](src/bingus/cogs/markov.py)
···3833- `/markov`: Make bingus try and reply to a prompt passed, use this to bypass the 80% change that bingus
3934 usually has to reply
4035- `/scan_history`*: Scan the history of the current channel and add it to the chain. Since Bingus only learns
4141- from *new\* messages while he's active, you may need to do this when restarting him. This command can take a while depending on the number of messages.
3636+ from*new\* messages while he's active, you may need to do this when restarting him. This command can take a while depending on the number of messages.
4237- `/dump_chain`\*: Dumps the entire underlying markov chain as a JSON file and sends it
4338- `/load_chain`\*: Loads a markov chain JSON (as generated by `/dump_chain`) additively
4439- `/weights`: Dump the weights of the specified token to other tokens
45404641#### Markov Config
47424848-- `Markov.REPLY_CHANNELS`: A _comma-delimited_ list of channel IDs that the bot should have
4343+- `REPLY_CHANNELS`: A _comma-delimited_ list of channel IDs that the bot should have
4944 have a chance to reply to messages in. The bot still learns from all channels in realtime, but
5045 these channels it'll have an 80% of replying to any message
51465252-- `Markov.BRAIN_FILE`: Path to file where the chain will be persisted. This file will automatically be created
4747+- `BRAIN_FILE`: Path to file where the chain will be persisted. This file will automatically be created
5348 if it doesn't exist already. The file itself is msgpack compressed with brotli,
5449 so it's recommended to give it a `msgpackz` extension. By default it will be set to `$PWD/brain.msgpackz`
5550···89849085#### Cog Config
91869292-For simplicity we'll just use env vars for config. Prefix any env vars your cog will
9393-read with the cog's name and a `.` (example: `Markov` cog can have a var called `Markov.REPLY_CHANNELS`).
8787+For simplicity we'll just use env vars for config.
94889589Try to documents these options within this README file under the [The individual cogs docs](#cog-docs).
9690Create a third-level heading with your cog's name, and a link to its source code.