I don't have a BNC/ZNC, account so I can't see how that behaves unless someone wants to give me a free account

Being able to autojoin multiple servers without manually choosing them is a great idea, but the script will need to make a few changes to overcome mIRC quirks.

* The settings added to this script will behave differently, depending on whether mIRC thinks your entry matches an entry inside a group.

* If server/port is a range, mIRC chooses a number randomly from the range, but retries that number repeatedly. But if the server is in a 'group' defined with a range, mIRC will instead randomly choose a port each time.

* If server/port is in a group, the retry will retry other servernames in that group, which may be unexpected.

Solution: The server entries should add a field for 'group', then use that if it contains a value.

The interface could use a little improvement to 'idiot proof' user input.

* it silently ignores input when I use a network name containing a space
* the label says server/port without indicating the port is optional, and if I use irc.dal.net/6661 as instructed, it fails.
* it should let me rearrange the order in which networks connect, and not show me a sorted list that's different than connect order. i.e. I don't connect my group of networks alphabetically. Using them in 'item' order isn't good either, since the sort order of items changes as new are added, even if you use buckets=1.
* either it should let you see the connect button without entering an altnick, or it should keep you from using altnick==primary
* It shouldn't commit edits to a server entry until you click 'apply', which is grey'ed out until something changes.
* If the new 'group' field contains a value, you shouldn't need to fill anything else in, since it would be getting values from servers.ini, and this script is only used for connecting to them. The exceptions would be things not in servers.ini such as Oper Login

Using groups also helps for networks I've used where I need to have multiple servernames in the retry list for 1 network.

Ask: It would help to have a 'help' button next to each item, to give tips and examples, so novices know what some of these items do. i.e. do you need to list server AND port, what should go in 'services command', etc.

This lets you have the Fixedsys font at more sizes than the original FIxedsys gives. At the same font size offered by Fixedsys, the ASCII text is basically the same.

You'll need to test various sizes to see if they work for you. At some sizes, the characters have a shadowing effect that can affect visibility.

If using this as your scripts editor font, it gives a visible [B] [C] [O] for the Ctrl+B Ctrl+K and Ctrl+O hotekeys. What would make it even more useful would be if it gave [R] [U] [I] symbols for the Ctrl+R Ctrl+U and Ctrl+I symbols too.

While it does map additional unicode characters, this can be a drawback in programs which do font linking. For example, the chess pieces icons don't exist in Fixedsys, so it font-links for them. In NoLiga, it contains icons for the chess pieces which are not the same quality as the ones in MsGothic, so the Queen looks like a profile of Bart SImpson.

Example: //echo -a $replace(R N B Q K B N R,R,$chr(9814),N,$chr(9816),B,$chr(9815),Q,$chr(9813),K,$chr(9812))

If your queen looks like Bart without using any Excelsior font, mIRC font-links the "Fixedsys Excelsior 3.01" font name without the 'No Liga", so you can uninstall that font name and install this font name, and be able to use this font without it affecting your font linking.

If you want to spice up your mIRC's display, give this script a try, channels now use a black background + event colors that contrast against black.

Channel messages now have their own column, with right-justified next to the msg, with options to change it to [nick] (nick) {nick} etc. Event messages are changed, like *QUIT showing how long they were in channel.

Status Windows and #channels have a green watermark, can be disabled or changed color. The script comes with Liberation Mono font in case your Windows doesn't already have that. You'd need to install the font before mIRC would use it.

Worth using the script for just 1 feature is the nicklist coloring the nicks by their status, as well as how long they've been idle in the channel.

Most of the options can be toggled on/off, so you can decide how many of the features you wish to use. Explore "Theme" menu in channel rightclick menu to test features like acronyms that are disabled by default.

Before installing, make a copy of your mirc.ini in case it doesn't restore all settings. For example, it removes any channel-specific fonts, and when you unload the script it restores your channels to use the font formerly used by your Status Window, absent any bold or italic settings. While the script is installed, you can use channel-specific fonts if needed.

I didn't install the Liberation Mono font that came with the script, because I already had that Font installed having a newer timestamp and larger filesize.

This script has already had several significant improvements since I've started testing it, and I'm sure future updates will make this review obsolete. Suggested areas for future updates:

1. The black background contrasts well against default colors 8/9/11 but not so well against 2/5/12. Perhaps define indexes 2/5/12 to use slightly different RGB colors so blue-2 and the others can contrast better against black.

2. Add an acronym viewer/editor to add/remove acronyms. So people can add their own acronyms, or delete ones they don't want. Don't disable acronym touching punctuation. Have a code to override expansion, like .bbl cancels the expansion without showing the period.

4. Menu choice to edit the idle-time boundaries for the different layers of idle nick colors. Would also serve as a reminder to the user describing what the colors all mean.

Give it a try!

test

Simple script that works at least as far back as v6.35, and can be modified to count other things that mIRC reports only by individual server. For example you can change $!chan(0) to $!ial(*,0) to count your total IAL across all servers.

