From 330a7460271817967d19eb6c9a2b500a9b8654a7 Mon Sep 17 00:00:00 2001 From: jesopo Date: Wed, 3 Jul 2019 11:26:20 +0100 Subject: [PATCH] Add docs/help/channels.md --- docs/help/channels.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 docs/help/channels.md diff --git a/docs/help/channels.md b/docs/help/channels.md new file mode 100644 index 00000000..66eeb78b --- /dev/null +++ b/docs/help/channels.md @@ -0,0 +1,21 @@ +## Channels + +BitBot responds to `/invite`s sent to him. If you invite him to a channel with a password (`+k` channel mode) he will record the key and use it in the future. If you change the key and he sees you doing it, he'll update his records to use the new key in future. + +### +k channels with no /invite bypass + +Some networks do not allow `/invite`d users to bypass channel passwords - thus BitBot can't join without a key and then record the key. There's two things you can do to fix this. + +`/msg <bot> config channel:#channel key ` +- or - +`/msg <bot> raw JOIN #channel :key here` + +After using either of these to get BitBot initially in to a channel, he will go about recording and updating the channel's key as described above. + +### Disabling join-on-invite +`/msg <bot> config server accept-invites off` + +### Perform commands on join +From the channel you wish him to perform commands for, do: + +`!cperform add PRIVMSG {CHAN} :hello, I'm {NICK}`