mirror of
https://github.com/Mikaela/Limnoria.git
synced 2025-01-11 20:52:42 +01:00
Updated, thanks again Grantbow.
This commit is contained in:
parent
049ff3d0cb
commit
98c0512eec
@ -107,24 +107,25 @@ Supybot wants to send a message that's longer than that. What it
|
|||||||
does, then, is break it into "chunks" and send the first one,
|
does, then, is break it into "chunks" and send the first one,
|
||||||
following it with "(X more messages)" where X is how many more chunks
|
following it with "(X more messages)" where X is how many more chunks
|
||||||
there are. To get to these chunks, use the more command. One way to
|
there are. To get to these chunks, use the more command. One way to
|
||||||
try is to look at the listing of configuration groups for the bot
|
try is to look at the default value of
|
||||||
(more on this in the CONFIGURATION document) by giving the command
|
supybot.replies.genericNoCapability -- it's so long that it'll
|
||||||
"config list supybot". Last I checked, it'll overflow into a second
|
stretch across two messages.
|
||||||
chunk. When you invoke this command, you should see output like:
|
|
||||||
|
|
||||||
<supybot> nick, ident, user, server, password, channels, prefixChars,
|
<jemfinch|lambda> $config default
|
||||||
defaultCapabilities, defaultAllow, defaultIgnore,
|
supybot.replies.genericNoCapability
|
||||||
humanTimestampFormat, externalIP, bracketSyntax, pipeSyntax,
|
<lambdaman> jemfinch|lambda: You're missing some capability
|
||||||
followIdentificationThroughNickChanges, alwaysJoinOnInvite,
|
you need. This could be because you actually
|
||||||
showSimpleSyntax, maxHistoryLength, nickmods, throttleTime,
|
possess the anti-capability for the capability
|
||||||
snarfThrottle, threadAllCommands, pingServer, pingInterval,
|
that's required of you, or because the channel
|
||||||
upkeepInterval, flush, (1 more message)
|
provides that anti-capability by default, or
|
||||||
|
because the global capabilities include that
|
||||||
Now, to see the rest of the output, simply give the command "more",
|
anti-capability. Or, it could be because the
|
||||||
and it will show you the rest:
|
channel or the global defaultAllow is set to
|
||||||
|
False, meaning (1 more message)
|
||||||
<jemfinch> more
|
<jemfinch|lambda> $more
|
||||||
<supybot> httpPeekSize, and defaultSocketTimeout
|
<lambdaman> jemfinch|lambda: that no commands are allowed
|
||||||
|
unless explicitly in your capabilities. Either
|
||||||
|
way, you can't do what you want to do.
|
||||||
|
|
||||||
You should now have a solid foundation for using Supybot. Be sure to
|
You should now have a solid foundation for using Supybot. Be sure to
|
||||||
check the help that is built-in to the bot itself if you have any
|
check the help that is built-in to the bot itself if you have any
|
||||||
|
Loading…
Reference in New Issue
Block a user