Forums Active Threads Past Year

This is cool.
Thank / Спасибо.

Thanks, for $pbkdf2() the hash can be: md5, sha1, sha256, sha384, sha512, and for $argon2() the hash can be: 2id, 2i, 2d. These have been added to the help file.

Dear mIRC User,

mIRC v7.83 has been released today.

This is a small update that adds features and addresses a number of issues reported by users since the last release. It includes improvements, changes and fixes, including:

Fixed NickServ bug that prevented /nickserv from logging on when connecting.
Fixed IPv6 parser bug that affected /dcc commands and other features.
Fixed listbox text not being displayed correctly with different DPI settings.
Added support for key derivation functions pbkdf2 and argon2 as identifiers.
Added /drawdll command that allows a custom DLL to draw to a picture @window's bitmap.
Added $encode()/$decode() 'y' switch that Punycode-encodes/decodes text.
Added support for internationalized domain names when resolving addresses.
Updated CA root certificates cacert.pem file.

How to upgrade?
mIRC is distributed in an installer that installs mIRC on your computer for you. Simply download and run the installer from the download page on the mIRC website. Follow the instructions the installer gives to you. When upgrading all your old settings and scripts will stay as they were, if you want that. Read the questions the installer asks with care and nothing can go wrong. You will be chatting with the new mIRC in no time. If you get stuck or if you want to find out more about a certain feature, just click on a Help button or browse the Help file and you should find lots of hints to help you out.

Where to download?
As always, the latest version of mIRC can be downloaded from the download page on the mIRC website.

Registering mIRC
As you know, mIRC can be downloaded freely and evaluated for 30 days. If you find that you enjoy using mIRC, it would be great and much appreciated if you registered your copy. This licenses you to use your copy of mIRC and helps to support our continued work on mIRC. You can find out how to register here.

Full list of Fixes, Changes and Additions.
For a more detailed list of recent changes, please see the whatsnew.txt file. You will need to read through the help file to learn more about these changes and their impact. Some changes are obvious, some need getting used to - please take your time to play with them and see how they work. May we invite you to use these forums for all questions you might have? The forums offer great help with everything related to mIRC!

Thanks for using mIRC, have fun on IRC!

Thanks for the feedback. The behaviours you describe are how the (optional) feature has always worked across all dialogs. The custom dialogs are simply using the existing functions for this.

I have had to make more changes to the custom dialog optional keyword parser as there was an issue with the order in which it was being parsed in the custom dialog code. At this point, I have decided to remove this feature for now and revert to the 7.82 custom dialog code, as it still needs more testing and will delay the release that was planned this week. I will add it back in a future beta cycle.

There are no betas available for testing at this time. Please download the latest version of mIRC from the mIRC website.

I regualrly use Undernet without any trouble but the other day, I tried to log in and recieved this error message:
-
irc.undernet.org HTTP/1.1 303 See Other
-
irc.undernet.org Location: https://block.malwarebytes.com?lic=...186.233.185.155&url=irc.undernet.org
-
Connection: close

It kept trying to connect and the message continued to appear. I am able to connect to other servers, however.

PLS NOTE: This began when i installed the latest udate of MIRC 7.82

Can you help me connect to Undernet? Thanks!

Thanks, I have extended the nickserv code to also use the username if it is specified in the server dialog. This change will be in the next beta.

Couple notes.

Your suggestion is great and is an obvious improvement upon the original, too simple, suggestion.
But what you proposed syntactically speaking doesn't work: if you want an optional text for the editbox then you wouldn't be filling AND a ghost text AND the original field for the editbox's text.

The new beta only implements a default (optional) text, which, practically speaking, is quickly limiting, a better implementation which doesn't break the current syntax would be

With the optional option and empty value for the text, it would then show the default (optional) as an optional/ghost text.

Whereas this would then show the custom optional/ghost text "custom"

And we do need a /did switch to get that behavior.




It would also be nice to have an option to get a default value, so basically a text that is selected, which, when in focus, would automatically overwrite itself.
This can't be scripted.

As of 2025/11/06, the beta post notes:

