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

Contents of /eggdrop1.9/help/cmds2.help

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


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

1 %{help=fixcodes}
2 ### %bfixcodes%b
3 use this in those situations where the bot gets mixed up about your
4 type of connect, eg: when you /ctcp chat the bot & it thinks you're
5 telnetting, and you're actually using dcc, it effectively switches
6 telnet on and off.
7 %{help=ignores}%{+m}
8 ### %bignores%b [wildcard]
9 lists the hostmasks that the bot is currently discarding msgs,
10 etc from. the ignores are numbered, so they can be easily
11 removed with %b'-ignore'%b by number. a permanent ignore looks
12 like this:
13 [ 1] *!onaji@* (perm)
14 Xerxes: spamming me
15 Started 18:38
16 this kind of ignore can only be stopped by using %b'-ignore'%b.
17 Xerxes is the one who added it, and his comment is "spamming
18 me". he added it at about 18:38 today. a temporary ignore
19 looks like this:
20 [ 2] *!*@shellx.best.com (expires at 19:59)
21 MyBot: msg/notice flood
22 Started 18:59
23 that means the ignore was made automatically by the bot at
24 18:59, because someone flooded it. it can be removed with
25 %b'-ignore'%b, or it will expire an hour after it started (this
26 is set in %b'ignore-time'%b).
27
28 if you use %b'ignores <wildcard>'%b it will list all the ignores
29 that match against your wildcard.
30
31 see also: +ignore, -ignore, set ignore-time
32 %{help=link}%{+t}
33 ### %blink%b [some-bot] <new-bot>
34 tries to link in a new bot. if you use the form
35 .link newbot
36 then your bot must have a record for the new bot (see %b'.+bot'%b).
37 you can either set a password on each end or they will negotiate
38 one the first time they link. if you use the form
39 .link somebot newbot
40 then the request will be sent to "somebot" for it to link to
41 "newbot".
42 %{help=loadmod}%{+n}
43 ### %bloadmod%b <module>
44 Loads a module.
45 %{help=match}%{+o|o}
46 ### %bmatch%b <attr> [channel] [[start] limit]
47 shows you user records with the attributes requested:
48 <attr> is of the form: <+/-><global>[&/|<channel>[&/|<bot>]]
49 specifying & as the speperator, will cause AND style matching,
50 | will cause OR style matching, channel flags are match vs
51 the specified channel (or your console channel), and bot
52 is match vs the sepreate bot flags.
53 some examples:
54 .match +o will match any GLOBAL +o's
55 .match -o&+o will match anyone without a global +o AND
56 with a channel +o on your console channel
57 .match +f|+f will match anyone with a global +f or a
58 channel +f on your console channel
59 .match |f #fred will match anyone with +f on channel #fred
60 ### %bmatch%b <wildcard-string> [[start] limit]
61 shows you user records where the nickname or any of the hostmasks
62 match the wildcard string shown.
63
64 the default limit is 20, meaning that if more than 20 user records
65 match your requirements, only the first 20 will be shown. you can
66 change this limit by specifying one on the command line, though.
67 if you include a limit, you may also include a starting place (the
68 default is 1). for example, to list the first 15 users who have
69 hostmasks from clemson.edu:
70 .match *clemson.edu 15
71 to get the next 10 (if there are more than 15), you ask to list
72 numbers 16 thru 25:
73 .match *clemson.edu 16 25
74 %{help=me}
75 ### %bme%b <text>
76 performs an action on the party line.
77 %{help=module}%{+n}
78 ### %bmodule%b [modulename]
79 Reports the names of currently loaded modules, including
80 dependancies & status report, you can get info only on a
81 specific module by specifying it.
82 %{help=modules}%{+n}
83 ### %bmodules%b [botname]
84 requests a listing of the modules loaded on the remote bot or your
85 bot if no botname is specified.
86 %{help=motd}
87 ### %bmotd%b [botname]
88 will redisplay the party-line message of the day, which was
89 shown when you first joined. If the name of a remote bot is
90 given as parameter, the respective motd will be displyed.
91 %{help=newpass}
92 ### %bnewpass%b <password>
93 changes your password on the bot, just like the /msg command
94 'pass', except you don't need to type your old password.
95 %{help=handle}
96 ### %bhandle%b <new-handle>
97 changes your handle on the bot. That's the handle(nickname) that the
98 bot will know you as forever and ever, and what you have to use when
99 telnetting in or IDENT'ing yourself, so remember it.
100 %{help=nick}
101 ### %bnick%b
102 Please note, that this command has been superceeded by
103 'handle'. If you still want to use 'nick', load compat.tcl
104 into your bot.
105 %{help=note}
106 ### %bnote%b <nickname[@bot]> <message>
107 sends a private note to a user on the party line. if that user
108 is currently on the party line, and not marked as away, she will
109 receive the message immediately. otherwise it may be stored
110 and displayed the next time that user joins the party line. if
111 you join the channel, and have notes stored for you on the bot,
112 it will tell you. to send a note to someone on a different bot,
113 use "nick@bot" for the nickname.
114
115 see also: whom, notes
116 %{help=page}
117 ### %bpage%b <# or off>
118 allows you to slow down the number of lines the bot sends to you
119 at once while you're in chat mode. with this on, any commands
120 that send greater than the specified number of lines will stop
121 when the number is reached, and wait for you to type another
122 command (or press enter) to continue. if you have to many
123 lines waiting to be seen you may be booted off the bot.
124 %{help=quit}
125 ### %bquit%b [comment]
126 removes you from the party line and disconnects your dcc chat
127 session with the bot. if you specify a comment, it will be
128 displayed to other users as you leave.
129 %{help=rehash}%{+m}
130 ### %brehash%b
131 reloads the config file for the bot, which resets all the %b'set'%b
132 variables and reloads any TCL scripts your config loads. it
133 also saves and reloads the user file from disk, just to give
134 your disk a little extra wear.
135
136 see also: save, reload, restart
137 %{help=rehelp}%{+n}
138 ### %brehelp%b
139 This command gets the bot to recheck all it's help files for new
140 commands that have been added.
141 %{help=relay}%{+o}
142 ### %brelay%b <botname>
143 will relay you via telnet to another bot that your bot knows of,
144 whether or not they are currently connected. your dcc-chat/telnet
145 connection to this bot will be relayed to the other bot until the
146 other bot drops your relay, or until you send "*bye*" on a line by
147 itself.
148
149 see also: bots
150 %{help=reload}%{+m|m}
151 ### %breload%b
152 reloads the user file of the bot, discarding any changes made
153 since the last %b'.save'%b or hourly user file save. sharebots
154 should probably not ever do this.
155
156 see also: rehash, save
157 %{help=traffic}%{+m|m}
158 ### %btraffic%b
159 shows total and dayly net traffic stats since last %b'.restart'%b.
160 stats groups are IRC, Botnet, Partyline, Transfer.mod and Misc.
161
162 see also: restart
163 %{help=whoami}
164 ### %bwhoami%b
165 Shows your handle and to what bot you are connected.
166 %{help=restart}%{+m}
167 ### %brestart%b
168 restarts the Tcl interpreter, wipes all timers and utimers, and
169 reloads the config file for the bot, which resets all the %b'set'%b
170 variables and reloads any TCL scripts your config loads. it
171 also saves and reloads the user file from disk, just to give
172 your disk a little extra wear. it's also the most risky command
173 to run, because it's never ever really worked properly.
174
175 see also: rehash, reload, save
176 %{help=save}%{+m|m}
177 ### %bsave%b
178 makes the bot write its entire user list to the disk. this is
179 useful if you think the bot is about to crash or something, since
180 the user file is only written to disk about once an hour.
181
182 see also: reload, rehash
183 %{help=backup}%{+m|m}
184 ### %bbackup%b
185 makes the bot write a backup of its entire user list to the disk.
186 if the channels module is loaded, this also write a backup of the
187 channels file.
188 this is useful if you feel the need to backup the user list and
189 the channels settings.
190
191 see also: reload, rehash
192 %{help=simul}%{+n}
193 ### %bsimul%b <nickname> <text>
194 if the user is on the party line, the bot will simulate them typing
195 the text you specify. example:
196 .simul dweeb .quit
197 makes it just as if "dweeb" typed ".quit". this command will not work
198 unless eggdrop has simul enabled in the config file. Please use this
199 command ethically.
200 %{help=su}
201 ### %bsu%b <user>
202 changes your username to that of another. If you
203 are an owner this does not require a password
204 otherwise, you must enter the password of <user>.
205
206 %b.quit%b returns you to your original user.
207 %{help=trace}
208 ### %btrace%b <bot>
209 sends out a trace signal to another bot. if that trace signal
210 returns (and it should!) you will get an output something like
211 this:
212 Trace result -> Valis:Stonewall:NoBoty:SomeBoty
213 it's a list of the bots between you and the destination bot.
214 it should also return the time in seconds it took for the
215 trace to occur.
216
217 see also: bots, bottree
218 %{help=unlink}%{+t}
219 ### %bunlink%b <bot>
220 disconnects the named bot from the botnet, assuming it was
221 connected in the first place. some bots (sharebots in
222 particular) might not allow you to unlink them.
223 ### %bunlink%b *
224 disconnects from all bots
225
226 see also: link, bots, bottree
227 %{help=unloadmod}%{+n}
228 ### %bunloadmod%b <module>
229 Unloads a module.
230 %{help=whom}
231 ### %bwhom%b [channel]
232 will display a table of the users currently on the joint party
233 line (formed when you have two or more bots linked together).
234 it will show each user's nickname, preceded by a "*" if they
235 are the owner of their bot, "+" if they are a master, "%%" if
236 they are a botnet master or "@" if they are an op. in other
237 columns it will show which bot the user is on, and his or her host.
238
239 if the user is away, the away message will be shown. likewise,
240 if they are idle, the idle time will be displayed.
241
242 if you are on a different channel than the party line (channel
243 0), then this will show the people on every bot who are on
244 your current channel. you can also optionally give the "channel"
245 option to list who is on a particular channel.
246
247 see also: who, bots, chat
248 %{help=who}
249 ### %bwho%b [bot]
250 lists people on this bot, or bots connected to this bot. the
251 first section is people on your current channel (the party
252 line, if you haven't changed channels) who are on the bot.
253 a '*' next to the nickname means that user is an owner; '+'
254 means they're a master; '@' means they're an op, '%%' means
255 they are a botnet master. the user's nickname, hostname, and
256 possibly an idle time and/or away message will be displayed:
257 %{+n}
258 Owners will also see the users dcc idx
259 %{-}
260 *Robey telnet: nowhere.com
261
262 the next section is bots directly linked to this one:
263 -> MagField (14 Oct 01:16) eggdrop v1.0j
264 (btw, if you're still using 1.0j, you need to upgrade ;)
265 the arrow indicates who initiated the connection -- the right
266 arrow means this bot connected to MagField. a left arrow
267 means they connected to us. a '+' next to the arrow indicates
268 that the bot is sharing userfiles with us. the connection
269 time (14 Oct 01:16) and bot version are also shown.
270 Nowadays it may also show the network the bot resides on.
271 %{+n}
272 Owners will also see the bots dcc idx
273 %{-}
274
275 the final section is a list of users on this bot who are not
276 on your channel. (this section may be omitted if everyone is
277 on the same channel as you.)
278
279 if you specify a bot's name, as in %b'.who valis'%b, the who request
280 will be sent to that bot, as long as that bot is on the botnet.
281 %{+m}
282
283 masters may also see "(con)" after a user's entry, this shows that
284 user's console modes (see the %b'.console'%b help page).
285
286 in the final section (users that aren't on this channel), masters
287 will see the actual channel other users are on. also, people in
288 the file system will be listed (as being in channel "files") --
289 a '+' next to the nickname here means the user has access to return
290 to the party line.
291 %{-}
292
293 see also: whom
294 %{help=whois}%{+o|o}
295 ### whois <nickname>
296 will show you the bot information about a user record. there are
297 five headings:
298 HANDLE the handle (nickname) of the user
299 PASS "yes" if she has a password set, "no" if not
300 NOTES number of notes stored waiting for the user
301 FLAGS the list of flags for this user (see below)
302 LAST the time or date that the user was last on the
303 channel
304
305 the valid flags under FLAGS are:
306 o global op (bot will op this user on any channel)
307 m master (user is a bot master)
308 n owner (user is the bot owner)
309 t botnet master (user is a botnet master)
310 x xfer (user has file-area access)
311 j janitor (user is a file-area master)
312 p party-line (user has party-line access)
313 u unshared (not sent to other share-bots)
314 b bot (user is another bot)
315 d global deop (user cannot get ops)
316 f global friend (user is not punished for doing bad things)
317 v global voice (user get +v automatically on +autovoice channels)
318 a global auto-op (always op this user on join)
319 w wasop-test (needs wasop test for +stopnethack procedure)
320 e global exempted from stopnethack
321 g give auto-voice (works as +a but for voice instead)
322 (plus 26 user-defined flags, A-Z)
323
324 each channel that the user has joined will have a specific record
325 for it, with the channel-specific flags and possibly an info
326 line. the channel-specific flags are:
327 m master (user is a master for the channel)
328 n owner (user is an owner for the channel)
329 o op (bot will give this user chanop)
330 d deop (bot will not allow this user to become a chanop)
331 f friend (user is not punished for doing bad things)
332 v voice (user gets +v automatically on +autovoice channels)
333 q quiet (user never gets +v on +autovoice channels)
334 a auto-op (always op this user on join)
335 w wasop-test (needs wasop test for +stopnethack procedure)
336 e exempted from stopnethack
337 g give auto-voice (works as +a but for voice instead)
338 (plus 26 user-defined flags, A-Z)
339
340 hostmasks for the user are displayed on the following lines.
341 if the user entry is for a bot, there will be a line below which
342 says "ADDRESS:" and gives the bot's telnet address. some user
343 entries may have "EMAIL:" and "INFO:" entries too.
344 There may be additional information displayed depending on the
345 modules loaded.
346
347 for bots, there are additional flags seen under the BOTATTR:
348 entry, these include:
349 s share (bot is sharing user records, aggressively)
350 p share (bot is sharing user records, passively)
351 g global share (share all channels)
352 h hub (bot is auto-linked at highest priority)
353 a alternate (bot is auto-linked if no hub bots can be linked)
354 l leaf (bot is not allowed to link in other bots)
355 r reject (bot will not be allowed on the net)
356 i isolate (isolate the party line across a botlink)
357 (plus 10 user-defined flags, 0-9)
358 bots may also have +s (share) settings for individual channels
359 %{+m}
360 masters: if there is a comment, you will see it under "COMMENT:"
361 %{-}
362
363 see also: match
364 %{help=status}%{+m|m}
365 ### %bstatus%b
366 ### %bstatus all%b
367 displays a condensed block of information about how the bot
368 is running. here's an example from Snowbot:
369 I am Snowbot, running eggdrop v1.1.1: 400 users (mem: 42k)
370 Running on BSDI 2.5
371 Admin: Robey <robey@wc130.residence.gatech.edu>
372 #turtle : 2 members, enforcing "+tn-mlk" (greet, bitch)
373 #gloom : 3 members, enforcing "+tn-i" (greet)
374 Server minnie.cc.utexas.edu:6667
375 Online for 4 days, 06:18 (background) CPU 14:18 cache hit 55.3%%
376
377 the first line tells you the bot's name, what version of eggdrop
378 it's running, the number of users the bot has records of, and the
379 amount of memory being used.
380
381 the second line, tell what operating system the bot is running
382 under.
383
384 the third line, if present, is the contents of your 'admin'
385 line in the config file.
386
387 next is a line for each of the channels your bot is currently
388 monitoring. for each channel, it lists the number of people on
389 the channel ("members"), what channel modes it's trying to enforce,
390 and which options are set for that channel.
391
392 if your bot is sharing user files with anyone, and is currently
393 either transmitting or receiving the userfile from a bot, it will
394 say so here, and tell how many users have been received so far,
395 or how many more users need to be transmitted.
396
397 the next few lines show the current server, and if the helpbot is
398 in use, its nickname and current server. to prevent server
399 flooding, both the bot and its helpbot use queues to store replies
400 to queries from users. if either queue has a significant amount
401 of information in it, this status display will show how full (%%)
402 the queue is.
403
404 the next line tells you how long the bot has been online, and
405 whether it is operating in the background or foreground. if it's
406 in the foreground, it will tell you whether it's in terminal mode
407 or channel display mode. (terminal mode makes the local console
408 simulate a dcc chat connection, and channel display mode displays
409 a '.status' and '.channel' output every few seconds.) it will
410 also give you an estimate of the amount of CPU time (minutes and
411 seconds) the bot has used so far, and how well the cache is
412 working. (the cache is an attempt to keep the CPU time down, and
413 anything over 50%% or so is just great.)
414
415 if you do %b'.status all'%b you will see another pageful of info,
416 showing every internal setting as specified in the config file.
417 it should be self-explanatory to anyone who needs to use it.
418
419 see also: set, channel
420 %{help=uptime}%{+m|m}
421 ### %buptime%b
422 displays the bot's current uptime like .status would show.
423
424 see also: status

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23