Forums mIRC Help mIRC timing out on a Discord Proxy

I have mIRC running on a custom IRC server implementation that translates Discord events into IRC messages and vice versa. This is because the mIRC instance connected to it runs a bot crucial to the community that the Discord server belongs to and rewriting it in a modern programming language would be inconvenient to the maintainer of the bot. The server connects to Discord as a client and presents itself to a single IRC client as a server with IRCv3 features that facilitate Discord's features.

Everything works as expected. We have event been able to script the bot to respond to reactions and other asynchronous events (through use of message tokens,) but issues arise when connecting mIRC to the fake server: specifically, mIRC times out and kills the connection of certain operations take too long. The server in question has over 1k users and mIRC seems to time out while receiving the NAMES list. We've had to slow down the message queue of the server in order to keep mIRC connected and that only sometimes works.

Does anyone have any advice on how to make this work?

As long as your server is behaving in the same way as a standard IRC server, eg. sending the expected numerics, 001, etc. on connecting, sending End of MOTD, so mIRC can trigger post-connection features, and so on, I can't a reason why this would be happening. A thousand users on a channel is not that large, so mIRC should not have a problem with that.

One way to see what is happening is to use the "/debug on" command to output raw server communication to a debug.log. Or "/debug @test" to output to a @test window. You can then see what mIRC is sending/receiving to/from the server. You can then do the same thing on a standard IRC server and compare the results. Is your server sending the same sequence/format of events as a standard IRC server?

You could also try to narrow the cause down, eg. is mIRC connecting with SSL? If it connects without SSL, does that make a difference?

That said, this will also depend on what your script in mIRC is doing. If your script performs long operations, this will block mIRC in the interim. If you add debugging /echo comands to your script, can you see where the slowdown is taking place?