Giant Whisper Posted May 1, 2018 Posted May 1, 2018 Hi, What should I do to avoid these numbers? client 2016-03-02 Quote
0 Tribal Posted May 18, 2018 Posted May 18, 2018 Hey, so I got this issue too, and would like to know how to fix it. The client I am using is 20170517 I tried a 20161228 client, a 20170517 and a 20170614 one. Recompiled my personal test server using './configure --enable-packetver=<client version> --enable-prere=yes' (on CentOS 7 using devtools-7). I've found outa Client diff for 20151104 clients exists, but I don't know how to modify that to a more current one. Running latest master branches on rAthena and running 'git pull' on a regular basis on test server. However no fix has been found yet (at least by me). I found out on my live server the numbers have a different notation than on my test server currently. I tried using Wireshark for valuable output, but I couldn't find anything of use. (Could be my incompetence using Wireshark though). I did find out that it's the ZC_ACK_WHISPER02 packet which is defined in 'src/map/clif.cpp' with the following code: void clif_wis_end(int fd, int result) { struct map_session_data *sd = (session_isValid(fd) ? (struct map_session_data *)session[fd]->session_data : NULL); #if PACKETVER < 20131223 const int cmd = 0x98; #else const int cmd = 0x9df; #endif if (!sd) return; WFIFOHEAD(fd,packet_len(cmd)); WFIFOW(fd,0) = cmd; WFIFOB(fd,2) = (char)result; #if PACKETVER >= 20131223 WFIFOL(fd,3) = sd->status.char_id; // GID/CCODE #endif WFIFOSET(fd,packet_len(cmd)); } If anyone could elaborate on this issue, please do. Thanks in advance, Kevin Quote
Question
Giant Whisper
Hi, What should I do to avoid these numbers? client 2016-03-02
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.