Commands

All commands are typed in a window's text field preceded by /, or can be used inside a script (alias, event, popup) without the slash. They're the same commands, with the same behavior, in both contexts.

Connection

Messages

CTCP

CTCP (Client-To-Client Protocol) is the standard IRC mechanism two clients use to exchange "service" requests outside the normal chat (client version, ping, time, etc.). Yoake implements it on IRC and, in addition, on Telegram and WhatsApp as well when BOTH sides use Yoake.

Yoake also automatically replies to incoming CTCP VERSION, PING, TIME and CLIENTINFO requests (a standard IRC client-to-client protocol feature, the same thing real mIRC does) - on IRC the reply goes out as a NOTICE, never shown in the channel/query window itself (exactly like real mIRC), logged as a one-line note in Status.

Away / ignore

Incoming calls

Our own addition - real mIRC has no calls. Yoake detects when a call comes in (audio or video, both Telegram and WhatsApp) and shows it as a system message, but it's notification only: GramJS/Baileys don't implement the actual audio/video at all, you can't really answer from here - see Scripting for the full explanation.

Twitch

Twitch is a network of its own, with the same multi-account/multi-channel spirit as IRC (several Twitch accounts at once, several channels per account at once) but of a different nature: it isn't a text protocol like IRC, so Yoake doesn't talk to it over a socket - it opens a real embedded browser instead (a hidden Chromium window, one per joined channel) that replicates what a real person would do on the twitch.tv website. Login, chat, the nicklist and the channel list all depend on the real Twitch site, not on a dedicated server - see Connecting for how login works.

Status / Stories

