diff options
| author | 2019-07-03 11:29:39 +0100 | |
|---|---|---|
| committer | 2019-07-03 11:29:39 +0100 | |
| commit | 655f00ce8418b45208ac1e369db42e06f790a54e (patch) | |
| tree | 1696a44eaddbfbdc2f42bd9409a01c4f7289dc34 /docs | |
| parent | extra newline between '>' lines so they don't get joined together (diff) | |
| signature | ||
< is important!
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/help/channels.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/help/channels.md b/docs/help/channels.md index 4b632bea..8725bd9b 100644 --- a/docs/help/channels.md +++ b/docs/help/channels.md @@ -6,11 +6,11 @@ BitBot responds to `/invite`s sent to him. If you invite him to a channel with a 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 <password here> +> /msg <bot> config channel:#channel key <password here> or -> /msg <bot> raw JOIN #channel :key here +> /msg <bot> raw JOIN #channel :<password 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. |
