ViewVC logotype

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

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

Revision 1.7 - (show annotations) (download)
Mon Aug 21 18:28:11 2000 UTC (19 years, 7 months ago) by guppy
Branch: MAIN
CVS Tags: eggdrop105040
Changes since 1.6: +5 -7 lines
added Sup's two small patches, needfix and ignorehelp (also testing cvslog -- sorry for not letting fabian apply these patches)

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

ViewVC Help
Powered by ViewVC 1.1.23