Thread: Matrix 838

Originally Posted by Naturality

Not really sure where to begin. I know that the source has basically nothing added, chat is broken etc. I fixed chat for normal players, working on admins and what not, then I came across this.

Code:

[WorldPacketsDecoder] Missing packet 73, expected size: 4, actual size: 4

What does this mean? I'm clueless when it comes to packets since I haven't really dealt with them yet.

I noticed something that whenever I moved my camera, it would say packet 7 missing, so I put the packet of Move_Camera to 7 and I stopped getting that message. I'm not sure if it's sending that error because its missing a packet, and because it received a packet that the message stopped or what. :c

This is the default message displayed when the packet is not handled. So basically, add the end of all the packet decoded there is:

Code:

} else {
    Logger.log("WorldPacketsDecoder", "Missing packet....");
}

A packet is a block of information that's exchanged between the client and the server in both directions.

So basically what's happening is the client is sending packet 73 and the server doesn't know what to do with it. So it's printing out that message. To identify the packet parameters use this: [Only registered and activated users can see links. ]

Originally Posted by clem585

This is the default message displayed when the packet is not handled. So basically, add the end of all the packet decoded there is:

Code:

} else {
    Logger.log("WorldPacketsDecoder", "Missing packet....");
}

A packet is a block of information that's exchanged between the client and the server in both directions.

So basically what's happening is the client is sending packet 73 and the server doesn't know what to do with it. So it's printing out that message. To identify the packet parameters use this: [Only registered and activated users can see links. ]

Thank you for this, I read your post about reading/writing bytes. I somewhat understand the writing part, but I'm not too sure about the reading part.
Confused on actually how to read it on the server side.

Originally Posted by Naturality

Thank you for this, I read your post about reading/writing bytes. I somewhat understand the writing part, but I'm not too sure about the reading part.
Confused on actually how to read it on the server side.

It's usually the same exact method but with "read" instead of "write". Just look at the methods. Example it says:

Code:

class330_sub34.aClass330_Sub46_Sub2_7729.writeUnsignedShort(i_9_, (byte) 21);
class330_sub34.aClass330_Sub46_Sub2_7729.writeUnsignedByte(Class356.method4190((byte) 3) ? 1 : 0, (byte) 83);

on the client, you get this code after removing the junk:

Code:

writeUnsignedShort(X);
writeUnsignedByte(X);

Now, on the server, all you have to do is read:

Code:

stream.readShort();
stream.readByte();

in the packet decoder.

You can confirm your results by comparing the write/read of both client and server:

Code:

public void writeUnsignedShort() {
    buffer[(offset += 323600977) * -824785231 - 1] = (byte) (i >> 8);
    buffer[(offset += 323600977) * -824785231 - 1] = (byte) i;
}

public void readUnsignedShort() {
    return (readUnsignedByte() << 8) + readUnsignedByte();
}

Without the junk it gives:

Code:

write: i >> 8 + i
read:  i << 8 + i

The ">>" 8 encrypted the "i" so it needs to be "<<" in return. We can see that everything is in order so "readUnsignedShort" is the read equivalent of "writeUnsignedShort".