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 USER

N (manager) commands

X (Xmaster) Undernet X commands

n (owner) commands

m (master) commands

o (op) commands

l (halfop) commands

v (voice) commands

- (valid user) commands

  • output
  • host
  • userset


  • SETUP user's settings & info, all valid user flags/settings & their explication you can find on the flags page.

    Syntax chan: !userset <$setting> [-global] <-on|-off|$text|$host> [$user|$nick] [-now]
    Syntax msg: /msg <BotNick> userset <$setting> [-global] <-on|-off|$text|$host> [$user|$nick] [-now]

    Description:

    $setting - the user setting/info - permident, antihack, reporting, info, mail, url & invisible.

    -global - setup global user setting(s), used with the parameter "info".

    -on - enable the setting/info, used with the parameters "permident", "antihack", "reporting" & "invisible".
    -off - disable tthe setting/info, used with the parameters "permident", "antihack", "reporting" & "invisible".
    $text - setting/info value, used with the parameters "info", "mail" & "url".
    $host - valid hostmask *!ident@host, used with the parameter "permident". Pay attention at security of provided host, if the host is insecure (too common, when somebody else may match the host) you may have problems on channel, even take. It's STRONGLY recommended to setup the hosts in this way: *!ident@cool.SHELL.host.or.ip.com, *!ident@complete.PROIVDER.host.or.ip.com, *!*@edyy.users.undernet.org, *!*@edyy.users.quakenet.org,. Otherwise, for example: if you have a psy on shell and setup the host like *!*@cool.SHELL.host.com (without ident) - any user on same shell will able to match this host (if you have autoop or protections flags, the user with same host will have also autoop or protections), this is the reason why unique idents are enabled on shells, to make unique uhosts & to distinguish the users.

    $nick - the user's nick to setup the setting(s) for. The BOT will check if this person has an user or not on BOT. If it has no user - the BOT will announce you about. Sometimes it may happen that there is already an user on BOT with same name as the nick on channel, but the user's host does not correspond to the nick's host currently on channel. In this case the BOT will warn you, that there is already an user on BOT with same name as nick but with a different host. If you are sure that the nick on channel is the same person as the BOT's current user - use the parameter "-now" to enforce the BOT to setup the setting(s) for this user. Another option in this case, which is more secure - you can ask the person to authorise on BOT - in order to have the new host registered & to be recognised by BOT (global +o access level requireed).
    $user - user on BOT to setup the setting(s) for (global +o access level requireed).

    -now - enforce the BOT to setupt the setting(s) when there is an user which host does not correspond to the curent nick on channel.

    Example: !userset permident *!*@niqu.users.undernet.org or /msg DELPHINUS userset antihack on
    Example: !userset invisible -on or !userset info -global blabla
    Example: !userset mail edyy@mail.com edyy or !invisible on

    Note: see also the commands userinfo, output, whois & host.

  • userinfo
  • access
  • pass
  • newpass
  • auth
  • login
  • deauth
  • newhandle

~ (common) commands

GLOBAL USER

N (manager) commands

n (owner) commands

m (master) commands

o (op) commands

v (voice) commands