2.2. Meanings of umodes

2.2.1. +a, auspex

Auspex is the ability to see all servers and IP addresses. Care should be taken to keep this information private, and not reveal it to non-auspex users.

2.2.2. +A, user auspex

User auspex is the ability to see all users and channels. Users with this mode set can see inivisible users and secret channels, and all members. Care should be taken to keep this information private, and not reveal it to non-auspex users.

2.2.3. +b, see bots

Users with the +b umode set will receive warning messages from the server when potentiol flooders and spambots are detected.

2.2.4. +B, edit other users

This umode allows the operator to use the SETHOST, SETNAME, and SETIDENT commands on other people. It also allows the operator to change another person's umode, although they cannot grant modes that the target user doesn't have without +*, grant modes.

2.2.5. +c, see client connections

Users who have the +c umode set will receive server notices when clients attach to the network. They are also warned when a client fails to provide reverse DNS or ident information.

2.2.6. +C, block CTCP

This is a user umode, which anybody can set. It is not specific to operators.

Note that this will interfere with CTCP ACTION messages (/me), so it is not recommended it be used unless absolutely necessary.

2.2.7. +d, debug

The +d umode provides extra information and commands which may be of interest to debuggers. It will also cause the user to receive server notices if certain assertions fail inside the server. It's precise meaning is extremely variable. While every effort will be made to ensure that it grants no extra privileges, no guarantees can be made. Do not depend on the effects of this umode as they can and will change without notice in later revisions.

Note that this may (and usually will) divulge information about the network routing. It may also give away IP addresses. Yeah, it's a security risk. Sorry.

2.2.8. +D, die command

The DIE command causes a server to cease processing at once and exit. This umode should not be granted without due care.

2.2.9. +e, identified

This umode is used for integration with dancer/hybserv. A user with the +e umode has successfully identified with nickserv.

Under no circumstances should +e be granted in an O:line.

2.2.10. +E, reject messages from unidentified users

This is a user umode, which anybody can set. It is not specific to operators.

2.2.11. +f, full warning

Users with the +f umode set will receive notices when an I:line becomes full, and users can no longer connect.

2.2.12. +F, immune to flood protection

+F users will not be throttled in their use of commands, nor will they be checked by the flood detection code.

2.2.13. +G, global kill

An operator who can do global kills can kill a user who is attached to a different server. See +K, local kill.

2.2.14. +h, high priority

A person with high priority set will have their connection polled more often by the server, and will still be able to do stuff while the server is in high traffic mode. Normally, high traffic mode means that most commands from attached clients will be rejected, until the server can clear it's backlog of processing. This mode should be granted sparingly, to only those people who would need to be able to work rapidly when the server is under extreme load.

2.2.15. +H, rehash

This grants the ability to use the rehash command, to reload the server configuration files.

2.2.16. +i, invisible

This is a user umode, which anybody can set. It is not specific to operators.

2.2.17. +I, refuse invite

This is a user umode, which anybody can set. It is not specific to operators.

2.2.18. +k, server kill notices

Users with the +k umode set will receive server notices when server kills occur.

2.2.19. +K, local kill

With the +K umode, a person can set klines and use the KILL command, to remove people from the server they are connected to.

2.2.20. +l, channel creation notices

A user with +l set will receive a server notice when a new channel is created (by somebody entering it).

2.2.21. +L, force lusers

With the +L umode set, a user can use the 4-argument LUSERS message to force a recount.

2.2.22. +m, immune

they are able to speak even if they are banned.

2.2.23. +M, mass notices

A user with +M set can send notices to people based on a mask. A notice to $* will go out to every user on the network.

2.2.24. +n, nick change notices

A user with +n set will receive a server notice every time somebody changes their nick, giving the old and new nicks.

2.2.25. +N, use any nick

The +N umode overrides Q:lines and X:lines, which normally forbid the use of given nicks. This is potentiolly useful if running without services, to protect the nicks of opers, should you wish to do that.

2.2.26. +o, operator

This indicates global operator status. It's meaning is now minimal; it is a gateway to the operator umodes. Setting -o will automatically remove all the operator umodes. The things which +o still does are listed in Dancer operators.

Under no circumstances should +o be granted in an O:line.