However, that post/page is transitory in nature and so is often blank. Fortunately, versions.txt is persistent and also notes it (emphasis added):


(It doesn't look like a 32-bit ARM is planned, so those of us with RaspberryPi 2 servers are out of luck!)

Being able to drag and move channels around has been suggested a lot before.

Being able to see emoji is a font issue and mIRC does fallback to different fonts when a character isn't available in a font so you should be able to see emoji, you can try to set your font to 'segoe ui'.

As far as using emoji you can use this script which lists all the 'face' emoji in a custom windows, double clicking copy to clipboard.

alias emoji {
if ($window(@emoji)) { window -a @emoji | return }
else {
window -odl @emoji -1 -1 100 500 verdana -28
var %a 1,%l 128512 128515 128516 128513 128518 128517 129315 128514 128578 128579 129760 128521 128522 128519 129392 128525 129321 128536 128535 9786 128538 128537 129394 128523 128539 128540 129322 128541 129297 129303 129325 129762 129763 129323 129300 129761 129296 129320 128528 128529 128566 129765 128566 128527 128530 128580 128556 128558 129317 129768 128578 128578 128524 128532 128554 129316 128564 129769 128567 129298 129301 129314 129326 129319 129397 129398 129396 128565 128565 129327 129312 129395 129400 128526 129299 129488 128533 129764 128543 128577 9785 128558 128559 128562 128563 129770 129402 129401 128550 128551 128552 128560 128549 128546 128557 128561 128534 128547 128542 128531 128553 128555 129393 128548 128545 128544 129324 128520 128127 128128 9760 128169 129313 128121 128122 128123 128125 128126 129302
while ($gettok(%l,%a,32)) {
aline -l @emoji $chru($v1)
inc %a
}
}
}
alias chrU {
var %chr = $iif(U+* iswm $1, $base($mid($1, 3), 16, 10), $1)
if (%chr isnum 65536-1114111) return $chr($calc(55232 + %chr / 1024)) $+ $chr($calc(56320 + %chr % 1024))
return $chr(%chr)
}
menu @emoji {
dclick : clipboard $sline(@emoji,1)
}

Finally i made sum investigations.

When mirc is using a soundcard, i tested it with "rme multiface" and now "creative pebble x speaker with internal usb soundcard", in both cases a running mirc eats 2 watt more power.

Now i had the idea to block mirc to access windows audio with sandboxie.
So i added "ClosedIpcPath=\RPC Control\AudioSrv" to the sandboxie.ini.
Then i start mirc inside sandboxie and voila ... 2 watt less energy consumption (25 Watt, instead of 27).
Maybe it isnt a very exact measurement because i use the power consumption measurement of an apc ups.
But it clearly shows that an always "touched" windows audio can generate unnecessary power consumption.

No matter, i can live with the sandboxie workaround

thx.

The issue is that when passing $6 = 1, it assumes it will work for everyone. Everyone is the hash key, and $1, $2, $3, $4 is the hash value. If I pass the same message to different channels, one will overwrite the other because the key is the same. The problem seems to be there.
I avoid $unsafe in the scon or timer when I know the value won't have problems.
The alias $sbtok builds an $aliasname(parameters) to be used in a timer or scon, for example:
noop $sbtok(44,echo,$null,-a,test) is the same as $echo(-a,test).

SBTOK = String Builder token

Your comment about the treebar had me go down the rabbit hole and I thought I would compare fonts for that and the switchbar to old backups and there's the answer. The font settings had changed.

Previously I had switchbar set to Microsoft Sans Serif 8 and the treebar Segoe UI 9. I dont ever recall changing the font on those so I wonder how old they are? They must have been default at one time?

See here for a recent discussion on this topic.

I appreciate your time and response. If mSL is baked into the gui then I wouldn’t even consider doing it, sounds like to much of a challenge.

Great! Thank you!

Hello Khaled,

I’ve noticed that IDN (Internationalized Domain Names) like irc.aşk.net are not resolved in the current mIRC versions (e.g., 7.81).

Can you please consider adding support for IDNs so users can connect to servers using Unicode domains directly?

This would greatly help users from many languages and regions.

Thank you for your great work on mIRC.

Dear mIRC User,

mIRC v7.82 has been released today.

This is a small update that adds features and addresses a number of issues reported by users since the last release. It includes improvements, changes and fixes, including:

Added $tip() support for permanent tray tips.
Added support for specifying a username for SASL Logins.
Added SASL disconnect on error server option.
Fixed percent encoding/decoding memory bug that would have caused intermittent crashes.
Fixed touchpad speed/sensitivity when scrolling in different types of windows.
Fixed handling of swapped mouse buttons in different contexts.
Fixed $urlget() crash bug when credentials are passed in URL.
Fixed features that were using the wrong default GUI font under Windows 10/11.
Fixed various Aero theme bugs relating to Windows display scale and text size options.
Updated all code and libraries in preparation for future 64bit / ARM64 versions.
Updated libraries to LibZip v1.11.4, LunaSVG v3.5.0, and TagLib v2.1.1.
Updated from the OpenSSL v3.0.x branch to v3.5.4.
Updated SSL code to remove use of 30+ deprecated OpenSSL APIs.
Updated CA root certificates cacert.pem file.

How to upgrade?
mIRC is distributed in an installer that installs mIRC on your computer for you. Simply download and run the installer from the download page on the mIRC website. Follow the instructions the installer gives to you. When upgrading all your old settings and scripts will stay as they were, if you want that. Read the questions the installer asks with care and nothing can go wrong. You will be chatting with the new mIRC in no time. If you get stuck or if you want to find out more about a certain feature, just click on a Help button or browse the Help file and you should find lots of hints to help you out.

Where to download?
As always, the latest version of mIRC can be downloaded from the download page on the mIRC website.

Registering mIRC
As you know, mIRC can be downloaded freely and evaluated for 30 days. If you find that you enjoy using mIRC, it would be great and much appreciated if you registered your copy. This licenses you to use your copy of mIRC and helps to support our continued work on mIRC. You can find out how to register here.

Full list of Fixes, Changes and Additions.
For a more detailed list of recent changes, please see the whatsnew.txt file. You will need to read through the help file to learn more about these changes and their impact. Some changes are obvious, some need getting used to - please take your time to play with them and see how they work. May we invite you to use these forums for all questions you might have? The forums offer great help with everything related to mIRC!

Thanks for using mIRC, have fun on IRC!

Thanks wims, i used original as well but was hoping your shorter version could be made to work but from what i understand from you is it can't be made to work, if i understood well.


BTW these are the aliases for it :


Much appreciated,

Simo.

I fixed some errors in the dll, there now no warnings.

Thanks for your bug report. I was able to reproduce this issue on a touchpad here. Excessively fast/sensitive two finger scrolling on touchpads seems to be a common issue with applications. In this case, mIRC was not handling how a touchpad sends WM_MOUSEWHEEL delta values in small increments, that need to be accumulated, which is different to how a mouse sends the same message. I have made a change to the next beta that should hopefully resolve the issue.

Figured I would use the General Discussion forum to shamelessly look for anyone, even old timers, still residing within this playground How is everyone?

You can find the scripts editor in the Tools menu in the mIRC menubar.

Once you open the scripts editor, you will need to click on the Aliases tab, then click View in the menubar to see which files are loaded.

You will then need to do the same thing with the Popups, Remote, Users, and Variables tabs.

If you see a servers.ini files listed in the View menu, you will need to select it, then click the File menu in the menubar and click on Unload.

Good idea, I support this request.

Oh that's a tough one.

Honestly, given mIRC there are probably more people that benefit from having Windows XP support than those that would benefit from having ARM support (after all, ARM64 devices can run x86 code, even if sub optimally).

I'd probably lean on a poll or system check from folks to get an idea of the number.

However, I definitely still recommend getting an x86-64 version of mIRC up and running if possible! As there are enough security benefits under the hood in Windows these days to make that worthwhile.

To be fair, though, maintaining Windows XP support now would be similar to maintaining Kenbak-1 support when mIRC first came out.