Hello all, I've got a problem when running a local server with the Risk ruleset. It might be related to the new configuration protocol changes in tpserver-cpp, but I think it's a bug in the Risk module (or unlikely with the Risk configuration file).
The problem is simply that I can't login. It works perfectly with minisec but not with Risk. I get the following (relevant) lines in tpadmin: 2008-10-18 17:53:03 < Info > [Server] Client on connection 12 is [libtpproto-py/0.2.4 daneel-ai/0.0.1] 2008-10-18 17:53:03 < Debug > [Server] isEnoughRemaining, checking for 10, have 30 2008-10-18 17:53:03 < Debug > [Server] isEnoughRemaining, checking for 5, have 16 2008-10-18 17:53:03 < Debug > [Server] finding player 2008-10-18 17:53:03 < Info > [Server] Creating new player automatically 2008-10-18 17:53:03 < Debug > [Server] finding player 2008-10-18 17:53:03 < Debug > [Server] Risk onAddPlayer 2008-10-18 17:53:03 < Debug > [Server] There are 0 current players and the max players is 6 2008-10-18 17:53:03 < Debug > [Server] Risk::isBoardClaimed has been called 2008-10-18 17:53:03 < Debug > [Server] Risk::isBoardClaimed will return true 2008-10-18 17:53:03 < Info > [Server] Bad username or password 2008-10-18 17:53:03 < Info > [Server] Creating new player 2008-10-18 17:53:03 < Debug > [Server] finding player 2008-10-18 17:53:03 < Debug > [Server] Risk onAddPlayer 2008-10-18 17:53:03 < Debug > [Server] There are 0 current players and the max players is 6 2008-10-18 17:53:03 < Debug > [Server] Risk::isBoardClaimed has been called 2008-10-18 17:53:03 < Debug > [Server] Risk::isBoardClaimed will return true 2008-10-18 17:53:03 < Info > [Server] Bad username or password in account creation So what I *think* is going wrong is that isBoardClaimed returns true when there are no players, thereby concluding there is no room for the new player and thus rejecting him with the irrelevant "Bad username or password". I might be wrong though. Also, I don't see why this would just now turn up and not during SoC when three of us toyed daily with the Risk ruleset - something with the merges or the administration protocol that brought this up? Anyway, it doesn't really matter, it needs to be fixed. :) Iwanowitch _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
