mirror of
				https://github.com/Mikaela/Limnoria.git
				synced 2025-10-31 15:47:25 +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, | ||||
| 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 | ||||
| try is to look at the listing of configuration groups for the bot | ||||
| (more on this in the CONFIGURATION document) by giving the command | ||||
| "config list supybot".  Last I checked, it'll overflow into a second | ||||
| chunk.  When you invoke this command, you should see output like: | ||||
| try is to look at the default value of | ||||
| supybot.replies.genericNoCapability -- it's so long that it'll | ||||
| stretch across two messages. | ||||
| 
 | ||||
| <supybot> nick, ident, user, server, password, channels, prefixChars, | ||||
|           defaultCapabilities, defaultAllow, defaultIgnore, | ||||
|           humanTimestampFormat, externalIP, bracketSyntax, pipeSyntax, | ||||
|           followIdentificationThroughNickChanges, alwaysJoinOnInvite, | ||||
|           showSimpleSyntax, maxHistoryLength, nickmods, throttleTime, | ||||
|           snarfThrottle, threadAllCommands, pingServer, pingInterval, | ||||
|           upkeepInterval, flush, (1 more message) | ||||
| 
 | ||||
| Now, to see the rest of the output, simply give the command "more", | ||||
| and it will show you the rest: | ||||
| 
 | ||||
| <jemfinch> more | ||||
| <supybot> httpPeekSize, and defaultSocketTimeout | ||||
|         <jemfinch|lambda> $config default | ||||
| 	                  supybot.replies.genericNoCapability | ||||
| 	<lambdaman> jemfinch|lambda: You're missing some capability | ||||
| 	            you need. This could be because you actually | ||||
| 	            possess the anti-capability for the capability | ||||
| 	            that's required of you, or because the channel | ||||
| 	            provides that anti-capability by default, or | ||||
| 	            because the global capabilities include that | ||||
| 	            anti-capability. Or, it could be because the | ||||
| 	            channel or the global defaultAllow is set to | ||||
| 	            False, meaning (1 more message) | ||||
| 	<jemfinch|lambda> $more | ||||
| 	<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 | ||||
| check the help that is built-in to the bot itself if you have any | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user
	 Jeremy Fincher
						Jeremy Fincher