Show users the RESV reason when they attempt to join channels that are resv'd #56
Conversation
Change RESV to show users the resv reason when attempting to join a resv'd channel (via the 479 numeric) Add canned messages to other uses of 479
|
Hmm, existing resv reasons may not be suitable for display to normal users. Perhaps display something to a user only if there is an explicit oper reason and/or make it configurable? |
|
I considered the possibility of handling it the same way klines are handled, with a pipe character seperating the user-visible reason and the oper-visible reason. Since there's interest in this behavior I'll try to update it tonight to include that. |
…om user reason) Applied same change to numeric 432 (ERR_ERRONEUSNICKNAME), given when a user tries to use a resv'd nickname Updated the oper help text for resv to reflect the new syntax
|
Oper reasons for RESVS are implemented. Additionally, I applied the same sort of change to numeric 432 (ERR_ERRONEUSNICKNAME) which is displayed when a user attempts to NICK to a resv'd nick. Memory-safety is easy to assess (I null out the pipe seperator byte, append the reason, and then restore it when broadcasting to users, no intermediate buffers are used) |
|
What is the status on this? |
|
Are legacy RESVs converted to be oper-only? If so, I would be willing to merge it. |
I changed form_str(ERR_BADCHANNAME) to allow the author to specify the message used displayed to users, which is now:
"%s :Illegal channel name (%s)"
I keep hearing how nice it would be if charybdis did this so I figured why not .