Jumping Problem

Korvacs · 09/12/2010, 17:25

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);
}

Arcо · 09/12/2010, 17:34

I don't need to implement that in both voids do I?
Just the second one right?

Korvacs · 09/12/2010, 17:35

Just in your send void, every out going packet must contain it.

Arcо · 09/12/2010, 17:39

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);
            }
        }

Korvacs · 09/12/2010, 17:46

When you create your byte[] for your packet do you make it 8 bytes longer than the length of the packet appears to be?

Arcо · 09/12/2010, 17:47

Oye, I forgot to do that >.<

Korvacs · 09/12/2010, 17:53

Any luck?

Arcо · 09/12/2010, 19:10

No luck :/
I can login, but it won't go past SetLocation

Korvacs · 09/12/2010, 19:23

Quote:

Originally Posted by .Arco

No luck :/
I can login, but it won't go past SetLocation

Odd, not sure whats up with that...

Arcо · 09/12/2010, 19:26

Is it 100% certain that its the TQServer thingy as you said?

CptSky · 09/12/2010, 19:30

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.

Arcо · 09/12/2010, 20:21

Well I just took a look at

which is the socket system I'm using and it does send the TQSeal.

~~µ~Xero~µ~~ · 09/12/2010, 23:15

to korvacs

Were u ******* 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.

Korvacs · 09/13/2010, 00:31

Quote:

Originally Posted by µ~Xero~µ

to korvacs

Were u ******* 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.

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. >_>

Arcо · 09/13/2010, 02:12

Quote:

Originally Posted by µ~Xero~µ

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