Nick and AltNick don't work, when different case of global nickname #637

New Issue

2026-10-05T04:35:25+02:00

adam commented

2026-10-05 04:35:25 +02:00

In my global setting, I have my IRC nickname set to "April". However, on one network, I'd like it to be "april" (lowercase).

If I try to set Nick and AltNick to "april" in the network-specific configuration page, it just resets back to the default of "April". If I add them directly to znc.conf, they get ignored and deleted upon startup.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28195272-nick-and-altnick-don-t-work-when-different-case-of-global-nickname?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

In my global setting, I have my IRC nickname set to "April". However, on one network, I'd like it to be "april" (lowercase). If I try to set Nick and AltNick to "april" in the network-specific configuration page, it just resets back to the default of "April". If I add them directly to znc.conf, they get ignored and deleted upon startup. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28195272-nick-and-altnick-don-t-work-when-different-case-of-global-nickname?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:35:26 +02:00

I think this is correct behavior.
AltNick is used when ZNC can't use the primary nick when connecting to server (e.g. if the nick is used by someone else). If "April" can't be used, "april" can't be used either, because IRC protocol compares nicks case-insensitively.

I think this is correct behavior. AltNick is used when ZNC can't use the primary nick when connecting to server (e.g. if the nick is used by someone else). If "April" can't be used, "april" can't be used either, because IRC protocol compares nicks case-insensitively.

adam commented

2026-10-05 04:35:27 +02:00

Right, but April and april both can be used; that's not the problem. I want my nick to be lowercase on just one network, but ZNC ignores setting it at a network level if it's the same name (but a different case) of the global nick.

Right, but April and april both can be used; that's not the problem. I want my nick to be lowercase on just one network, but ZNC ignores setting it at a network level if it's the same name (but a different case) of the global nick.

adam commented

2026-10-05 04:35:28 +02:00

I've experienced the same situation. There's some network(s) I'd like to have a different casing nick on too. As a work around, I have my perform module /nick to the different casing, but I'd much rather see the network specific configuration handle the different casing request. For example, I'm using PlasmaStar on most networks, but on at least one network, I'd like it to be plasmaStar, without having to use some auto-perform line.

I've experienced the same situation. There's some network(s) I'd like to have a different casing nick on too. As a work around, I have my perform module /nick to the different casing, but I'd much rather see the network specific configuration handle the different casing request. For example, I'm using PlasmaStar on most networks, but on at least one network, I'd like it to be plasmaStar, without having to use some auto-perform line.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#637