Packets Documentation

[dastgirp]

Description

Add Packet Documentation in markdown format.

Reference: https://github.com/rathena/rathena/blob/master/doc/packet_interserv.txt The packets listed on that site, and on our are almost similar, with few additions/deletions in some packets, so you might find it great for start.

You can see our packets on: https://raw.githubusercontent.com/HerculesWS/Hercules/master/src/map/intif.c https://raw.githubusercontent.com/HerculesWS/Hercules/master/src/map/chrif.c https://raw.githubusercontent.com/HerculesWS/Hercules/master/src/char/inter.c https://raw.githubusercontent.com/HerculesWS/Hercules/master/src/char/mapif.c https://raw.githubusercontent.com/HerculesWS/Hercules/master/src/char/loginif.c

What to look for in these files? search WFIFOHEAD or WBUFHEAD (All Packets start with this) Next line might have something like

WFIFOW(fd, 0) = 0x3804;

OR

WBUFW(buf, 0) = 0x3804;

0x3804 is the PacketID There are variations in WFIFO/WBUF commands, which are listed below:

WFIFOW/WBUFW = 2 bytes WFIFOL/WBUFL = 4 bytes WFIFOQ/WBUFQ = 8 bytes

[4144]

directly using packet fields is mostly legacy way. everywhere should be used structs in normal way

[dastgirp]

@4144 we don't use structs for communication between login-char, char-map and map-char, so for this particular issue, I guess searching WFIFO/WBUF would be ok for documentation

[ConnorBrereton]

Can I take a crack at this?

[sushmaunnibhavi]

Can I take a crack at this?

[dastgirp]

Yes, atm, nobody is doing this.