multi-prefix Extension

Copyright © 2012 William Pitcock <>

Unlimited redistribution and modification of this document is allowed provided that the above copyright notice and this permission notice remains intact.

Description πŸ”—

When requested, the multi-prefix client capability will cause the IRC server to send all possible prefixes which apply to a user in NAMES, WHO and WHOIS output.

These prefixes MUST be in order of β€˜rank’, from highest to lowest.


--> NAMES #tethys 353 guest = #tethys :~&@%+aji &@Attila @+alyx +KindOne Argure 366 guest #tethys :End of /NAMES list

--> WHO #test 352 guest #test grawity broken.symlink * grawity H@%+ :0 Mantas M. 315 guest #test :End of /WHO list

--> WHOIS barmand 311 guest barmand barmand * :Armand 319 guest barmand :~&@%+#falco @+#raynor 312 guest barmand :Antibes 318 guest barmand :End of /WHOIS list

Errata πŸ”—

Previous versions of this spec did not specify that all possible prefixes which apply to users be also sent in WHOIS output. This was added for consistency with other replies that contain user prefixes.

Software supporting multi-prefix: BitlBee, Ergo, IRCCloud Teams, ircd-hybrid, InspIRCd, Nefarious IRCu, Solanum, txircd, UnrealIRCd, AdiIRC, Ambassador, Colloquy, Glirc, HexChat, IceChat, Irssi, Konversation, KVIrc, mIRC, Mozilla Thunderbird, Quassel, senpai, Textual, WeeChat, gamja, IRCCloud, Kiwi IRC, The Lounge, web client, IRC for Android, CoreIRC, Palaver, Quasseldroid, IRCCloud (as Server), KiwiBNC (as Server), KiwiBNC (as Client), pounce (as Server), pounce (as Client), soju (as Server), soju (as Client), ZNC (as Server), ZNC (as Client), BitBot, Limnoria, Moon Moon, PyLink (clientbot), Sopel (ex Willie), ChatSharp, Communi, girc, irc-framework, ircrobots, Kitteh IRC Client Library, pydle, Rust irc, Warren