Today I've logged on to thud chat a couple of times, and on each occasion there's been at least 1 other user in the list of online users. When i said hello and no-one responded, I tried challenging people and got these errors:
Challenging guest1250 Challenge cancelled by guest1250 Message from GameServ: Bad challenge. guest1250 is not logged in yet.
or in debug:
Challenging guest1544 DEBUG: Sent: PRIVMSG GameServ :CHALLENGE guest1544 t ThudGame DEBUG: commandString=:GameServ!@66.197.210.71 PRIVMSG guest2445 :cancelchallenge guest1544, waitingFor=0 DEBUG: Name: GameServ DEBUG: Host: 66.197.210.71 Challenge cancelled by guest1544 DEBUG: commandString=:GameServ!@66.197.210.71 PRIVMSG guest2445 :message Bad challenge. guest1544 is not logged in yet., waitingFor=0 DEBUG: Name: GameServ DEBUG: Host: 66.197.210.71 Message from GameServ: Bad challenge. guest1544 is not logged in yet.
Basically they seem to be phantom users...
I dunno what this may mean, whether there's a logical explanation or an easy fix, but thought it'd be worth pointing out.
Mr Scrub













Well I haven't seen this happen for probably about a week now, so I dunno what was happening but it looks to be sorted...
Mr Scrub
"LOOKS PERFECTLY LOGICAL TO ME"
erm, having other problems in that the message
GameServ left (QUIT:has disconnected)
keeps appearing. >.<
One race is made of rock, the other race is made of miners....
Well that means basically what it says - the server which controls the playing of the game is going offline. However, I've really no idea why.
My best guess is that our esteemed hosts (messers Morgan & Alley) reckoned that there would be fewer people wanting to use the game over the Christmas period, so took the oportunity to try something new on the server, and in the process had to take it down temporarily.
Mr Scrub
"LOOKS PERFECTLY LOGICAL TO ME"
Hopefully the latest release will have fixed the problem with the game server dying.
When that happens, it comes back within 60 secondds anyway, and you should be able to continue your games, though for security, you'll need to log in again to the new server.
That's what the error in the original post means. You try to challenge them, it knows the person you challenged hasn't logged in, so it sends them a request to log in, and lets you know that they haven't logged in.
Since the client responds automatically to the login request, you should be able to challenge them again within a few seconds, and it'll work.
On my to-do list is a way to make that a bit more transparent, so that it will hold your challenge until they've logged in, and only tell you they're not logged in if they don't log in within a reasonable amount of time.