i Numeric IP (the unresolved host)
s Servername (the canonic name of the server the guy is on)
r Info text (formerly "Realname")
+ a Account name
If no field-matching flags are specified they default to what old servers
used to do: nuhsr (= everything except the numeric IP)
f : Include flags (all of them)
h : Include hostname
i : Include IP
+ l : Include idle time (0 for remote users) [2.10.11+]
n : Include nick
r : Include real name
s : Include server name
t : Include the querytype in the reply
u : Include userID with eventual ~
+ a : Include account name
And the ,<querytype> final option can be used to specify what you want the
server to say in the querytype field of the output, useful to filter the
:"source" 354 "target" ["querytype"] ["channel"] ["user"]
["IP"] ["host"] ["server"] ["nick"]
- ["flags"] ["hops"] [:"realname"]
+ ["flags"] ["hops"] ["idle"] ["account"]
+ [:"realname"]
Where only the fields specified in the %fields options are present.
Oslo-R.NO.EU.Undernet.org Niels
So that he can have in example a script that does
- "on 354 * 166" display "There is an oper ..."
+ on ^354 "% 166" display "There is an oper ..."
- The client will have to sort/format the fields by itself,
the _order_ in which flags are passed is not significant, the fields in the
recomended way for GUI based clients to get a channel's userlist and all
the infos they want about users on the channel.
+- If you use the new numeric, flags will contain all the information about
+ a user on a channel. @ for op'd, + for voiced, and ! for zombie. eg:
+ Isomer #coder-com H@+, where the old behavor of just displaying one of
+ them has been preserved for the old numeric. [2.10.11+]
+
Regards, Andrea aka Nemesi