Post: #58

(07-20-2012 05:29 AM)khaos Wrote:  @WAP
Move networking area below the intial stuff in the top of INI. Basically near whereever you put AGREE=1. That according to Anarch Cassius fixes those issues. There should be no reason it worked not long ago and be broken now since none of us are playing with the networking. That is SugarCube's area of expertise. He always has done the networking.

I suggest you to fix the default ini, because this issues can be the big problem for newbies in Sphere and for people who would like to migrate from old Sphere versions to the new one.

(07-20-2012 05:29 AM)khaos Wrote:  What packet issues? There are new walk packets we won't implement. Cube said something was buggy with them in general or something. He also didn't implement the new animation packets or something. He said they weren't needed at the moment I believe.

Very often:
DEBUG: df:Game packet (x) does not match the expected length, waiting for more data...
sometimes:
WARNING: df:Unknown game packet (x) received.
The last may be related with packet splitting, while a part of packets have read by Sphere as whole packets...
Also it seems, that ralely client can be stopped(it is not crash, but you can't move or do something, resend don't fix this, you have to re-login).

We don't use the new clients, only 2.0.3 and 6.0.14.3.