View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003665 | unreal | ircd | public | 2008-03-15 15:12 | 2015-07-26 03:33 |
| Reporter | foert | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | n/a | OS | n/a | OS Version | n/a |
| Product Version | 3.2.6 | ||||
| Summary | 0003665: Numeric 972 :channel is +Q | ||||
| Description | This is returned when attempting a KICK and channel mode +Q causes refusal. The channel name isn't included in the reply, which makes it less reliable to couple a sent command to a received response. Usually, numerics for channel-specific commands do contain the channel name. For example, raw 482 is <mynick> <channel> You're not channel operator. A similar case, but not as problematic, is raw 974 <mynick> <flag> <nick> is a channel admin/owner/network service, which is a failure raw for a MODE command, it's somewhat less obvious as the 972 but it could also have the channel name since MODE is bound to a channel. Another remark about this 974 one is that the <flag> parameter doesnt have + or -, just the flag character itself, at the moment I use a ? wildcard before it, but there is surely a bigger chance for mismatching the returned message to the command that was sent. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Numeric 972 is an extension of numeric 482 based on my knowledge. But should we add the #channel parameter for numeric 972 just because they serve the same purpose? Doesn't seem difficult from my side. Edit: It is also worth noting that mIRC displays numeric 482 on the channel's window hence omitting the #channel parameter. |
