irc_437(forbidden /nick due to a ban) only shows up on the channel

[zertap]

Say, you are currently on 2 channels, a and b.
You are currently viewing a.
Your nick is bar.
You change your nick on the server to foo.
Then you try to change your nick back to bar.
It fails, and you don't get any message about why on your current channel nor the server log.

This is due to nick foo being banned on the channel b. While on any channel with a banned nick, you cannot change nick on the server (At least, true to Rizon).

Problem is that weechat only informs you about this on the channel that has the affecting ban. Unless you go look at the channel b, you will never know why you cannot change your nick.

First place you'd go look when things go wrong like this, is the server log(after the current channel you are monitoring). I was pretty confused about what was going on, and figured it out by looking at the raw log.

on WeeChat 0.4.4-dev (git: v0.4.3-475-gb174b3c)

[zertap]

In my case, the reason was channel mode +M, which is:

'ModReg'. This will prevent any user who isn't a owner,
protected, opped, half-opped or voiced (+q/+a/+o/+h/+v) from
talking in the channel if they havent identified to their
nickname.

[0xallie]

Non-standard numerics are so much fun... This is numeric 435 (ERR_BANONCHAN) on charybdis-esque IRCds, which use 437 (ERR_UNAVAILRESOURCE) for a different thing: Return when the target is unable to be reached temporarily, eg. a delay mechanism in play, or a service being offline.