HOME

- News
- Admins

SUPPORT

- SETTINGS
- COMMANDS
- FLAGS
- a&a FAQ
- a&a forum
- a&a links

RULES

- Rules of use
- Terms of use
- Admins rules
- Helping rules
- Purge rules
- Become helper

LOCAL & GLOBAL USER FLAGS

  • N (manager) grants access to X, ChanServ, manager, owner, master, op, halfop & voice commands. a&a specific flag, this is the maximum access you can have on channel, like 500 access on X. Nobody with local access can remove this flag & it can be only one manager per channel (one user with +N flag). This flag grants automatically access to all local BOT's commands on channel, you do not need any special flag like +X or any of this kind.

  • n (owner) grants access to owner, master, op, halfop & voice commands. Standard eggdrop local owner flag, like 450-499 access on X. Major channel setup commands are available for this level access, chose your owners cautiously.
    Note: by default, an owner can remove or add +n flag (grant local owner access), on a&a BOTs this a local manager (+N flag) prerogative.

  • m (master) grants access to master, op, halfop & voice commands. Standard eggdrop local master flag, like 400-449 access on X. This is the minimum level access required for chattr - command which allows the user to grant local access on BOT to anyone on channel.

  • o (op) grants access to op, halfop & voice commands. Standard eggdrop local op flag, like 100-399 access on X. Essential commands which allow to administer & protect your channel.
    Note: if you have no X or ChanServ on your channel, you will have to adopt a security policy to prevent take (described in our FAQ) & oblige all chan master & owners to respect it.
    Note: see also the user flags a, d & w & the channel flags autoop & op.


  • l (halfop) grants access to halfop & voice commands. Standard eggdrop local halfop flag, like 100-200 access on X.
    Note: see also the user flags y, r & z & the channel flags autohalfop & halfop.

  • v (voice) grants access to voice commands. Standard eggdrop local voice flag, like 1-99 access on X. Minimum commands granted to a channel regular, also gives access to essential channel informations.
    Note: see also the user flags g & q & the channel flags autovoice & voice.

  • a (autoop) standard eggdrop autoop flag. User with +a is opped automatically on channel join or if deopped on channel - user will be opped back (must have +o flag too).
    Note: if the deop command is used - the BOT will refuse to deop an +a level user.
    Note: see also the user flags o, d & w & the channel flags autoop & op.


  • y (autohalfop) standard eggdrop autohalfop flag. User with +y is autohalfopped automatically on channel join or if halfdeopped on channel - user will be autohalfopped back (must have +l flag too).
    Note: if the halfdeop command is used - the BOT will refuse to halfdeop an +y level user.
    Note: see also the user flags l, r & z & the channel flags autohalfop & halfop.


  • g (autovoice) standard eggdrop autovoice flag. User with +g is voiced automatically on channel join or if devoiced on channel - user will be voiced back (must have +v flag too).
    Note: if the devoice command is used - the BOT will refuse to devoice an +g level user.
    Note: see also the user flags v & q & the channel flags autovoice & voice.


  • f (friend) standard eggdrop friend flag. User with +f flag will not be punished for abusive behavior (where a normal user, by default, would be punished). Deopping, kicking, banning +P or +H users, setting +lk on channels, etc. - allse abuse level actions will be ignored due to +f flag. Certainly the BOT will put all modes back as setup by default, reop back or unban +fHP flag users; +f flag exempt only from being punished.
    Note: see also user flags P & H.

  • X (X, ChanServ commands) grants access to X & ChanServ commands. a&a specific flag, this is a very powerful flag - so pay attention to the user you are giving to.
    Note: X flag can be given only by a +N user level access (manager).

  • P (protected user) a&a specific flag. The user with +P flag will be protected against deop, kick & ban. This is the first level protection flag - it means that as punishment the BOT will deop the offender. The BOT will not punish a higher hierarchic access user (+N access level for example), a +f user or another +P user. +P flag can be given only by a +N user level access (manager).
    Note: see also the user flags H & f, the command protect & the channel flags revenge, revenge-mode, protectops, protectfriends & protecthalfops.

  • H (heavy-protected user) a&a specific flag. As +P user, +H flag protects against deop, kick & ban. The single difference is the protection level. This is the second level protection flag - it means that as punishment the BOT will ban the offender. The BOT will not punish a higher hierarchic access user (+N access level for example), a +f user or another +PH user. +H flag can be given only by a +N user level access (manager).
    Note: see also the user flags P & f, the command protect & the channel flags revenge, revenge-mode, protectops, protectfriends & protecthalfops.

  • L (locked user) a&a specific flag. Locks user's access on channel, only channel manager (+N flag) will be able to change +L user's access. This flag is given when you don't want to give too much access to a certain user but at the same time you want to be sure that other higher access users will be unable to remove +L user's access.
    Note: L flag can be given only by a +N user level access (manager).

  • S (suspended user) a&a specific flag. Suspends local user access - the user can't give any command on BOT, but the protection & auto flags are, on the contrary, still valid/functional (+f, +P, +H, +a, +y & +g).
    Note: S flag can be given only by a +N user level access (manager).

  • k (kick) standard eggdrop flag. A +k access level user will not be allowed to stay on your channel - BOT automatically will kick this user. This is just another way to get rid of somebody on chan, without fulling your chan banlist.
    Note: Some times BOT gives +k flag itself, according to revenge-mode flag setting.
    Note: see also the user flags d, r & q, the channel flag private & the commands ban & kick.


  • d (deop) standard eggdrop flag. A +d access level user will not be allowed to get OP on your channel - BOT automatically will deop this user back (see also +bitch channel flag). Besides, if the +d user is opped by a +m user level access or higher - the BOT will allow this user to be opped.
    Note: Sometimes BOT gives +d flag itself, according to revenge-mode flag setting.
    Note: if the op command is used - the BOT will refuse to op an +d level user.
    Note: see also the user flags o, a, w & k & the channel flags autoop & op.


  • r (dehalfop) standard eggdrop flag. A +r access level user will not be allowed to get HALFOP on your channel - BOT automatically will dehalfop this user back. Besides, if the +r user is dehalfopped by a +m user level access or higher - the BOT will allow this user to be dehalfopped.
    Note: if the halfop command is used - the BOT will refuse to halfop an +r level user.
    Note: see also the user flags l, y, z & k & the channel flags autohalfop & halfop.


  • q (quiet) standard eggdrop flag. A +q access level user will not be allowed to get voice on channels with autovoice channels flag.
    Note: if the voice command is used - the BOT will refuse to voice an +q level user.
    Note: see also the user flags v, g & k & the channel flags autovoice & voice.


  • w (wasop-test) standard eggdrop flag. A +w access level user will pass wasop test procedure on channels with stopnethack-mode channel flag.
    Note: Note: see also the user flags o, a, d & e & the channel flags autoop, op & stopnethack-mode.

  • z (washalfop-test) standard eggdrop flag. A +z access level user will pass washalfop test procedure on channels with stopnethack-mode channel flag.
    Note: see also the user flags l, y, r & e & the channel flags autohalfop, halfop & stopnethack-mode.

  • e (nethack-exempt) standard eggdrop flag. A +e access level user will not pass wasop test procedure on channels with stopnethack-mode channels flag (user is exempted from stopnethack protection).
    Note: see also the user flags w & z & the channel flag stopnethack-mode.