This counts only at networks where you're connected, and counts open query and channel windows even if the other nick isn't there, and even if you are not in the channel nicklist.

You can move these aliases into any of your existing *.MRC scripts to avoid adding another to your scripts list. If you move it to your alt+D aliases file, be sure to remove the "alias" keyword too.

You might want to rename them to something like totalchans or allchans or chancount

Similar to the built-in $totp() except the number can be forced into a range more precise than simply limiting the number of digits from 3-9..

If the value in the next time interval needs to be kept secret from others, you should treat the 4th parameter like a password.

Something that $totp() does is use 1 of the unused digits of the $sha1 hash digest to decide which of the other hex digits it uses to calculate the random number, but that's just guarding against a theoretical unknown bias in the numbers, and I don't think it's needed here. This function uses a 52-bit value as the numerator, while $totp uses 'only' 31 bits.

Negative numbers are fine, but be sure to not use fractions, as that can allow numbers to be returned outside the min/max range.

It assumes you used the manager's menu to install it, and is confusing if using the download link then manually /load it. There's no dialog or right-click menu. Nor message saying install was successful. The manager menu doesn't say so, but to see this script's settings dialog you go to the "installed" tab and double-click on this script. Or type in editbox: /wiv_sets

The description is a little misleading, saying "command that you enter", but really means a message someone ELSE types into #channel. For "!ipv6 5.39.78.90" this script sends the answer to THEM as a notice. For "@ipv6 5.39.78.90" output is instead sent as a /msg to the entire channel.

Settings dialog's text "Display all the module using output messages" really means:

Lets script reply to YOU typing !ipv6 or @ipv6 keywords in the #channel's editbox.
Lets you see the script's answer in channel to the @ipv6 keyword. But it hides reply to someone else using !ipv6.

Script depends on ultratools.com for the reply, so wrong answers are their fault. I tested several ipv4's and it replied with an ipv6 address, which /dns resolved to the same hostname as /dns ipv4. However for my own ipv4, it returns the wrong ipv6 that's not in my "ipconfig /all", but is the same wrong answer at that website.

Things to be aware of.

1. The script opens urls in your browser without indicating that's what it will do. ie in settings the menu item 'help' doesn't show help text. Instead, it opens a browser link to the module manager's install page, where there's no 'help' for this script. For me, the link opens into the browser's active tab, not opening a new tab. Script can't install without the manager already being installed, this link isn't helpful.

2. Manager won't let you click to upgrade the script without turning off mIRC's 'initialization warning' option, which shouldn't be required if you aren't using the option to automatically install update.

3. If using the manager to "Unistall" this module, it also deletes this .mrc from disk, which may not be what you want to happen. You can install it again from the manager later, but it forces you to accept an upgrade to the module. Can avoid that by using /unload or the Remote Editor's menu.

Possible additional feature:

Channel and Nicklist right-click menus - instead be a dropdown menu having context-related choices, like choices for "add/remove channel/nicks to/from the ignore". Also, menu choice which lets you display lookup for $snick which are valid ip4's, with display only to self.

Since the top of the script doesn't contain any "how to use" help message, :LOAD: event could show a getting-started message to help someone get started, or where to get it.

Except for missing things like 'english' spin, this plays very similar to the pool game at the former 'Yahoo games'. Glitches mentioned in the description are few/far between, though I did once have a cueball not reset after a scratch, where it eventually came dribbling out of the pocket. There's no menu for this game, but you can easily add it like:

menu status {
Play Billiards!:b2
}

Suggestions for improvements, include a $style check for the current setting when browsing the B2 menu.
Also have a cheatsheet in the menu to remind us of the ball sequence in 9-ball.
Also an option to remove the logo in the middle of the board
Have an option to remember the prior setting, including the location/angle/power of the last shot. This could permit to either save the in-progress game to disk, or add an Undo feature. This would also allow people to submit bug reports that could be reproduced.
Also have a game editor which would allow creating a table layout for testing trick shots.

I found websites claiming to list proxy addresses, so I took ipv4's from those sites and fed them to this script, which does report them as proxies. This script also reports more info about the ip's, including being in different types of proxies. Unlike the other module showing the wrong ipv6 for my $ip, this one did not report me as being a proxy. Yay.

There can be a delay of several hundred milliseconds between when it does 'jsonopen' and its last $json() call, so for normal usage it won't cause a lag. But if your script is using this against all nicks during a join-flood, you can expect a combined lag.

Most of the things in my review of the ipv6-checker module apply here, since this module is very similar to the other one, except it instead reacts to someone typing in channel "!Proxy ipv4" or "@Proxy ipv4". The confusingly worded option related to displaying output also has the same effect here - it affects being able to see your responses in channel to "@Proxy ipv4", but you can't see your /notice responses to "!Proxy ipv4".

The description says you can reach the configuration via the menubar or /wsc_sets, but the command is actually /wxc_sets, and the menubar item doesn't appear until you go into options and enable it.

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.

Works like it says!

Possible improvements could include a cooldown timer to block abuse of your bot, and a customizable blacklist so you can choose to permit youtube and/or block other sites.