2.2.27. +p, god mode

do, they can always join channels and speak regardless of channel modes, limits, or bans.

2.2.28. +P, SETHOST and SETIDENT

This umode allows the use of the command SETHOST, and SETIDENT.

2.2.29. +r, notices on name rejections

Users with this umode set will receive a server notice when somebody tries to use an invalid nick/username, or a quarantined nick (Q:link) or banned realname (X:line).

2.2.30. +R, server routing

This umode grants the use of the commands CONNECT and SQUIT, in both local and remote forms. It also allows the use of the HTM command to query/change current HTM settings.

2.2.31. +s, server notices

This umode allows a user to receive server notices.

2.2.32. +S, run commands remotely

This allows various commands, notably ADMIN, INFO, MOTD, VERSION, and STATS, to be used in their remote form, where an extra server parameter is given and the command executes on a remote server, returning results to the user.

Note that this command does not affect the local or remote forms of the CONNECT and SQUIT commands; these are controlled entirely by umode +R.

2.2.33. +U, unkline

This grants the use of the UNKLINE command.

2.2.34. +v, view privileges

This causes the privileges an oper has available to be returned when the +v user WHOIS's them.

2.2.35. +V, view routing

This allows the routing between the servers to be seen. This activates the MAP command, and shows routing information in LINKS, as well as showing full server connection messages.

2.2.36. +w, receive wallops

This is a user umode, which anybody can set. It is not specific to operators.

2.2.37. +W, send wallops

Users with the +W umode can use the WALLOPS command to send WALLOPS messages.

2.2.38. +x, see servers joining

People who have the +x umode set will see all servers being introduced when a server rejoins, not just the one which made the connection. (This means all the servers already connected on the other side of the link). This obviously divulges routing information, and is rather loud on a large network. It's value is uncertain.

2.2.39. +X, experimental features

This umode controls access to various experimental features of dancer. It is deliberately undocumented. If you do not know what it does (if you are not involved in the development of dancer) then you should not use it. The features it controls will eventually be moved out and documented when their usage (and their side effects) are better understood.

2.2.40. +y, spy

This umode should be used with caution, as it is an invasion of privacy. Nonetheless, it is necessary that some people have this ability to detect stealthy floods. All sorts of client activity will be reported to an oper with umode +y set.

2.2.41. +Y, server connection details

This umode activates some extra messages sent during server connection, which used to be attached to +s. It exists mostly so that it can be turned off if these messages become bothersome.

2.2.42. +z, receive operwall

OPERWALL differs from WALLOPS in that the ability to receive such messages is restricted. Users with +z set will receive OPERWALL messages.

2.2.43. +Z, send operwall

The ability to send OPERWALL messages is controlled by the +Z umode.

2.2.44. +0, see opers

Users with the +0 umode set are able to tell that a person is an oper by their WHOIS, and in various other commands such as STATS o and TRACE.

2.2.45. +1, see connection settings

This umode allows the use of STATS commands to see:

2.2.46. +2, see network bans

This umode allows the use of STATS commands to see:

2.2.47. +3, see nick bans

This umode allows the use of STATS commands to see:

2.2.48. +4, see STATS T

This allows the use of the STATS T command, to get general server statistics.

2.2.49. +5, see STATS ?

This allows the use of the STATS ? command, to get a list of all servers and some statistics on them from the perspective of the current server.

2.2.50. +9, use testline

This umode enables the TESTLINE command.

2.2.51. +*, grant umodes

This umode allows the user to grant umodes they have access to to other people. As such it is very dangerous, and should be carefully controlled. It is strongly recommended that * never be put in the default umodes for anybody, and that it only be set when it is needed, to prevent accidents.

When a user has +* set, then they may set a mode on another user which that user would not normally have access to (assuming the originator has the ability to gain that mode themselves). This umode will be added to the list of umodes that the target has access to for the duration of the session. Similarly, removing a umode will revoke the ability to use that mode, unless it is in the list of normal user modes.

This umode is useless without +B also set.

2.2.52. +@, free spoofing

This umode allows the user to change their host to anything with the SETHOST command. Without it they can only use the 0-argument form of SETHOST to flip between their real and official spoofed hostname.

This umode is useless without +P also set.