1 |
$Id: USERS,v 1.12 2010/01/03 13:27:22 pseudo Exp $ |
2 |
|
3 |
Users and Flags |
4 |
Last revised: March 07, 2002 |
5 |
_____________________________________________________________________ |
6 |
|
7 |
Users and Flags |
8 |
|
9 |
|
10 |
People on IRC are recognized by the bot according to their |
11 |
nick!user@host. That is, if I am on IRC as: |
12 |
|
13 |
*** Robey is robey@hubcap.clemson.edu (i hate milk) |
14 |
|
15 |
Eggdrop will identify me according to "Robey!robey@hubcap.clemson.edu" |
16 |
and not only by my nickname. |
17 |
|
18 |
Eggdrop does not have access levels like some bots. There are no |
19 |
meaningless numbers or titles. Instead, each user has "flags" that |
20 |
entitle them to certain privileges. Think of a flag as a badge. Any user |
21 |
can have any number of flags -- you can have no flags, or you can have |
22 |
all of them. Some flags are good, some are bad. Each flag is identified |
23 |
by a letter. A channel flag applies only to a specific channel, and a |
24 |
global flag applies to all channels. The standard global flags are: |
25 |
|
26 |
n (owner) user has absolute control. Only give this flag to |
27 |
people you trust completely. |
28 |
|
29 |
m (master) user has access to almost every feature of the bot. |
30 |
|
31 |
t (botnet-master) user has access to all features dealing with the |
32 |
botnet. |
33 |
|
34 |
a (auto-op) user is opped automatically upon joining a channel. |
35 |
|
36 |
o (op) user has op access to all of the bot's channels. |
37 |
|
38 |
y (auto-halfop) user is halfopped automatically upon joining a channel. |
39 |
|
40 |
l (halfop) user has halfop access to all of the bot's channels. |
41 |
|
42 |
g (auto-voice) user is voiced automatically upon joining a channel. |
43 |
|
44 |
v (voice) user gets +v automatically on +autovoice channels. |
45 |
|
46 |
f (friend) user is not punished for flooding, etc. |
47 |
|
48 |
p (party) user has access to the partyline. |
49 |
|
50 |
q (quiet) user does not get voice on +autovoice channels. |
51 |
|
52 |
r (dehalfop) user cannot gain halfops on any of the bot's channels. |
53 |
|
54 |
d (deop) user cannot gain ops on any of the bot's channels. |
55 |
|
56 |
k (auto-kick) user is kicked and banned automatically. |
57 |
|
58 |
x (xfer) user has access to the file transfer area of the bot |
59 |
(if it exists) and can send and receive files to/from |
60 |
the bot. |
61 |
|
62 |
j (janitor) user can perform maintenance in the file area of the |
63 |
bot (if it exists) -- like a "master" of the file |
64 |
area. Janitors have complete access to the filesystem. |
65 |
|
66 |
c (common) this marks a user who is connecting from a public site |
67 |
from which any number of people can use IRC. The user |
68 |
will now be recognized by NICKNAME. |
69 |
|
70 |
b (bot) user is a bot. |
71 |
|
72 |
w (wasop-test) user needs wasop test for +stopnethack procedure. |
73 |
|
74 |
z (washalfop-test) user needs washalfop test for +stopnethack procedure. |
75 |
|
76 |
e (nethack-exempt) user is exempted from stopnethack protection. |
77 |
|
78 |
u (unshared) user record is not sent to other bots. |
79 |
|
80 |
h (highlight) use bold text in help/text files. |
81 |
|
82 |
All global flags other then u, h, b, c, x, j, and p are also |
83 |
channel-specific flags. Flags are set with the chattr command. |
84 |
The syntax for this command is: |
85 |
|
86 |
chattr <nickname> [attributes] [channel] |
87 |
|
88 |
There are also 26 global user-defined flags and 26 channel user-defined |
89 |
flags. These are used by scripts, and their uses very depending on the |
90 |
script that uses them. |
91 |
_____________________________________________________________________ |
92 |
|
93 |
Copyright (C) 2002 - 2011 Eggheads Development Team |