Jumping Problem

09/12/2010 17:25 Korvacs#31
Provided that your byte[] is 8 bytes longer than the length value to begin with then yeah that should be fine although personally i would memcpy:

Code:
fixed (byte* p = Packet, msg = GameHandler.TQServer)
{
      msvcrt.memcpy(p + Packet.Length - 8, msg, 8);
}
09/12/2010 17:34 Arcо#32
I don't need to implement that in both voids do I?
Just the second one right?
09/12/2010 17:35 Korvacs#33
Just in your send void, every out going packet must contain it.
09/12/2010 17:39 Arcо#34
Hmm, well now that I did that, I can't logon o.o
Code:
        public unsafe void Send(byte[] Packet)
        {
            lock (this)
            {
                fixed (byte* p = Packet, msg = PacketBuilder.TQServer)
                {
                    DataPacket.memcpy(p + Packet.Length - 8, msg, 8);
                }
                this.Socket.Send(Packet);
            }
        }
09/12/2010 17:46 Korvacs#35
When you create your byte[] for your packet do you make it 8 bytes longer than the length of the packet appears to be?
09/12/2010 17:47 Arcо#36
Oye, I forgot to do that >.<
09/12/2010 17:53 Korvacs#37
Any luck?
09/12/2010 19:10 Arcо#38
No luck :/
I can login, but it won't go past SetLocation
09/12/2010 19:23 Korvacs#39
Quote:
Originally Posted by .Arco View Post
No luck :/
I can login, but it won't go past SetLocation
Odd, not sure whats up with that...
09/12/2010 19:26 Arcо#40
Is it 100% certain that its the TQServer thingy as you said?
09/12/2010 19:30 CptSky#41
Your socket system probably already add the TQServer before sending. Look at my other post. You will find a way to always have the right seal.
09/12/2010 20:21 Arcо#42
Well I just took a look at [Only registered and activated users can see links. Click Here To Register...] which is the socket system I'm using and it does send the TQSeal.
09/12/2010 23:15 µ~Xero~µ#43
:facepalm: to korvacs :rolleyes:

Were u fucking serious with the TQServer String? If he can login,move (even only a bit) he sent it with it. how else could you login, not possible without the 8bytes of bs.

Anyway.. i checked your source arco. Atleast the one u gave me ages ago when it was 5065. the Jump Packet is too large.
09/13/2010 00:31 Korvacs#44
Quote:
Originally Posted by µ~Xero~µ View Post
:facepalm: to korvacs :rolleyes:

Were u fucking serious with the TQServer String? If he can login,move (even only a bit) he sent it with it. how else could you login, not possible without the 8bytes of bs.

Anyway.. i checked your source arco. Atleast the one u gave me ages ago when it was 5065. the Jump Packet is too large.
Yes i was serious, sending brand new packets with the TQ string is one thing, resending received packets is anouther. Clearly something you failed to grasp.

Remind me again of what youve done for the community that suddenly makes you an expert on anything? What....what was that? Nothing? Thought so. :facepalm:

As for "moving alittle bit" since you move client side even if you DONT send the packets back, any delay in resending (even for the slightest amount of time) can mean that you appear to move several spaces before receiving the first packet for your first movement, and since the .net framework sockets do not interact directly with the tcp protocol then this is definately a possibility.

Dont open your mouth unless you have something helpful to say Yuki, you just end up looking like a noob. >_>
09/13/2010 02:12 Arcо#45
Quote:
Originally Posted by µ~Xero~µ View Post
Anyway.. i checked your source arco. Atleast the one u gave me ages ago when it was 5065. the Jump Packet is too large.
Hum, the hell?
How is, (even if there is one) my jump packet too large o.O