Forums Active Threads Past Week

As per the topic, is it possible to hook mIRC events in a similar way to that of a script once the DLL is loaded? or is a script required to pass the data to the dll?

In my case, I'm considering the on PARSELINE event, rather than hooking the winsock read/write calls directly.

Hello, fellow mIRCer's.

Has anyone come up with a newer solution to have colored syntax in scripting? I recall someone from #mirc (argv0?) who said there is a .dll but I think it no longer worked.

Also, what's a common dialog creator/maker these days?

Thank you for your replies.

Dear mIRC User,

mIRC v7.78 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 SCRAM logon authentication bugs.
Added Windows taskbar support for DCC Send/Get progress bars.
Fixed Aero theme helper windows startup flicker bug.
Changed "Hide away reminders" option to apply to all contexts.
Added support for loading SVG files.
Fixed server list parsing bug causing random crashes.
Fixed $regml() bug relating to /F and empty groups.
Fixed flickering menubar bug.
Updated libraries to OpenSSL v3.0.15, TagLib v2.0.2, and LibZip v1.11.2.
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!

Hello,

I made a very basic script meant to encourage msl scripters to take it wherever they would like. It is intended to help people get over the hump of making API calls to openai so it's not bulletproof or feature packed but is instead quick and dirty. You can check it out here: https://github.com/sam-hiatt/Simple-chatgpt-mirc/

Would it be possible to extend the behavior of $dialog( N ) to be able to take an optional table argument as well, such that it (as would hopefully be obvious) returns the name of the Nth dialog using a specific dialog table (or the total number of them if N == 0), rather than just giving an "invalid name" error as it does currently? I realize this use case might very well be rather niche; I'm not entirely sure how common it is to even have multiple dialogs with the same dialog table open at once, and of course it isn't difficult to emulate the behavior by checking the table property, but certainly some scripts somewhere must allow multiple dialogs with the same table to be open at once, and for those that do, not having to manually make that specific check would probably be a small but nice bit of relief.

Hello people.
I want to replace mdx.dll for dcx.dll on my script but I couldn't understand how to use it. Can anyone explain me how can I replace this code here from mdx.dll to dcx.dll?!

mdx SetMircVersion $version | mdx MarkDialog mp3_system
mdx SetDialog mp3_system icon sistema/imagens/player32.ico

mdx SetDialog mp3_system bgcolor $rgb(0,0,0)

mdx SetFont mp3_system 120 20 500 Segoe UI

mdx SetColor mp3_system 70 text $rgb(255,255,255)
mdx SetColor mp3_system 70 textbg $rgb(0,0,0)
mdx SetColor mp3_system 70 background $rgb(0,0,0)

mdx SetBorderStyle mp3_system 70 windowedge



thank you

The most likely reason is that mdx.dll is not using Unicode.

Just a quick update on the language support in mIRC.

Since the last release (when language support was added) I have mainly been reviewing translations (Spanish, French, and German so far) to improve how mIRC parses/accepts/rejects valid/invalid string formats and to detect other issues in translated text. mIRC is an old application with 3000 strings of text, written over almost thirty years, that use different formats, sentence structures, contexts, and so on. These pose a real challenge to translators and I don't envy them having to translate them.

As I was not sure if/when users would contribute translations, I asked Alconost to translate the mIRC resources on Crowdin into Spanish as a first step. While this was in progress, French and German translations were kindly contributed. I have uploaded the French and German translations to Crowdin, which has allowed me to compare the English, Spanish, French, and German translations alongside each other. For the most part, the translations are great. However, there are some tricky combinations of words that I need to provide feedback on to the translators, which will require significantly more time and effort on my part. I would really like to establish a good base-line set of translations, since these may be used by other translators on Crowdin to decide context, meaning, etc. in the future.

I was originally hoping that a set of EFIGS language DLLs would be ready for distribution with the upcoming release but, at this point, I think more work is needed. So the current plan is to release the next version of mIRC soon and to continue work on EFIGS languages for the next release.

Thanks for your help/feedback with the translations so far everyone.

Thanks, I have added this to my to-do list.