Really thanks to you for your suggestion, it's work great!
Now I've the client decompressed but i have another question for you all:
Do anyone know the packet's payolad structure?
That's my problem :
Now I'm able to see all the classes of the client but when i sniff an exiting packet with wireshark, if make the same action, the payload change entirely... how, the server know what kind of action we are doing?
Inside the payload shouldn't be present, at least, an ID or something to identify the action?
First TCP capture with click on map
Second TCP capture with click on map
I've noticed that when I make a movement it's always sent a packet with a payload of 22 byte but as you can see the payload doesn't have anything equals.
Let me know if someone have any suggestion.
Thanks