> > What specifically is the problem is that you are missing the length > > value for the four element list ([jjjj]). I'm not sure how tpserver-cpp > > works in this regard and how you are missing that list length. > > tpserver-cpp works in assuming the client is running TP04. There is extra > programming required (that requires learning the frame format and using the > frame object) to make it work for TP03. It is much simpler to program for > TP04 *only*.
For now, we don't have any usable client which supports TP04 yet, so we will have to deal for the moment. I'm open to help (as nash is too probably) :) As a temporary fix, it is fairly trivial to add a new type to the libtpproto-py. Have a look at the ObjectDescs directory (the protocol library is designed to support configurable objects using the exact same code as orders). > Note that rfts even has a galaxy class, but doesn't use it because of how > crappy TP03 is. I am working toward tp04 support in libtpproto-cpp currently > (once I've finished, or in concert with, async support). Why do you need a Galaxy class? Leaving out object types doesn't seem like it should be a problem for the client. Hope this helps. Tim 'Mithro' Ansell _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