GLOBAL USER FLAGS

  • Q (authorised user) a&a specific flag, grants access to local valid user commands. It is given automatically when the user does auth on BOT, if the user has userset permident on BOT he does not need this flag.

  • W (X, ChanServ user) a&a specific flag. Identifies network channel services like X or ChanServ.

  • B (a&a bot) a&a specific flag. Identifies a&a BOTs.

  • A (antihack) a&a specific flag. It is given automatically when the user enables antihack option.

  • R (reporting) a&a specific flag. It is given automatically when the user enables reporting option.

  • I (invisible) a&a specific flag. It is given automatically when the user enables invisible option.

  • b (bot) standard eggdrop flag. Identifies any BOT, here included a&a BOTs.

  • t (botnet master) standard eggdrop flag. Grants access to botnet master commands.

  • x (xfer) standard eggdrop flag. Grants access to file-area & to xfer commands.

  • j (file-area master) standard eggdrop flag. Grants access to file-area & to janitor commands.

  • p (party-line) standard eggdrop flag. Grants access to party-line & to party-line commands.

  • c (common) standard eggdrop flag. Identifies a common-access user record. When 2 or more ppl use the same entrance & as consequence have the same user@host - in order to prevent allse ppl to appear as a single person - a common user record is created & for anyone who will match this record (when added to BOT) a new user record will be created which will identify them by nickname.

  • u (unshared) standard eggdrop flag. A +u access level user will not be sent to other share-bots. BOTs can be set up to share user records but if you need a particular user not to be on the rest of BOTs - this flag is to be used.

  • h (high-light) standard eggdrop flag. User will see highlighted text as output in telnet.

SETTINGS

  • permident - enabled allow the user to command the BOT from the given host (mask) without authorisation, be sure to specify a unique host.
    Example: !userset permident *!*@niqu.users.undernet.org
    Note: see also the commands userset & userinfo.


  • antihack - enabled blocks user's current hosts & will accept commands only from these hosts. No commands will be accepted from any other hosts, even if a maltreater will try to authorise with user's correct password, he will be ignored. Besides, if somebody will try to authorise with user's hand on BOT from an unknown uhost & reporting is ON, the BOT will store a note for user with the details of this attempt (nick, uhost, time & password he tried to use).
    Example: !userset antihack on
    Note: see also the commands userset & userinfo.


  • reporting - when antihack/secure are enabled & somebody made a take on your chan or tried to hack your user account, to store a note report ?
    Example: !userset reporting on
    Note: see also the commands userset & userinfo.


  • output - setup the colour, language & reply for BOT to answear the user. Colour - colour schemes used by BOT when answearing to user requests: none, bold, bluebold, bluered & light. Lang - the lanaguage the BOT will use answearing to user requests: english & romanian. Reply - the way the BOT will answear to user requests: by notice, by msg or directly on channel.
    Example: !output reply chan note
    Note: see also the command output.


  • info - set a global or local infoline for user (if channel is set +greet, the info will be used as greeting).
    Example: !userset info anything about you
    Note: see also the commands userset & userinfo.


  • mail - personal mail.
    Example: !userset mail niqu@starbots.info
    Note: see also the commands userset & userinfo.


  • url - personal web page.
    Example: !userset url http://starbots.info
    Note: see also the commands userset & userinfo.


  • invisible - allow other users to see your information or not (mail, url & info) ?
    Example: !userset invisible on
    Note: see also the commands userset & userinfo.


BOT FLAGS

  • s (share) standard eggdrop flag. BOT is sharing user records, aggressively.

  • p (share) standard eggdrop flag. BOT is sharing user records, passively.

  • g (global share) standard eggdrop flag. Share all channels.

  • h (hub) standard eggdrop flag. BOT is auto-linked at highest priority.

  • a (alternate) standard eggdrop flag. BOT is auto-linked if no hub bots can be linked.

  • l (leaf) standard eggdrop flag. BOT is not allowed to link in other bots.

  • r (reject) standard eggdrop flag. BOT will not be allowed on the net.

  • i (isolate) standard eggdrop flag. Isolate the party line across a botlink.