Image: Welcome
HOME
COUNTER

LOCAL & GLOBAL USER FLAGS

  • N (manager) grants access to local X, ChanServ, manager, owner, master, op, halfop & voice commands. botland 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 local 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 botland BOTs this a local manager (+N flag) prerogative.

  • m (master) grants access to local 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 local op, halfop & voice commands. Standard eggdrop local op flag, like 100-399 access on X. Essential commands which allow to administer & protect your channel (see also user +a & channel autoop flags for autoopping a single OP or all channels OPs).
    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.

  • l (halfop) grants access to local halfop & voice> commands. Standard eggdrop local halfop flag, like 100-200 access on X.

  • v (voice) grants access to local 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 (see also user +g & channel +autovoice flags for autovoicing a single voice or all channels users).

  • a (autoop) standard eggdrop local 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.

  • y (autohalfop) standard eggdrop local autohalfop flag. User with +y is autohalfopped automatically on channel join or if autohalfdeopped on channel - user will be autohalfopped back.

  • g (autovoice) standard eggdrop local 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.

  • f (friend) standard eggdrop local 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. - all these abuse level actions will be relieved due to +f flag.
    Note: certainly the BOT will put all modes back as set up in channel setup & will unban, op again or invite on channel +HP flag user, +f flag exempt only from being punished.

  • X (X, ChanServ commands) grants access to X & ChanServ commands. botland 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) botland specific flag. The user with +P flag will be protected against deop, kick & ban (see also +revenge & revenge-mode channel flags - to specify for an entire category of users with +f or +o flag). If kicked or banned the user will be automatically invited on channel by BOT, if deopped the user will be opped back. This is the first level protection flag - it means that as punishment the BOT will deop the offender (see also +H flag).
    Note: 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 protect command.

  • H (heavy-protected user) botland specific flag. As +P user, +H flag protects against deop, kick & ban (see also +revenge & revenge-mode channel flags - to specify for an entire category of users with +f or +o flag). 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.
    Note: 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 protect command.

  • L (locked user) botland 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) botland specific flag. Suspends local user access - the user can not do anything but he still "delights" exemption punishment & flag protections (with consideration that he has +f, +n or +P flags).
    Note: +S flag can be given only by a +N user level access (manager).

  • 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: Some times 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.

  • 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 (see also the ban command). 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.

  • 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.

  • 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 dehalfopprf by a +m user level access or higher - the BOT will allow this user to be dehalfopped.

  • w (wasop-test) standard eggdrop flag. A +w access level user will pass wasop test procedure (see also stopnethack-mode channel flag).

  • z (washalfop-test) standard eggdrop flag. A +z access level user will pass washalfop test procedure (see also stopnethack-mode channel flag).

  • e (exempted from stopnethack) standard eggdrop flag. A +e access level user will not pass wasop test procedure on channels with stopnethack-mode channels flag.

GLOBAL USER FLAGS

  • Q (authorised user) botland specific flag. 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) botland specific flag. Identifies nerwork channel services like X or ChanServ.

  • B (botland bot) botland specific flag. Identifies botland BOTs.

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

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

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

  • b (bot) standard eggdrop flag. Identifies any BOT, here included botland 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 all these 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.

USER SETTINGS

  • antihack - enalbed, 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

  • 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

  • permident - enabled, allow the user to command the BOT from the given host (mask) without authorisation, be sure to specify a unique host. updating.
    Example: !userset permident *!*@xuser.users.undernet.org

  • reporting - to store a report - when antihack/secure is enabled ?
    Example: !userset reporting on

  • mail - personal mail.
    Example: !userset mail blah@botland.org

  • url - personal web page.
    Example: !userset url http://botland.org

  • invisible - allow other users to see your information or not ?
    Example: !userset invisible on

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.

Page was generated in 0.0024 secconds.
All rights reserved © botland.horatiu.vip 2026
Some articles are used with permission of starbots.info thanks aqwzsx :)