Hello. Just to say that thanks to appropriate logging, I finally found what made the server crash. It was the use of Healing Wish in doubles with a pokémon in second slot. Was a pretty stupid mistake, because it's a result of the failure test (counting the remaining pokémons). Anyway, thanks to BEACH and Arthur for battling and making the server crash, so that now this bug is fixed. I'll use this opportunity to tell you a bit more about server crashes, those induced by battling. If your battle is frozen and the server window is active, it's already a hint. Try talking in the battle window, and then in the server. The crash will occur when the battle ends, i.e. when one of the two players log off or forfeits. So, if the server works fine but your battle froze (meaning you can't even talk in the battle window), save the battle log, take a screenshot, warn people on the mainchat that the server may crash, and PM me the battle log on the forums. (Don't post it in the Bugs Forum, because people may abuse it). That said, Beta Server already has the crash fixed (as well as 2 minor bugs reported, like Magic Coat + Dark Void), and i'll upload a safe server ASAP for everyone.
It won't connect for me and a few friends I talk to. It asks for a password, or it goes straight to this: (20:16:11) Connected to Server! Error while connected to server -- Received error n°1: The remote host closed the connection (20:16:13) Disconnected from Server! (sorry if this is the wrong place, but it seemed like there are too many "server wont work" threads ._.)
When it asks for a password, it means that somebody has already registered the alias you are attempting to sign on with, and you need to enter the password that they registered the alias with. Of course, if you didn't register the alias, you're going to have to change your alias, else you won't be able to get onto the server. As for it going straight to the error... well, the other members of auth are more likely to solve this than I am.
Well if it was earlier today/yesterday, it seems like that error happened because the server had crashed.
I watched the server crashing still even with the latest sources from svn. According to the output it happens when a battle is starting. Maybe there is a problem with older (outdated) clients and/or some strange teams. There should be an addition to send the clients version to the server on login (two-way version diff !), in the first step for debugging, later also for optionally banning too old versions.
Well, there's no problem regarding that with the beta server, which is more crowded. All the crashes were due to battle problems and made the server crash when the battle ended. Maybe a resource problem? And agreeing on the version, why not.
Up, to say that a threading problem was probably causing the recent crashes with Beta Server - that would happen sometimes when a spectator stops watching a battle when the battle is processing. I found it by luck, when i was doing the threading for the new db system (sigh). More like, I remembered how I did it and was anxious so I checked the source, and the problem was there. Good thing is, it happens not so frequently with the beta server which often has 200+ players) so I don't think other servers would be affected. Anyway, it was updated in the latest download along with other fixes.