[6132+] 10005 Walk Packet Protobuff Serialization/Deserialization (the PROPER way)

[CrystalCastle]

Requirements

• Download and include in project
• Make sure you strip the 4 bytes at the beginning of the packet (Size and Type) and ensure that you remove the packet footer (8 bytes containing the TQServer/ TQClient) before deserializing your packet. And obviously ensure you add the correct packet headers and footers when sending the serialized packets back to the client

[6132] Walk Packet Class Structure

    [ProtoContract]
    public class Packet_Movement
    {
        [ProtoMember(1)]
        public uint Direction { get; set; }

        [ProtoMember(2)]
        public uint UID { get; set; }

        [ProtoMember(3)]
        public uint Running { get; set; }

        [ProtoMember(4)]
        public uint TimeStamp { get; set; }

        [ProtoMember(5)]
        public uint MapID { get; set; }
    }

Protobuff .Net Deserialization Example

Serializer.Deserialize<Packet_Movement>(new MemoryStream(Packet));

Protobuff .Net Serialization Example
This also converts it from a MemoryStream into a Byte array

Packet_Movement PM_Class = new Packet_Movement();
byte[] Packet_Data;
using (var ms = new MemoryStream())
{
    Serializer.Serialize(ms, PM_Class);
    Packet_Data = ms.ToArray();
}

[Spirited]

**** you! I was going to write this up before leaving this morning and put it on my wiki. I had an example project and everything. You win this round! *Shakes fist in air* Edit: Put up my version on the wiki anyways. Best to have more than one example / implementation, I suppose.

[CrystalCastle]

Originally Posted by Spirited

**** you! I was going to write this up before leaving this morning and put it on my wiki. I had an example project and everything. You win this round! *Shakes fist in air* Edit: Put up my version on the wiki anyways. Best to have more than one example / implementation, I suppose.

Haha. Yeah dude, do as you please

[KraHen]

The new intern at TQ HQ must have had fun implementing this in CO.

[-impulse-]

You might want to mark Direction and Running as Required fields in their proto attributes. In case they are 0 the serializer will not write them and the client will not use the packet, because the client defined the proto fields are required most likely (not writing them in the packet would result in failure in deserialization).

[modyali2]

it need array.copy
the final step

[Xio.]

Originally Posted by modyali2

it need array.copy
the final step

Why?

[MCJackson]

CrystalCastle,I really appreciate your help very much， You really are a genius

[tkblackbelt]

I thought protobuf also include the proto member index in the encoded data? Wouldn't that cause the client to not be able to read the packet?

[Spirited]

Originally Posted by tkblackbelt

I thought protobuf also include the proto member index in the encoded data? Wouldn't that cause the client to not be able to read the packet?

The header of the packet, which includes the packet length and identifier, doesn't go through Google Protocol Buffers. If you take a look at from my wiki website, the first int of data isn't included as a protomember. Each field is also required, so if the direction is zero or movement type is zero (for example), it won't crash the client or cause mishandling on the server.