Tyler - Thanks for the timely response. don't worry about not being around yesterday, it was a holiday in the US, not canada :P.
So my little error seems to be splitting into two seperate errors. One with the Bus Error (Server problem) , and one with my ruleset. The Bus error thing is sort of a sideline, as it doesn't crop up during config file loads. I can actually load my ruleset via a config file and the game seems to run properly from the server logs... The real error I am being held back by is the inability to connect to my server if the ruleset is set to risk. Here's what I did: tpserver-cpp -C quickstart-minisec.conf >This is all cool and loads/ lets me log in properly. So I go and modify quickstart-minisec a little bit to see if my quickstart has left anything out. I change minisec to risk for the ruleset, and comment out the last two lines that are minisec specific. Now I try again with the modified config: tpserver-cpp -C quickstart-minisec.conf >This time I cannot log in with my client though. I get the same error message as I mentioned before in the client, and I see this in the server: 2008-05-27 14:34:14 < Info > Client on connection 5 is [libtpproto-py/ 0.2.4 libtpclient-py/0.3.1 tpclient-pywx/0.3.1] 2008-05-27 14:34:14 < Info > Creating new player automatically 2008-05-27 14:34:14 < Info > Bad username or password 2008-05-27 14:34:20 < Error > underlying read, tcp, error is: Connection reset by peer 2008-05-27 14:34:20 <Warning> Socket error 2008-05-27 14:34:20 < Info > Closed connection 5 tpserver-cpp> I'm sorry if I have been really needy for help lately :P Ryan 'jphr' Neufeld --------------------------- visit me at hammerofcode.com _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
