/[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.1 - (show annotations) (download)
Sat Oct 9 13:10:46 1999 UTC (20 years, 5 months ago) by fabian
Branch: MAIN
finished reordering help files. They were all misplaced...

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]
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) if you want to narrow the field a bit.
95 ### %bbinds%b [type] %ball%b
96 Displays all the Tcl bindings of every type (or the specified
97 type), including the bindings for built in commands such as:
98 msg - op *msg:op
99 %{help=boot}%{+t}
100 ### %bboot%b <nickname> [reason]
101 ### %bboot%b <nick@bot> [reason]
102 Will kick a user off the party line, and display the reason if you
103 give one. You can attempt to boot someone from another bot (in a
104 botnet), though it may be rejected if that bot does not allow remote
105 boots. You can not boot the bot's owner.
106 %{help=botattr}%{+t}
107 ### %bbotattr%b <nickname> [attributes] [channel]
108 Lets you view and change the attributes (flags) field for a bot.
109 Example:
110 Sets Fred1 +share and -hub.
111 .botattr Fred1 +s-h
112
113 Whether or not you change any flags, it will show you the bot's
114 attributes afterwards.
115 To get a list of the flags possible, do %b'help whois'%b.
116 %bNOTE:%b This command is NOT used to replace .chattr,
117 it modifies botflags such as +s, +h, +a, +u... bot specific
118 flags only.
119 %bNOTE:%b You can't use this command on bots which are directly
120 linked to your bot at the current moment.
121
122 See also: whois, chattr
123 %{help=botinfo}%{+t}
124 ### %bbotinfo%b
125 Requests information from every bot currently in the botnet.
126 Each bot should eventually send you one line listing its version
127 and other information.
128 %{help=bots}
129 ### %bbots%b
130 Shows the list of bots currently in the botnet. Example:
131 Bots: cEvin, ruthie, Killa1
132 There is no indication of which bots are directly connected to
133 this one. Use %b'who'%b %{+t}or %b'bottree'%b%{-} for that information.
134 %{help=bottree}%{+t}
135 ### %b[v]bottree%b
136 Shows a tree-format diagram of the bots currently in the botnet.
137 It's just a nice way to get a feel for how the bots are connected
138 physically. if 2 bots are sharing, a + will be indicated, or a ?
139 if nothing is known.
140 Use vbottree if you want to know bot versions as well.
141
142 See also: bots, botinfo
143 %{help=chaddr}%{+t}
144 ### %bchaddr %b<bot> <address:botport#/userport#>
145 Changes the internet address for a bot. This is the address
146 your bot will try to telnet to in order to create a connection
147 and link up. If the bot has a seperate port for bots and users
148 they should be seperated with a slash (/).
149
150 See also: link, +bot
151 %{help=chat}
152 ### %bchat off%b
153 ### %bchat <channel # or name>%b
154 Changes your channel on the dcc chat connection. when you first
155 connect to the bot, it places you on channel 0 (the party line).
156 You can move to another channel where basically nobody can see
157 you (except anyone else who decides to join that channel). Valid
158 channel numbers are 1 thru 99999.
159
160 Some channels may have assigned names if the assoc module is
161 loaded. For those, you can specify the channel by name instead
162 of number if you wish.
163
164 %b'chat off'%b removes you from any channel at all. You can still
165 use normal bot commands and see the console, but you can't talk
166 to anyone except via %b'.note'%b
167
168 %b'chat on'%b returns you to the party line (channel 0) if you were
169 elsewhere.
170
171 ### %bchat%b <*channel# or name>
172 Same as above, but for channels available only to the bot you
173 are on.
174 %{help=chattr}%{+m|m}
175 ### %bchattr%b <nickname> [attributes] [channel]
176 Lets you view and change the attributes (flags) field for a user.
177 For example, to give Lamer the p and f flags:
178 .chattr Lamer +pf
179 Or to remove Denali from the global op list:
180 .chattr Denali -o
181 You may also do any combination of the above:
182 .chattr Fred1 -m+xj-o
183
184 You can also change the flags for Usagi on a specific channel by
185 supplying the channel after the attributes:
186 .chattr Usagi -m+dk-o #blah
187
188 Changing global and channel specific flags within the same command
189 line is now possible! Example:
190 .chattr Bill f|o #lamer (global +f, +o #lamer)
191
192 Whether or not you change any flags, it will show you the user's
193 attributes afterwards.
194
195 To get a list of the flags possible, do %b'help whois'%b.
196
197 %bNOTES:%b
198 Only the owner may add or remove the 'n' (owner), 'm' (master)
199 and 't' (botnet master) flags.
200 It is pointless to -n a permanant owner. You must remove the
201 permanant owner in the config file.
202 This command can no longer be used to change bot flags, they
203 are a seprated entity, changeable with the %b'.botattr'%b command.
204 See also: whois
205 %{help=chnick}%{+t}
206 ### %bchnick%b <oldnick> <newnick>
207 Changes the handle/nickname of a user record. For example, to
208 change the nickname of user 'gavroche' to 'jamie', you would
209 type: 'chnick gavroche jamie'
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 'user' 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 use is paging
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=debug}%{+m}
316 ### %bdebug%b
317 will display a dump of memory allocation, assuming the bot was
318 compiled with DEBUG defined. it's useless to anyone but program-
319 mers hacking on the bot and trying to find memory leaks.
320 %{help=echo}
321 ### %becho%b <on/off>
322 sets whether you want your messages echoed back to you. if it's
323 on, then when you say something on the party line, it will be
324 displayed to you just like everyone else will see it. if it's off,
325 then that won't happen.
326 %{help=die}%{+n}
327 ### %bdie%b [reason]
328 kills the bot. the bot goes offline immediately, logging who gave
329 the 'die' command. you shouldn't have to use this too often. if you
330 specify a reason, it's logged, otherwise the reason is "authorized by
331 <nickname>".

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23