mIRC 7.85 and 7.86: WebSockets, IRCv3 replies, account bans and per-server settings
mIRC 7.86 (29 October 2026) and 7.85 (9 September 2026) bring WebSocket connections, IRCv3 replies, account bans, channel context, per-server IRCv3 settings and OpenSSL security updates. Here is what is new.
mIRC 7.85 and 7.86: WebSockets, IRCv3 replies, account bans and per-server settings
mIRC 7.86 was released on 29 October 2026, seven weeks after mIRC 7.85 came out on 9 September 2026. Taken together, the two releases are the biggest step mIRC has made towards modern IRC in a long time: WebSocket connections, IRCv3 replies, account-based bans, channel context and per-server IRCv3 settings, plus the usual round of security updates.
This article walks through both versions, explains what each new feature actually does, and tells you whether you need to update.
At a glance
| mIRC 7.85 | mIRC 7.86 | |
|---|---|---|
| Released | 9 September 2026 | 29 October 2026 |
| Type | Feature release | Fixes, security, scripting |
| Headline | WebSockets, +reply, account bans |
Per-server IRCv3 settings |
| OpenSSL | 3.5.8 | 3.5.9 |
| Changelog entries | 24 | 12 |
mIRC 7.85 (9 September 2026): the IRCv3 release
WebSocket connections
mIRC can now connect to an IRC server over WebSockets. Enter a server address prefixed with ws: or wss: (the TLS variant) and mIRC uses a websocket instead of a plain TCP connection.
Why it matters: WebSockets were ratified as an IRCv3 specification in February 2026, mainly so that browser clients can talk to IRC servers. For a desktop client the benefit is reach. A websocket connection looks like ordinary web traffic, so it often works on networks where the classic IRC ports (6667, 6697) are blocked, and it lets you connect to servers that only expose a websocket endpoint.
Replies with IRCv3 +reply
Threaded replies are one of the things people miss most when they come to IRC from Discord or Matrix. mIRC now supports the IRCv3 +reply client tag, and it does so without changing how you type:
- In a channel window, start your message with
nick:as you always did. - If the last message from that nick carried a message ID, mIRC attaches that ID to your message as a reply.
- When a reply arrives, mIRC briefly highlights the message it refers to in the same window.
Clients that understand +reply can show the two messages as linked. Everyone else just sees a normal "nick: text" line, so nothing breaks for older clients. It only works on servers that support message IDs and message tags.
Bans by account: EXTBAN and ACCOUNTEXTBAN
A classic host ban is easy to dodge with a new IP address. Many networks therefore support banning a services account instead, but the syntax differs from server to server. mIRC now reads the server's EXTBAN and ACCOUNTEXTBAN tokens and builds the correct ban for you:
/ban -a #channel Nick
/ban -alooks up the nick's account name in the Internal Address List (IAL) and bans or unbans that account with the right prefix for the network.- If no account is found, it falls back to a wildcard ban.
- Scripters get three new
$ibl()properties:.prefix,.maskand.account, which return the parsed parts of an entry in the ban list.
Channel context
Bots and services often answer a channel command with a private NOTICE, which then lands in a different window from the conversation it belongs to. The IRCv3 channel-context tag (mIRC's changelog calls it context-chan) lets the sender say which channel a private message relates to.
When a PRIVMSG or NOTICE carries this tag, mIRC routes it to that channel window. Your existing settings and already open windows take priority, so a query window you have open keeps receiving its messages.
no-implicit-names
Normally a server sends the full nick list (NAMES) every time you join a channel. On large channels and slow or metered connections that is a lot of data. With the new /server -ircv3 switch you can turn on no-implicit-names for a connection, and the setting stays in place for that status window until you change it.
A more readable interface on Windows 10 and 11
- All dialogs now use the default Windows GUI font. For custom script dialogs the new font applies only to dialogs that use the
mapordbuoption, so pixel-based layouts are not disturbed. - The Windows 11 Text Size accessibility setting is respected. Text scaling and alignment were fixed in several places and dialogs now follow the setting too.
Alt+Din the Connect dialog deletes a server, with a confirmation prompt.- The Scripts Editor minimize button is disabled in non-desktop mode.
Getting ready for 64-bit
The changelog lists fixes for "various issues relating to 64-bit/ARM64 in preparation for a future 64bit release". There is no date and no 64-bit download yet, but it is the clearest sign so far that a native 64-bit mIRC is on the way.
Other changes and fixes in 7.85
- STS: if you previously accepted an invalid certificate for a server, strict transport security no longer blocks the connection.
- Server ports: port parsing is stricter and accepts only valid formats, ranges and prefixes.
- Hotlinks: a trailing period is no longer treated as part of an address, so links at the end of a sentence open correctly.
- Numerics: numeric 344 in WHOIS replies on InspIRCd is displayed properly, and numerics 697 and 698 are shown in the channel window.
- ZNC: away status is handled correctly when numeric 301 arrives without an away message.
- Logon: CAP parsing for
echo-messageandlabeled-responsewas updated. - Scripting: optional text in custom dialogs no longer triggers editbox events.
- Libraries: OpenSSL 3.5.8, TagLib 2.3.2, UTF8-CPP 4.2.0, a new CA root certificates file and a refreshed servers list.
mIRC 7.86 (29 October 2026): polish, security and scripting
Per-server IRCv3 settings
7.85 introduced /server -ircv3 for one option. 7.86 turns it into a proper per-server setting that covers three IRCv3 capabilities:
| Option | What it does |
|---|---|
echo-message |
the server sends your own messages back to you, so you see them exactly as others do |
no-implicit-names |
the server does not send the nick list automatically on join |
server-time |
timestamps come from the server instead of your local clock, which keeps history and bouncer playback in the right order |
server-time is enabled by default. An option is turned off by prefixing it with !, for example !server-time. This is useful when one network or bouncer misbehaves with a capability and you do not want to change the setting for every other network.
New identifiers for scripters
$spaces(command, parms)reproduces the behaviour of the well-known spaces.dll in theon INPUTevent. Scripts that loaded the DLL just to handle consecutive spaces can now use a built-in identifier.$trim(text,lmr)removes excess spaces from the left, middle and right of a text.$lastechoreturns the global result of the last/echocommand.
Security and library updates
- OpenSSL 3.5.9, UTF8-CPP 4.2.1, LibZip 1.12.1 and ADA IDNA 0.7.0.
- An updated CA root certificates file (
cacert.pem).
The release notes describe this as bug and security fixes in several libraries. OpenSSL is what protects every TLS connection mIRC makes, so this alone is a reason to update.
Bug fixes in 7.86
- The
+replystate for a channel or query was not reset, so a later message could be sent as a reply by mistake. - Timestamps were missing for some events, such as CTCP messages.
- The Server dialog parsed
ws:andwss:addresses incorrectly when a server or SASL password was set. - The color palette dialog did not accept digits in editboxes when the dialog was scaled.
- Memory leaks and intermittent crashes in the About dialog.
- Memory leaks and wrong results for some calculations in the MAPM / Big Float library.
Should you update?
Yes. If you are on 7.84 or older, go straight to 7.86: you get everything from 7.85 plus the fixes for the two bugs that came with its new features (the +reply state and websocket addresses with passwords). If you already run 7.85, update for the OpenSSL fixes and the reply bug.
The latest version is always on the official download page at mirc.com. Installing over an existing copy keeps your settings and scripts.
What this means for IRC
mIRC is still one of the most widely used IRC clients on Windows. When it adopts replies, account bans, channel context and WebSockets, these features stop being something only newer clients have. Network operators get one more reason to enable message tags and message IDs, and users get a more modern experience without leaving the client they know.
Sources
Related articles
Podeli objavu
Bilo je korisno? Podelite sa drugima!