Never connects to certain world

I have this world setup to auto-connect when MUSHclient starts up:
tcdbbs.zapto.org 4218

Whenever I start up MUSHclient, it stays at "Look up world name: tcdbbs.zapto.org" and never actually connects. I've waited an hour and nothing. I can reproduce this on multiple computers, but I'm on the same network. Can anyone else reproduce this, or is it just my network?

I tried it and connected just fine. Have you tried going into a command line and trying to ping the server? If it can't find it, you might just need to make a better dns list. Also, try 68.62.252.116, which is the IP address of that server (at least it was when I tried it, don't know if it's a static IP).

It connects fine for me if I don't use Connect On Startup.

Did you test it on Connect at Startup? That's what I'm talking about.

Ah, misunderstood the issue there. I just toggled the connect on open option and opened up another instance of MC. Didn't connect, and I let it wait for a bit. Then I clicked the connect icon twice, and presto, instant connection. There's definitely something wrong with the connect on open option.

Yeah while it's waiting I can disconnect and reconnect and it'll work. But it should connect to it or timeout, not stay in an attempt at connecting forever.

Oh, and btw, it is not a static IP but it just recently (a few days ago) changed to the one you displayed there for the first time in nearly three years, so it's pretty close to being static. ;)

I can't reproduce that. You mean auto connect at program startup? With a couple of startup worlds they all seem to connect OK.

I can reproduce this with multiple computers:
-Make sure that world is setup to auto-connect on startup.
-Close MUSHclient.
-Open MUSHclient.
-All worlds will auto-connect fine except that one.

I figured it was just my network until Shaun said he can also reproduce this.

Actually, I didn't try that mud. I tried Aardwolf. When I opened MUSHclient, the connect button was pressed down already as if it was connected, but there was no response at all. The title bar also said it was connecting. When I finally gave up, I manually had MC connect, and everything was fine.

Connecting is done asynchronously. Maybe that message gets swallowed up somewhere. I still can't reproduce it here.

Ah here we go. I narrowed it down. It's not the world that makes this happen. It's what is being opened in what order.

It seems that the last world in the startup list will not connect as we've said here. I changed it from the address I said in the first post to a new server and new MUD, and it still happens. I believe this may have something to do with the world trying to connect while the spellchecker is loading?

Ah yes, the spell checker. :(

I can reproduce it now. :)

If you edit the spellchecker.lua file and change this line:


local SHOW_PROGRESS_BAR = true -- show progress bar? true or false


to:


local SHOW_PROGRESS_BAR = false -- show progress bar? true or false


That seems to fix it.

I have fixed the problem in version 4.03 by loading the spellchecker sooner (before opening the worlds in the startup list).