/[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.3 - (show annotations) (download)
Fri Feb 25 22:05:58 2000 UTC (19 years, 2 months ago) by fabian
Branch: MAIN
Changes since 1.2: +5 -2 lines
david's wildbinds patch

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23