Chalk Game F too!

Server registered to EIS TradeWars Server
Supports up to 25 games and 100 nodes

<D> Test RLogin <F> LEGION Beta
<O> Sing's Timing Tests <R> Stress Test

<#> Players Online
<!> View game descriptions

<Q> Quit

Selection (? for menu) : FFailed to start game session...Disconnected...
Connection lost.

Yeah, a few more days and I would have got first rank! lol

I'm glad everyone's hanging in there. Game A is a lot of fun.

It's going to be sweet when JP finds and fixes this CPU pegging. As long as I've played this game it's done this from time to time.

And a BIG thank you to, who is it EP who's hardware we're abusing? Whomever it is donating the hardware, we couldn't do this without you!

Thank-You!

Let me know if you need me to do anything. I'm assuming that twx runs on a server os, and not a desktop os. could be running into a tcp socket issues too

Don't worry about the games. They're not closed. When the server is stressed, opening games will just cause additional stress. TWGS will now automatically close games to keep players from continuing to try to open them and exacerbate the problem. I need to make it more clear that the game is temporarily closed, though, so people aren't confused that the game has been closed by the op.

Before I did this, the server was so bogged down that it took EP over an hour to finally get connected and trigger a reboot. With this change, it takes me about 2 minutes to get on and kill TWGS. So it's a huge improvement.

I'm seeing a pattern now. Twice now the node with Micro's bot was stuck in a disconnect state. This last time, I was able to verify that the node on which Micro's bot was stuck was pulling 100% CPU. So whatever is happening, it's being caused when Micro's bot logs in to check game stats. I'm going to get with Micro and see if we can use his bot to track this bug down. Sorry about the inconvenience this is causing, but I think it'll be worth it. Hopefully this problem won't last more than another day or two, and if it is Micro's bot triggering the bug, we'll be able to control it.

I reconfigured Microbot to only scan classictw.com on demand. We can run it any time you want to, but it won't run on it's normal schedule.

Cool. Will you be around tomorrow to troubleshoot this with me?

Ok, this bug is fixed. Sorry for the disruptions!

Microbot was triggering the bug because it didn't understnd the new description menu changes.

My apologies to all the players on classictw.com!!!

...but at least we found the bug before it even got released!

No problem, that's why we're here Good Job!

It was nothing specific to Micro's bot. Anyone dropping carrier at that menu would have spiked the CPU. We're lucky Micro's bot was doing it so it was discovered before release.

When will a new version with this bug fix be released? This is a major bug that can cause damage to the servers CPU, and a quick release would be appreciated.

This bug is not in any versions that have been released. It was caught before it got out.