Snippets Project Page
Author: spectre
Original: Raccoon
Added: 5y
Updated: 5y
mIRC: 7.55
Hits: 1,769
Downloads: 48
Review: maroon
Size: 801B
2 0
Login to vote.
psyBNC multi network fix
v1.0
This script restores psyBNC's functionality with mIRC 7.53+ which introduced CPRIVMSG/CNOTICE support.
That functionality in a nutshell broke psyBNC's multi-network support if the primary network defined in psyBNC supported that feature set.
This script intercepts NUMERIC 005 and filters out the problematic server features.
It would be great if someone updated the "psyBNC 2.4 beta 2" source code and filtered out these features on psyBNC itself so a mIRC fix is not necessary
Download
JSON
▲ Review
▼ Source
; psyBNC multi network fix v1.0 ; Date: Feb 27th 2019 ; Code snippet by Raccoon ; ; spectre's note: This script restores psyBNC's functionality with mIRC 7.53+ which ; introduced CPRIVMSG/CNOTICE support. ; That functionality in a nutshell broke psyBNC's multi-network support if the ; primary network defined in psyBNC supported that feature set. ; This script intercepts NUMERIC 005 and filters out the problematic server features. ; It would be great if someone updated the "psyBNC 2.4 beta 2" source code and ; filtered out these features on psyBNC itself so a mIRC fix is not necessary! On *:PARSELINE:in:& 005 *:{ noop $regsubex(foo,$parseline,/\s(?:CPRIVMSG|CNOTICE|NAMESX|WHOX)/g,,&foo) .parseline -ib &foo }
Changelog:
0
0
Review: maroon
I don't use PsyBNC, so am unable to test it there. This snippet works by checking for an inbound server message where the 2nd token is 005. Any tokens which are exactly those 4 words are stripped from the line, and the edited line is sent for mIRC to 'see'. If mIRC can't see these tokens in the 005 message, then it shouldn't change its behavior in response to these network settings.
You should be able to paste this snippet into any other existing script, as long as you place it on a line above any other PARSELINE event handlers.
It might be possible to selectively apply this per network, depending on whether you can reliably test $network or the server name at this stage of connection.
I don't use PsyBNC, so am unable to test it there. This snippet works by checking for an inbound server message where the 2nd token is 005. Any tokens which are exactly those 4 words are stripped from the line, and the edited line is sent for mIRC to 'see'. If mIRC can't see these tokens in the 005 message, then it shouldn't change its behavior in response to these network settings.
You should be able to paste this snippet into any other existing script, as long as you place it on a line above any other PARSELINE event handlers.
It might be possible to selectively apply this per network, depending on whether you can reliably test $network or the server name at this stage of connection.