/[cvs]/eggdrop1.6/help/cmds1.help
ViewVC logotype

Contents of /eggdrop1.6/help/cmds1.help

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


Revision 1.22 - (show annotations) (download)
Thu Nov 26 09:32:27 2009 UTC (10 years, 6 months ago) by pseudo
Branch: MAIN
CVS Tags: HEAD
Changes since 1.21: +1 -0 lines
Moved console flags validation from cmd_console() to a separate function check_conflags().

Added calls to check_dcc_attrs() / check_dcc_chanattrs in tcl_chattr() to make the behaviour consistent between all chattr functions.

Added calls to check_conflags() in check_dcc_attrs/check_dcc_chanattrs() and chon_console() in order to ensure users will not retain privileged console flags if their access gets downgraded.
Fixes Bugzilla Bug # 133 ".chattr / .console bug"
Found by: DarkReap1 / Patch by: pseudo

1 %{help=+bot}%{+t}
2 ### %b+bot%b <handle> [address[:bot port[/user port]]] [host]
3 Creates a user record for a new bot with the handle given. If no hostmask
4 is specified, the bot will try to automatically add a host from the channel.
5 The bot's address will be used in linking. If the bot has a separate port
6 for bots and users they should be separated with a slash (/).
7
8 See also: -bot
9 %{help=+host}%{+t|m}
10 ### %b+host%b [handle] <hostmask>
11 Adds a hostmask to a user's user record. Hostmasks are used to identify your
12 handle on IRC. If a handle is not specified, the hostmask will be added to
13 YOUR user record.
14
15 See also: -host
16 %{help=+ignore}%{+m}
17 ### %b+ignore%b <hostmask> [%%<XdXhXm>] [comment]
18 Adds an ignore to the list of ignores stored on the bot, with optional
19 comment and ignore time. This ignore is stored with your handle as the
20 creator. Ignore time has to be expressed in days, hours, and/or minutes.
21
22 See also: -ignore, ignores
23 %{help=+user}%{+m}
24 ### %b+user%b <handle> [hostmask]
25 Creates a new user record for the handle given. The new user record will
26 have no flags, an optional hostmask, and no password.
27
28 See also: -user, +host, -host
29 %{help=-bot}%{+t}
30 ### %b-bot%b <bot>
31 This is exactly the same as %b'.-user'%b (it removes a user record). It is
32 included for convenience.
33
34 See also: +bot, +user, -user
35 %{help=-host}%{-}
36 ### %b-host%b <hostmask>
37 Removes a host from your handle.
38 %{+m|m}
39
40 ### %b-host%b <handle> <hostmask>
41 Removes a hostmask from a user's user record.
42 %{-}
43
44 See also: +host
45 %{help=-ignore}%{+m}
46 ### %b-ignore%b <hostmask/number>
47 Removes the specified ignore from the list of ignores stored on the bot. You
48 may also reference the ignore by the number shown by the 'ignores' command.
49
50 See also: +ignore, ignores
51 %{help=-user}%{+m}
52 ### %b-user%b <handle>
53 Removes the specified handle's user record.
54
55 See also: +user, +bot, -bot
56 %{help=addlog}%{+to|o}
57 ### %baddlog%b <text>
58 Adds your comment to the bot's logfile. Bot masters can go back later and
59 review the log, and will see your comment (with your handle attached). This
60 is useful for explaining confusing activity.
61 %{help=away}%{-}
62 ### %baway%b [away-message]
63 Marks you as "away" on the party line. Your away message will show up in
64 the %b'.who'%b list, and will be displayed to anyone who tries to send you
65 a note. Your notes will be stored, and then displayed to you as soon as you
66 are no longer away. Saying something on the party line will automatically
67 remove your "away" status, or you can type %b'.back'%b or %b'.away'%b by
68 itself.
69
70 See also: back
71 %{help=back}%{-}
72 ### %bback%b
73 This marks you as no longer away on the party line.
74
75 See also: away
76 %{help=backup}%{+m|m}
77 ### %bbackup%b
78 This makes the bot write a backup of its entire user list to the disk. If
79 the channels module is loaded, this will also write a backup of the channels
80 file. This is useful if you feel the need to backup the userfile and channel
81 settings.
82
83 See also: reload, rehash, save
84 %{help=banner}%{+t}
85 ### %bbanner%b <text>
86 Displays a message to everyone currently using the bot's party line or file
87 area. This is useful for announcing that the bot will go down, etc.
88 %{help=binds}%{+m}
89 ### %bbinds%b [type/match] [all]
90 Shows the Tcl bindings in effect, in a list similar to this:
91 Command bindings:
92 TYPE FLAGS COMMAND HITS BINDING (TCL)
93 msg -|- rose 0 msg_rose
94 msg -|- go 0 msg_go
95 dcc m|- bind 0 cmd_bind
96 pub -|- gross 0 pub_gross
97 The fields should be self-explanatory, except for HITS, which records the
98 number of times that binding has been called. If not, go read the file
99 %b'doc/tcl-commands.doc'%b for help on the Tcl bind command. Note that the
100 builtin commands are now shown. You may also specify a type of binding to
101 show (i.e. %b'.binds msg'%b) or you can specify a wild card match (i.e.
102 %b'.binds *seen*'%b) if you want to narrow the field a bit. The wild card
103 matches will match against the TYPE, COMMAND and BINDING fields. You can
104 view more binds by adding 'all' to the end of the command.
105
106 See also: tcl
107 %{help=boot}%{+t}
108 ### %bboot%b <handle[@bot]> [reason]
109 Kicks a user off the party line and displays the reason, if you specify
110 one. You can also specify a bot, and attempt to boot someone from another
111 bot on the botnet, though it may be rejected if that bot does not allow
112 remote boots. You can not boot a bot owner.
113 %{help=botattr}%{+t}
114 ### %bbotattr%b <handle> [flags] [channel]
115 Lets you view and change the bot flags for a bot. For example, to set
116 "Fred1" +share and -hub, you would do '.botattr Fred1 +s-h.'
117
118 Whether or not you change any flags, it will show you the bot's flags
119 afterwards. To get a list of the flags possible, see %b'.help whois'%b.
120
121 %bNOTE:%b This command is NOT used to replace .chattr. It modifies bot flags,
122 such as s, h, a, u, etc.
123 %bNOTE:%b You can't use this command on bots which are directly linked to your
124 bot at the current moment.
125
126 See also: whois, chattr
127 %{help=botinfo}%{-}
128 ### %bbotinfo%b
129 Requests information from every bot currently on the botnet. Each bot should
130 eventually send you one line containing its version, network setting,
131 channels, and uptime.
132
133 See also: bottree, vbottree, bots
134 %{help=bots}%{-}
135 ### %bbots%b
136 Shows the list of bots currently on the botnet.
137
138 Example:
139 Bots: cEvin, ruthie, Killa1
140
141 There is no indication of which bots are directly connected to this current
142 bot. Use %b'.who'%b%{+t} or %b'.bottree'%b%{-} for that information.
143
144 See also: bottree, vbottree, botinfo
145 %{help=bottree}%{-}
146 ### %bbottree%b
147 Shows a tree-format diagram of the bots currently on the botnet. It's just a
148 nice way to get a feel for how the bots are physically connected. If 2 bots
149 are sharing, a + will be indicated, or a ? if nothing is known.
150
151 See also: bots, botinfo, vbottree
152 %{help=chaddr}%{+t}
153 ### %bchaddr%b <bot> <address[:bot port[/user port]]>
154 Changes the address for a bot. This is the address your bot will try to
155 connect to when linking. If the bot has a separate port for bots and users,
156 they should be separated by a slash (/).
157
158 See also: link, +bot
159 %{help=chat}%{-}
160 ### %bchat%b <on/off>
161 ### %bchat%b <[*]channel number/name>
162 Changes your current channel on the partyline. When you first connect to
163 the partyline, it places you on channel 0 (the main party line).
164
165 Some channels may have assigned names if the assoc module is loaded. For
166 these, you can specify the channel by name instead of channel number if
167 you wish.
168
169 %b'.chat off'%b removes you from all channels, including the main party line.
170 You can still use bot commands and see the console, but you can't talk to
171 anyone except via %b'.note'%b. %b'.chat on'%b returns you to the main party
172 line (channel 0) if you were elsewhere.
173
174 If you prefix the channel with a '*', you will join a local channel.
175
176 See also: console
177 %{help=chattr}%{+m|m}
178 ### %bchattr%b <handle> [flags] [channel]
179 This lets you view and change the flags for a user.
180
181 For example, to give Lamer the p and f flags:
182 .chattr Lamer +pf
183
184 To remove Denali from the global op list:
185 .chattr Denali -o
186
187 You may also do any combination of the above:
188 .chattr Fred1 -m+xj-o
189
190 You can also change the flags for Usagi on a specific channel by supplying
191 the channel after the attributes:
192 .chattr Usagi -m+dk-o #blah
193
194 Changing global and channel specific flags within the same command line is
195 also possible (global +f, +o #lamer):
196 .chattr Bill f|o #lamer
197
198 Whether or not you change any flags, it will show you the user's attributes
199 afterwards. To get a list of all possible flags, see %b'.help whois'%b.
200
201 %bNOTES:%b Only the owner may add or remove the 'n' (owner), 'm' (master) or
202 't' (botnet master) flags. It is pointless to -n a permanent owner.
203 You must remove the permanent owner in the config file.
204
205 See also: whois, botattr
206 %{help=chhandle}%{+t}
207 ### %bchhandle%b <oldhandle> <newhandle>
208 Changes the handle of a user. For example, to change the handle of user
209 'gavroche' to 'jamie', you would use 'chhandle gavroche jamie'.
210
211 See also: chpass
212 %{help=chpass}%{+t}
213 ### %bchpass%b <handle> [newpassword]
214 Changes a user's password. If you do not specify the new password, the user
215 effectively no longer has a password set. A password is needed to get ops,
216 join the party line, etc.
217
218 %bNOTE:%b In previous versions, setting a password to "nopass" would clear
219 a user's password -- with encrypted passwords. This no longer works!
220
221 See also: chhandle
222 %{help=comment}%{+m}
223 ### %bcomment%b <user> <comment>
224 Creates or changes the comment field for a user. The comment field can only
225 be seen via 'whois' or 'match'. Non-masters cannot see the comment field.
226 %{help=console}%{+to|o}
227 ### %bconsole%b [channel] [modes]
228 Changes your console level so that you will see only the types of console
229 messages that you want to. Your current console channel is the channel (that
230 the bot is on) from which you can view from the party line, and which
231 channel-specific commands (like 'say' and 'op') take affect on.
232
233 Valid flags are:
234 %bj%b joins, parts, quits, and netsplits on the channel
235 %bk%b kicks, bans, and mode changes on the channel
236 %bm%b private msgs, notices and ctcps to the bot
237 %bp%b public text on the channel
238 %bs%b server connects, disconnects, and notices
239
240 %{+m}
241 Masters only:
242 %bb%b information about bot linking and userfile sharing
243 %bd%b misc debug information
244 %bc%b commands
245 %bo%b misc info, errors, etc (IMPORTANT STUFF)
246 %bw%b wallops (make sure the bot sets +w in init-server)
247 %bx%b file transfers and file-area commands
248
249 %{+n}
250 Owners only (these have to be enabled in the config file via "set raw-log"):
251 %bh%b raw share traffic
252 %br%b raw incoming server traffic
253 %bt%b raw botnet traffic
254 %bv%b raw outgoing server traffic
255
256 There are also 8 user-defined console modes ('1' through '8').
257
258 %{+o|o}
259 The mode can also be a modifier like '+p' or '-jk' or '+mp-b'. If you omit
260 the channel and modes, your current console channel and flags will be shown.
261
262 %{+m|m}
263 ### %bconsole%b <user> [channel] [modes]
264 This is used to set the console level of another user. This can even be used
265 on users who normally would not be able to set their own console mode.
266 %{help=dccstat}%{+m}
267 ### %bdccstat%b
268 Displays a table-format list of all "dcc" connections in use on the bot.
269 Dcc stands for "Direct Client-to-client Communication", and Eggdrop expands
270 this to cover every open socket. Any type of network connection to the bot
271 is considered a "dcc" connection.
272
273 The headings of the table are:
274 %bSOCK%b the socket number of this connection (always unique)
275 %bADDR%b the ip address mask of the host the bot is connected to, if
276 applicable
277 %bPORT%b the port number being used for this connection
278 %bNICK%b the handle of the user or bot, if applicable
279 %bHOST%b the hostname corresponding to the IP address, if available
280 %bTYPE%b the type of dcc connection (see below)
281
282 The types of connections currently possible are as follows (but more are
283 being added all the time):
284 %bCHAT%b dcc-chat partyline user
285 %bPASS%b user entering dcc chat (being asked for password)
286 %bSEND%b user sending a file
287 %bGET%b sending a file to a user
288 %bGETP%b pending get (waiting for the user to acknowledge)
289 %bLSTN%b telnet listening port (in place of a hostname, it will show the
290 callback procedure name, or a mask of acceptable handles)
291 %bT-IN%b incoming telnet user (being asked for handle)
292 %bFILE%b user in dcc-chat file area
293 %bBOT%b connected bot (botnet connection)
294 %bBOT*%b pending bot link (waiting for acknowledgement)
295 %bRELA%b user in relay connection to another bot
296 %b>RLY%b bot being relay'd to (one for each "RELA")
297 %bCONN%b pending telnet connection (chat, relay, bot-link, etc)
298 %bNEW%b new user via telnet (entering a handle)
299 %bNEWP%b new user via telnet (entering a password)
300
301 In addition, 'CHAT' and 'BOT' have flags listed for each connection. Capital
302 letters mean that the flag is on, and lowercase letters mean that the flag
303 is off. The flags for 'CHAT' are:
304 %bC%b in file area, but allowed to return to party line
305 %bP%b party line access only
306 %bT%b telnet connection (instead of dcc chat)
307 %bE%b echo is on
308 %bP%b paging is on
309
310 The flags for 'BOT' are:
311 %bP%b ping sent, waiting for reply
312 %bU%b user-file sharing is active
313 %bC%b local bot initiated the connection
314 %bO%b user-file offered, waiting for reply
315 %bS%b in the process of sending the user-file
316 %bG%b in the process of getting the user-file
317 %bW%b warned this bot to stop hubbing
318 %bL%b leaf-only bot (not allowed to be a hub)
319 %bI%b bot is currently in the 'linking' stage
320 %bA%b bot is being aggressively shared with
321
322 For 'CHAT' users, the party-line channel is also listed.
323 %{help=debug}%{+m}
324 ### %bdebug%b
325 Display a dump of memory allocation information, assuming the bot was
326 compiled with memory debugging. It's useless to anyone but developers
327 trying to find memory leaks.
328 %{help=echo}%{-}
329 ### %becho%b <on/off>
330 Specifies whether you want your messages echoed back to you. If it's on,
331 then when you say something on the party line, it will be displayed to you
332 just like everyone else will see it. If it's off, then it won't happen.
333 %{help=die}%{+n}
334 ### %bdie%b [reason]
335 This kills the bot. The bot goes offline immediately, logging who issued
336 the 'die' command. You shouldn't have to use this too often. If you specify
337 a reason, it is logged, otherwise the reason is "authorized by <handle>".

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23