On Thu, Aug 21, 2008 at 7:02 PM, Victor Ivri <[EMAIL PROTECTED]> wrote: > I'm living in ET, which is -5 UTC. Tuesday 1PM UTC is fine for me.
Okay, so http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=26&year=2008&hour=13&min=0&sec=0&p1=0 or http://tinyurl.com/6modsp for guests to determine their time. > >> I can host, though I'm fine if you'd rather have someone else. > > That's fine! I want to try and ping you prior to that, to see approx. > how long a turn should take. Okay, catch me on IRC. I need to toy around with my router too I think. >> Mmm, longer turn length please. 120 should be plenty I think, but 60 >> is a bit close. My bot is pretty slow. :) > > Now I'm afraid, you see ;). Mine takes no longer than 3-4 seconds on a > local server. I'm sure that the logic in my bot, implemented in C or Java, wouldn't take a lot longer than a few seconds either. It's just my framework. Order of magnitude optimizations are probably possible, but were out of range for SoC, and the bot is still fast enough when playing against a human so I didn't bother too much. Sorry bored spectators, pick a realtime game next time. Or watch the video. >> Though it also sends a >> request end of turn frame at the end of its calculations, so it won't >> keep you if it actually isn't thinking. > > Are you using TP04? I switched to it, but then I had problems with > getting OrderDescs (server broke off connection with client for some > reason, and might've crashed, too.. don't recall exactly), and I had > to switch back to TP03. So mine doesn't send an EOT frame. Erm, I use TP03, but they work. Don't ask me about the specifics, I just use libtpclient-py. I never knew they aren't even in TP03. Though that probably explains the "Turn Finished Frame: protocol version not high enough, but continuing anyway" messages in the server output. :) Iwanowitch _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