Our own addition - real mIRC has nothing equivalent (there's no concept of "status" on IRC).

Saving photos/videos

Right-click a photo or video open in the viewer: two options, "Save as..." (opens the file picker, you choose where) or "Save to default folder" (saves right away, no questions asked, like real mIRC does with received DCC files). There's no risk of overwriting a file with the same name: if one already exists, a number in parentheses is added.

Saved stickers

Our own addition - real mIRC has no concept of stickers. In the viewer, right-click an incoming image or sticker and pick "Save as sticker": it works on any image, not only on a real incoming sticker (like the official clients' "convert to sticker"). Ctrl+K for stickers is Ctrl+S: it opens the list of saved stickers right above the text box of any window (the same spot as the emoji picker) - a click sends one straight to the open chat (it doesn't insert it into the text, same as clicking a sticker in the official clients), the cross in the top-right corner of each one deletes it from the list.

Download whole set (Telegram only) - same right-click in the viewer, but only on a real incoming sticker that belongs to a pack: downloads and saves every sticker in that set in one go (like the real Telegram client does), ready in the Ctrl+S list. On a "loose" sticker (no real pack) or a plain photo the option doesn't even show up.

Video playlist (scripting)

Our own addition - real mIRC never had video, so it has nothing equivalent. Designed for a script that wants to walk through a channel/group looking for videos (e.g. a channel with a series' episodes) and play them in sequence, moving to the next one on its own when one finishes.

See $msg() in Identifiers and functions to walk through a channel's messages, and the on videoend event in Scripting (fires on its own when a video finishes playing) for a complete automatic-playlist example.

Share / Forward

Our own addition - real mIRC always sends DCC files to a single nick chosen by hand in the command, it has no real "forward". Every photo/video/audio/document in chat has a 🔁 Share button right below it (in text mode it only appears after opening it at least once, since there's no preview there) - it opens a window with a search field and the list of contacts (with phone number, if available) and groups/channels of both networks currently connected, not just the source one: click one to share right away.

If source and recipient are on the same network, sharing uses that network's native forward (the same mechanism as "Forward" in the official client): the server copies/reuses the message it already has, without the file passing through here again - faster, and for the recipient it shows up as a real forward (on Telegram with the "Forwarded from" label). Only when source and destination are on different networks (e.g. a video seen on Telegram, sent to a WhatsApp contact) is the file downloaded and re-sent as a new upload on your behalf - the only possible way in that case, since neither network can forward to the other. The same download-and-resend path also kicks in on the same network if the native forward fails (e.g. media too old, the original reference is no longer available).

Every media item in text mode also has a unique number right in its label, e.g. [video33] - used by the share command to share it without the mouse:

Loading scripts (/load, /unload, /reload)

Official mIRC documentation (mirc_commands.html). Identical syntax to real mIRC, with one important architectural difference: in real mIRC you can have many separate .mrc files, each with its own position in a "Scripts" list; here instead aliases/events/popups all already live in a single shared space (the same reason why, as documented elsewhere, an alias written in Remote works identically to one written on the Aliases tab). As a result:

• The position parameter (-a2, -rs3, ...) is accepted for syntax compatibility but ignored.
• If the loaded file redefines the same event name that's already active (e.g. two on start in two different files), the last one loaded overwrites the previous one - the exact same rule that already applies today within a single file.
• /load triggers on load but not on start (real mIRC fires both): on start is a single global event, having it fire again on every /load would create an infinite recursion in the most natural use case ("on start { load -rs extra.mrc }" to load something extra at startup) - discovered precisely while testing this feature.
• -ru (users file) has no equivalent: there's no concept of an IRC user list/access levels in this app.
• -pm (popup menu bar) correctly loads the data, but the "menubar" context isn't wired to a real visible menu in the interface yet (pre-existing limitation, not specific to /load).

Loading the same file twice with load updates it in place (like real mIRC) instead of leaving a duplicate. Files loaded with /load stay loaded even after restarting the app (re-read from Yoake.ini, just like real mIRC remembers its Scripts list), /unload removes them from there too.

; load an extra alias package at startup
on start {
  load -rs C:\Yoake\scripts\extra.mrc
}
; ...later, to remove it:
unload -rs C:\Yoake\scripts\extra.mrc

Windows

Updates

Command specific to Yoake, not real mIRC.

Files and sounds

DCC: direct chat, file transfer on IRC, stickers in channels

Besides dcc send above (file transfer, official mIRC/DCC documentation), Yoake also supports real DCC CHAT: a direct chat over a TCP socket between two machines, which once established no longer goes through the server. On IRC it's the real, historical protocol, compatible with any other real IRC client (mIRC, HexChat, irssi...); on Telegram/WhatsApp the exact same socket is reused, but the invite travels "disguised" as a normal message (the same trick already used by /ctcp above), plus a security token, since there's no pre-existing trust model there like on IRC - it therefore only works Yoake-to-Yoake, never toward a contact's official client.

An accepted DCC chat becomes its own small window, with the same interface as a normal chat (no nicklist, it's a connection between just two parties). For the address to use in the invite, Yoake defaults to preferring a public IPv6 address if the machine has one (no NAT to traverse - it works from many mobile connections nowadays too); if there isn't one, it falls back to a local IPv4 address, warning that it's probably only reachable on the same local network unless you've manually forwarded a port on your router.

DCC SEND on IRC. dcc send (see the "Files and sounds" table above) now also works on IRC - previously it wasn't available at all on this network. Same syntax and the same progress window already used for Telegram/WhatsApp, but with a real, byte-accurate percentage (real DCC, direct socket): unlike WhatsApp, whose progress bar is an indeterminate animation because Baileys doesn't expose incremental upload progress, on IRC the number shown is therefore more accurate. Same IPv6/IPv4 choice and the same NAT warning as the DCC chat above.

Stickers and images in IRC channels. Sending a saved sticker/image while a CHANNEL window is active (not a private query, which uses the normal dcc send above) goes through a different, purpose-built mechanism: real DCC is always 1-to-1, it can't "broadcast" to an entire channel - not even real mIRC can do that, it's a protocol-level limitation, not a Yoake gap. Instead, Yoake sends a single CTCP announcement (our own invention, not a real DCC subtype) to the channel, with a session id, address, port, filename and size: the IRC server relays it to everyone inside on its own, for free, like any normal channel message. A real IRC client that isn't Yoake silently ignores it, like any other CTCP it doesn't recognize - it never sees the image. Any Yoake client in the channel that does recognize it connects DIRECTLY to the sender (the image bytes never pass through the server) and downloads it automatically, no "accept" step needed: it appears in the channel like a normal sticker, exactly as on Telegram/WhatsApp. Size limit: 200KB - anything larger is rejected with a warning instead of being sent anyway or flooding the channel.

File Handling

As in real mIRC, used to read/write text files inside scripts (aliases, events) - not commands meant for interactive use in chat, a bit like timer. Each opened file is given a name of your choice (<handle>), later used to refer to that file until you close it.

See also Identifiers and functions for $fread(), $fgetc(), $feof and $ferr, used to read the content of an open handle.

Binary Files

As in real mIRC, they work byte by byte instead of by text lines (unlike fopen/ fwrite above). The data lives in binary variables &name (byte arrays 0-255), distinct from normal text %variables - they stay until you do bunset.

See also Identifiers and functions for $bvar() and $bfind(), which read the content of a binary variable.

Sockets

As in real mIRC, they let a script talk directly to an external TCP server (or receive data from one), independently of Telegram/WhatsApp - not commands meant for interactive use in chat, like fopen above. Each connection is given a name of your choice (<name>), later used to refer to that socket.

See also Identifiers and functions for $sock(), and Available events for on sockopen/on sockread/on sockclose/on socklisten.

External programs

Timers and signals

Variables and flow control

Flow control as in real mIRC - no "for" (doesn't exist there either), only if/elseif/ else/while/goto. if and elseif accept both the classic multi-line block with braces, and a single command on one line with no braces (classic mIRC style):

if (a == b) { ... }
elseif (a == c) { ... }
else { ... }

if (%nick == $null) goto done        ; no braces: a single command, the whole line
if (a == b) { ... } elseif (a == c) { ... } else { ... }   ; "} elseif (...) {" on the same line is fine

while (a < b) { ... }   (max 10000 iterations, then stops on its own)
:label ... goto label

Operators (official mIRC documentation, "If-then-else statements" section):

As in real mIRC, every word operator (isin, isnum, isop, etc.) can be negated by putting a ! in front of it, e.g. if (%x !isin %list).

See also Identifiers and functions for $nick, $chan, $1-$9 and the $len()/$calc()/etc. functions usable inside any command, and Dialogs for /dialog and /did (custom windows with buttons, text boxes, lists, tabs and menus).