Partyline sometimes messages users instead of outputting to the channel #253

New Issue

2026-10-05T04:07:55+02:00

adam commented

2026-10-05 04:07:55 +02:00

Could be a client bug, not sure.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/567239-partyline-sometimes-messages-users-instead-of-outputting-to-the-channel?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).

Could be a client bug, not sure. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/567239-partyline-sometimes-messages-users-instead-of-outputting-to-the-channel?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 closed this issue

2026-10-05 04:07:55 +02:00

adam commented

2026-10-05 04:07:56 +02:00

A user brought this up in #hexchat so if that is your client who sees this I'll just relay the info.

HexChat relies on the 005 reply to know the prefixes of channels so if one user is not connected to a server it defaults to #&!+ and znc uses ~. So it will treat incoming messages from that prefix as a PM.

Perhaps this will be improved in the future but for now to work around this you can:

Connect to a server.
Write a script to always print them in a channel tab.
Run /recv :irc.bnc.im 005 <yournick> CHANTYPES=~# on connection.

A user brought this up in #hexchat so if that is your client who sees this I'll just relay the info. HexChat relies on the 005 reply to know the prefixes of channels so if one user is not connected to a server it defaults to _#&!+_ and znc uses _~_. So it will treat incoming messages from that prefix as a PM. Perhaps this will be improved in the future but for now to work around this you can: - Connect to a server. - Write a script to always print them in a channel tab. - Run `/recv :irc.bnc.im 005 <yournick> CHANTYPES=~#` on connection.

adam commented

2026-10-05 04:07:56 +02:00

@TingPing
ZNC Should be rewriting chantypes:
https://github.com/znc/znc/blob/master/modules/partyline.cpp#L192

And it does seem to be for me on HexChat ( I havent had this issue in ages, I think there were more conditions to cause it):
* CHANTYPES=#~

Emphasis on sometimes

@TingPing ZNC Should be rewriting chantypes: https://github.com/znc/znc/blob/master/modules/partyline.cpp#L192 And it does seem to be for me on HexChat ( I havent had this issue in ages, I think there were more conditions to cause it): * CHANTYPES=#~ Emphasis on sometimes

adam commented

2026-10-05 04:07:57 +02:00

@md-5 It does rewrite them. This scenario only happens when you are not connected to a server.

@md-5 It does rewrite them. This scenario only happens when you are **not** connected to a server.

adam commented

2026-10-05 04:07:58 +02:00

That would explain why the buginess stopped :p

That would explain why the buginess stopped :p

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#253