/[cvs]/eggdrop1.9/help/cmds1.help
ViewVC logotype

Contents of /eggdrop1.9/help/cmds1.help

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.13 - (show annotations) (download)
Wed Dec 17 08:43:19 2003 UTC (15 years, 5 months ago) by wcc
Branch: MAIN
CVS Tags: HEAD
Changes since 1.12: +0 -0 lines
FILE REMOVED
* Bye bye notes.mod.

1 %{help=+bot}%{+t}
2 ### %b+bot%b <bot> <address:botport#[/userport#]> [hostmask]
3 Creates a user record for a new bot with the nickname given.
4 The hostmask table will have one entry, either that specified,
5 a host from a current user with the given nick, or "none",
6 and the bot (b) flag will be set for the user. The internet
7 address field of the user will also be set to the address given.
8 You can use this command and %b'chpass'%b to completely set up a
9 record for a future bot, or you can let the two bots negotiate
10 a password for themselves the first time they link. If the bot
11 has a seperate port for bots and users they should be seperated
12 with a slash (/).
13 %{help=+host}
14 ### %b+host%b <hostmask>
15 Allows you to add a host for yourself.
16 %{help=+host}%{+m|m}
17 ### %b+host%b <nickname> <hostmask>
18 Adds a hostmask to a user's record on the bot. The hostmasks
19 are where the bot will identify that user from. Usually you
20 will not need to use this command since a user can add hostmasks
21 to her own record via the %b/MSG IDENT%b command, but it's here if
22 you need it.
23 %{help=+ignore}%{+m}
24 ### %b+ignore%b <hostmask> [%%<XdXhXm>] [comment]
25 Adds a hostmask to the ignore list, with your nickname and optional
26 comment and ignoretime. This command can be used to either ignore
27 users on irc, or to ignore incoming telnet connections. Ignoretime
28 has to be expressed in days, hours and/or minutes.
29
30 See also: -ignore, ignores
31 %{help=+user}%{+m}
32 ### %b+user%b <nickname> <hostmask>
33 Creates a new user record for the nickname given, with one entry
34 in the hostmask table. The new user record will have no flags
35 (i.e. not be a master, op, friend, etc) and no password.
36 %{help=-bot}%{+t}
37 ### %b-bot%b <bot>
38 Exactly the same as %b'-user'%b, but is included for convenience.
39 It erases a user record.
40
41 See also: +bot, +user, -user
42 %{help=-host}
43 ### %b-host%b <hostmask>
44 Allows you to remove a host for yourself.
45 %{+m|m}
46 ### %b-host%b <nickname> <hostmask>
47 Removes a hostmask from another user's record on the bot.
48 See also: +host
49 %{-}
50 %{help=-ignore}%{+m}
51 ### %b-ignore%b <hostmask OR number>
52 Removes the ignore from the list of ignores stored on the bot --
53 You may also reference the ignore by the number shown in '.ignores'.
54
55 See also: +ignore, ignores
56 %{help=-user}%{+m}
57 ### %b-user%b <nickname>
58 Erases the user record for the nickname given.
59
60 See also: +user, +bot, -bot
61 %{help=away}
62 ### %baway%b [away-message]
63 Marks you as "away" on the party line. Your away message will
64 show up in the %b'.who'%b list, and will be displayed to anyone who
65 tries to send you a note. Your notes will be stored, and then
66 displayed to you as soon as you are no longer away. Saying
67 something on the party line will automatically remove your "away"
68 status, or you can type %b'.back'%b or %b'.away'%b by itself.
69 %{help=back}
70 ### %bback%b
71 This marks you un-away on the party line.
72 %{help=binds}%{+m}
73 ### %bbinds%b [type/match]
74 Shows the Tcl bindings in effect, in a list similar to this:
75 Command bindings:
76 TYPE FLGS COMMAND HITS BINDING (TCL)
77 msg -|- rose 0 msg_rose
78 msg -|- go 0 msg_go
79 dcc m|- bind 0 cmd_bind
80 pub -|- gross 0 pub_gross
81 The fields should be self-explanatory, except for HITS, which
82 records the number of times that binding has been called.
83 If not, go read the file %b'tcl-commands.doc'%b for help on the
84 Tcl bind command. Note that the builtin commands are now shown.
85 You may also specify a type of binding to show (ie,
86 %b'.binds msg'%b) or you can specify a wild card match (ie,
87 %b'.binds *seen*'%b) if you want to narrow the field a bit.
88 The wild card matches will match against the TYPE, COMMAND and
89 BINDING fields.
90 ### %bbinds%b [type] %ball%b
91 Displays all the Tcl bindings of every type (or the specified
92 type), including the bindings for built in commands such as:
93 msg - op *msg:op
94 %{help=boot}%{+t}
95 ### %bboot%b <nickname> [reason]
96 ### %bboot%b <nick@bot> [reason]
97 Will kick a user off the party line, and display the reason if you
98 give one. You can attempt to boot someone from another bot (in a
99 botnet), though it may be rejected if that bot does not allow remote
100 boots. You can not boot the bot's owner.
101 %{help=botattr}%{+t}
102 ### %bbotattr%b <nickname> [attributes] [channel]
103 Lets you view and change the attributes (flags) field for a bot.
104 Example:
105 Sets Fred1 +share and -hub.
106 .botattr Fred1 +s-h
107
108 Whether or not you change any flags, it will show you the bot's
109 attributes afterwards.
110 To get a list of the flags possible, do %b'help whois'%b.
111 %bNOTE:%b This command is NOT used to replace .chattr,
112 it modifies botflags such as +s, +h, +a, +u... bot specific
113 flags only.
114 %bNOTE:%b You can't use this command on bots which are directly
115 linked to your bot at the current moment.
116
117 See also: whois, chattr
118 %{help=botinfo}
119 ### %bbotinfo%b
120 Requests information from every bot currently in the botnet.
121 Each bot should eventually send you one line listing its version
122 and other information.
123 %{help=bots}
124 ### %bbots%b
125 Shows the list of bots currently in the botnet. Example:
126 Bots: cEvin, ruthie, Killa1
127 There is no indication of which bots are directly connected to
128 this one. Use %b'who'%b %{+t}or %b'bottree'%b%{-} for that information.
129 %{help=bottree}
130 ### %b[v]bottree%b
131 Shows a tree-format diagram of the bots currently in the botnet.
132 It's just a nice way to get a feel for how the bots are connected
133 physically. if 2 bots are sharing, a + will be indicated, or a ?
134 if nothing is known.
135 Use vbottree if you want to know bot versions as well.
136
137 See also: bots, botinfo
138 %{help=chaddr}%{+t}
139 ### %bchaddr %b<bot> <address:botport#/userport#>
140 Changes the internet address for a bot. This is the address
141 your bot will try to telnet to in order to create a connection
142 and link up. If the bot has a seperate port for bots and users
143 they should be seperated with a slash (/).
144
145 See also: link, +bot
146 %{help=chat}
147 ### %bchat off%b
148 ### %bchat <channel # or name>%b
149 Changes your channel on the dcc chat connection. when you first
150 connect to the bot, it places you on channel 0 (the party line).
151 You can move to another channel where basically nobody can see
152 you (except anyone else who decides to join that channel). Valid
153 channel numbers are 1 thru 99999.
154
155 Some channels may have assigned names if the assoc module is
156 loaded. For those, you can specify the channel by name instead
157 of number if you wish.
158
159 %b'chat off'%b removes you from any channel at all. You can still
160 use normal bot commands and see the console, but you can't talk
161 to anyone except via %b'.note'%b
162
163 %b'chat on'%b returns you to the party line (channel 0) if you were
164 elsewhere.
165
166 ### %bchat%b <*channel# or name>
167 Same as above, but for channels available only to the bot you
168 are on.
169 %{help=chattr}%{+m|m}
170 ### %bchattr%b <nickname> [attributes] [channel]
171 Lets you view and change the attributes (flags) field for a user.
172 For example, to give Lamer the p and f flags:
173 .chattr Lamer +pf
174 Or to remove Denali from the global op list:
175 .chattr Denali -o
176 You may also do any combination of the above:
177 .chattr Fred1 -m+xj-o
178
179 You can also change the flags for Usagi on a specific channel by
180 supplying the channel after the attributes:
181 .chattr Usagi -m+dk-o #blah
182
183 Changing global and channel specific flags within the same command
184 line is now possible! Example:
185 .chattr Bill f|o #lamer (global +f, +o #lamer)
186
187 Whether or not you change any flags, it will show you the user's
188 attributes afterwards.
189
190 To get a list of the flags possible, do %b'help whois'%b.
191
192 %bNOTES:%b
193 Only the owner may add or remove the 'n' (owner), 'm' (master)
194 and 't' (botnet master) flags.
195 It is pointless to -n a permanant owner. You must remove the
196 permanant owner in the config file.
197 This command can no longer be used to change bot flags, they
198 are a seprated entity, changeable with the %b'.botattr'%b command.
199 See also: whois
200 %{help=chhandle}%{+t}
201 ### %bchhandle%b <oldhandle> <newhandle>
202 Changes the handle of a user record. For example, to
203 change the handle of user 'gavroche' to 'jamie', you would
204 type: 'chhandle gavroche jamie'
205 %{help=chnick}%{+t}
206 ### %bchnick%b
207 Please note, that this command has been superceeded by
208 'chhandle'. If you still want to use 'chnick', load compat.tcl
209 into your bot.
210 %{help=chpass}%{+t}
211 ### %bchpass%b <handle> [newpassword]
212 Changes a user's password on the bot. If you leave off the new
213 password, the user effectively no longer has a password set. A
214 password is needed to get ops, join the party line, and other
215 things (but only required if one is set).
216
217 %bNOTE:%b In previous versions, setting a password to "nopass" would
218 clear a user's password -- with encrypted passwords, this no
219 longer works!
220 %{help=comment}%{+m}
221 ### %bcomment%b <user> <comment...>
222 Creates or changes the comment field for a user. The comment field
223 can only be seen via 'whois' or 'match'. Non-masters cannot see the
224 comment field.
225 %{help=console}%{+to|o}
226 ### %bconsole%b [channel] [modes]
227 Changes your console level, so that you will see only those types
228 of console messages that you want to. Your current console channel
229 is the channel (that the bot is on) which you can view from the
230 party line, and which channel-specific commands (like 'say' and
231 'op') take affect on. valid levels are:
232 m display private msgs/ctcps to the bot
233 p display public talk and ctcps on the channel
234 k display kicks/bans/mode changes on the channel
235 j display joins/parts/nick changes/signoffs/etc on the channel
236 b display bot links/unlinks/userfile-sharing
237 s display server messages and connect/disconnects
238 w display msgs between IRCops (wallops)
239 %{+m|m}
240 channel master only:
241 c display user commands (dcc and msg)
242 o display other bot notices [HIGHLY RECOMMENDED]
243 %{+m}
244 master only:
245 x display file transfers and file-area commands
246 d display debug messages that only coders would care about
247 %{+n}
248 owner only:
249 r display all raw text from the server (if enabled)
250 v display raw text SENT to the server (if enabled)
251 -- There are also 8 user-defined console modes '1' thru '8' --
252 %{+o|o}
253 The mode can also be a modifier like '+p' or '-jk' or '+mp-b'. If
254 you omit the channel and modes, it will show your current console
255 channel and setting.
256 %{+m|m}
257 ### %bconsole%b <user> [channel] [modes]
258 Is used to set the console level of another user. This can even
259 be used on users who normally would not be able to set their own
260 console mode.
261 %{help=dccstat}%{+m}
262 ### %bdccstat%b
263 displays a table-format list of all the "dcc" connections the bot
264 is handling. "dcc" means "direct client-to-client communication"
265 and eggdrop expands this to cover every open socket. so any type
266 of network connection to the bot is considered a "dcc" connection.
267 the headings of the table are:
268 SOCK the socket of this connection (always unique)
269 ADDR the IP-number of the host the connection is to, if
270 applicable
271 PORT the port number being used for communication
272 NICK the nickname of the user or bot, if it's a user or bot
273 HOST sometimes, the hostname corresponding to the IP address
274 TYPE the type of dcc connection (see below)
275
276 the types of connection currently possible are as follows (but
277 more are being added literally all the time):
278 chat user in dcc-chat command mode
279 pass user entering dcc chat (being asked for her password)
280 send raw data connection: user sending a file
281 get raw data connection: sending a file to a user
282 getp pending get (waiting for the user to acknowledge)
283 lstn telnet listening port (in place of a hostname, it will
284 show the proc to call, or mask of acceptable nicks)
285 t-in incoming telnet user (being asked for his nickname)
286 file user in dcc-chat file area
287 bot bot linked in (aka botnet connection)
288 bot* pending bot link (waiting for acknowledgement)
289 rela user in relay connection to another bot
290 >rly bot being relay'd to (one for each "rela")
291 conn pending telnet connection (chat, relay, bot-link, etc)
292 new new user via telnet, entering a handle
293 newp new user via telnet, entering a password
294
295 in addition, 'chat' and 'bot' have flags listed for each con-
296 nection. capital letters mean the flag is on, and lowercase
297 letters mean the flag is off. for 'chat', the flags are:
298 C in file area, but allowed to return to party line
299 P party line access only (no +o access)
300 T telnet connection (instead of dcc chat)
301 E echo is on
302 P paging is on
303 for 'bot', the flags are:
304 P ping sent, waiting for reply
305 U user-file sharing is active
306 C this bot initiated the connection
307 O user-file offered, waiting for reply
308 S in the process of sending the user-file
309 G in the process of getting the user-file
310 W warned this bot to stop hubbing
311 L leafed bot (not allowed to hub)
312 I bot is currently in the 'linking' stage
313 A bot is being agressively shared with
314 for 'chat' users, the party-line channel is also listed.
315 %{help=echo}
316 ### %becho%b <on/off>
317 sets whether you want your messages echoed back to you. if it's
318 on, then when you say something on the party line, it will be
319 displayed to you just like everyone else will see it. if it's off,
320 then that won't happen.
321 %{help=die}%{+n}
322 ### %bdie%b [reason]
323 kills the bot. the bot goes offline immediately, logging who gave
324 the 'die' command. you shouldn't have to use this too often. if you
325 specify a reason, it's logged, otherwise the reason is "authorized by
326 <nickname>".

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23