[DiscordArchive] I'm not into all the magic that happens inside the worldpackets, and how the client uses them. BUT,
[DiscordArchive] I'm not into all the magic that happens inside the worldpackets, and how the client uses them. BUT,
Archived author: caweren • Posted: 2020-03-26T10:16:40.065000+00:00
Original source
I'm not into all the magic that happens inside the worldpackets, and how the client uses them. BUT, i have an issue that can only be fixed by doing one thing. I need to change and int16 to either and uint16 or int32. Now, am i correct in thinking that the client would end up getting garbage? I mean, if the client is designed to retrieve an int16, but i feed it an int32 it has no idea what's going on? Or does the packets send out lengths aswell, and if so, can the client distinguish these?
Archived author: MaxtorCoder • Posted: 2020-03-26T10:21:03.531000+00:00
Original source
> I mean, if the client is designed to retrieve an int16, but i feed it an int32 it has no idea what's going on? Or does the packets send out lengths aswell, and if so, can the client distinguish these?
The length is sent, the client reads the packet with type readers and such.
Archived author: MaxtorCoder • Posted: 2020-03-26T10:21:18.241000+00:00
Original source
So if you send a uint32 instead of uint16, the client will read it as a uint16.
Archived author: MaxtorCoder • Posted: 2020-03-26T10:21:26.651000+00:00
Original source
And then have 2 bytes as junk data.
Archived author: caweren • Posted: 2020-03-26T10:21:41.536000+00:00
Original source
That's what i thought... This kills my entire project