ViewVC logotype

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

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

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

ViewVC Help
Powered by ViewVC 1.1.23