Bug #5224
closedIncorrect IRCv3 SETNAME support
0%
Description
On the latest public beta 4.0 20210124 the IRCv3 SETNAME support is incorrectly handled.
1) Whenever ANY client uses /setname new name here, AdiIRC will display to the user Your fullname is mow new name here (it should only display it for one's own changes)
2) Minor spelling mistake: now is misspelled as mow
3) Whenever a realname change occurs by any client, AdiIRC attempts to echo a 2nd line, with the contents of $2- from SETNAME
example: user Koragg on IRCCloud executes /setname AdiIRC Has Broken SETNAME Support
output: user AwayLurker on AdiIRC sees the following 2 lines:
[16:52] * Your fullname is mow AdiIRC Has Broken SETNAME Support
[16:52] * Has Broken SETNAME Support
expected output: nothing, as it is another user who changed their realname, and not the AdiIRC client/user.
example of own /SETNAME change:
[17:06] * Your fullname is mow AdiIRC Has Broken SETNAME Support
[17:06] * Has Broken SETNAME Support
expected output: just the first line, NOT the additional * Has Broken SETNAME Support
where to test: any network with IRCv3 SETNAME support where /SETNAME is available to users. Suitable testing grounds: irc.snoonet.org (only given as to have a reliable testing network, NOT as advertisement.
Updated by Per Amundsen almost 4 years ago
- Category changed from Scripting to Irc
- Status changed from New to Resolved
- Regression changed from No to Yes
Should be fixed in next beta.
Updated by Per Amundsen almost 4 years ago
- Status changed from Resolved to Closed