Mikegyver

nemo not yet support Custom Packet Keys Encryption starting on 2016 clients which means u can only use default packet keys encryption.

no wonder i don't face this kind of problem coz i've been using zack's data from the start. glad to know this problem not caused by client diffted by nemo patcher...

I don't think packet obfuscation would causing trouble. And i'm using this client too.. with packet encryption / packet obfuscation enabled.. no problem when killed monster dropped any items. But just want to ask u. Do your kRO full client is in the latest version? As this is 2017-06-14 exe client, ur kRO also at least on the same date or newer. My suggestion, try to patch your kRO client first and see either this problem happen again or not.

Follow these... It should fix the missing gcc on ./configure sudo apt-get install gcc-5 -y sudo apt-get install g++-5 -y sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 1 sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-5 1

I see.. i finally get what u mean earlier.. Thanks dude.. much appreciate for these releases.

yup. i know.. those 2 patches update are relevant on this i thread.. but i mean.. on overall recommended patches.. only left enable who command which is still fail on recommended patch.

yup. i know.. those 2 patches update are relevant on this i thread.. but i mean.. on overall recommended patches.. only left enable who command which is still fail on recommended patch.

i'm using secretdataz nemo. + combine your 2 update patches.. just left this one on recommended patch which still fail i i think if u click on select recommended.. u can try on click on it. EDIT: anyway thanks for the fix. i guess i can use this 2017-07-05 RE client. thanks to u.

yup. it works for me on 2017-07-05 too.. but, got another recommended patch is failed.

can u create for disconnect to login window? i think it is much quite related too.

u can replace 41 6C 65 72 74 00 00 with 4D 65 73 73 61 67 65 and it will become message

yup.. the rest should be working fine.. and it is just too bad @NeoMindhas been hiatus.. and his last commit on nemo was end of may 2016. i've seen somebody offering a paid service request a fix on nemo patcher.. u can ask the topic starter.. either he already got a reply or not.

do u have unpacked 2016-10-26 RE client?

Does this client has been unpacked by ollydbg?

HAHAHAHA.. of course... since i patch ur client with enable packet encryption. u only can comment on this if the client is patched with disabled packet encryption on nemo patcher. and i'm not sure why u want to disabled packet encryption? as this packet encryption can secure ur server from WPE. as it name is encryption.. it do encrypt the client.. for the client - packet encryption for the server - packet obfuscation if u disable packet obfuscation on server, u must disable packet encryption on client. but, i setup ur client with packet encryption is enabled. so, u must enable packet obfuscation on server. @sader1992 client starting 2015-12-16 cannot be patch with custom packet key encryption. so, if 2015-12-16 & newer client, it only will use default packet encryption keys which is already in the src/map/clif_obfuscation.h

yeah.. i know i made it for u. since the client is already packet encryption enabled, why need to comment on #define PACKET_OBFUSCATION_WARN? this is for those who are disabled packet encryption on nemo. as it warn the owner of he is currently disable the packet encryption.. but i made ur client into packet encryption enabled. i don't think u need to comment on it.. unless.. if u do comment on #define PACKET_OBFUSCATION, then u need to comment on #define PACKET_OBFUSCATION_WARN.. to eliminate the warning of packet encryption is disabled. but that will be such an unsafe act.. and i will never disabled this on the server that i setup. and i will never proposing / suggesting / recommending on disabling this feature..

i'm using rA with last week git hash not having need to comment on #define PACKET_OBFUSCATION_WARN. are u disable packet encryption on nemo patcher for this client? as far i patch that client with packet encryption enabled. u are exposing ur server for threat & vulnerability if u disabled packet encryption. read more on this topic. i would say.. before u follow some guide posted by others, u should check on it first before u trying on that guide. EDIT: please qoute my reply so that i get a notification of what u reply.

Firstly. I setup ur rA using git. Not svn.. svn is history already dude. ra has transitioned from svn to git years ago. Secondly. I just check rA. It appear that ur Git Hash: 9eaabd5 which on july 17. thus, this is not latest git hash. the latest rA would be Git Hash: ac1cf04 which was released yesterday. u need to fetch the update from https://github.com/rathena/rathena/commits/master then, see either still having the same problem or not.

it is not that rA not support the client. but the thing is.. those client cannot be patch by nemo patcher.. the restore login window patch broken for 2017-06-21 & newer clients.. during gravity implement the option to disable the selection of the doram race, it changes something on the login window. as nemo patcher are very outdated (last update was on end of may 2016). it cannot patch restore login window for these clients.. after u patch these client & u launch them.. it will closed back.. as cannot proceed to login window / login screen..

i would say.. better just do some search on youtube.. maybe u can get see some of the guide setting up webhosting using this 00webhos...

well.. good luck!

i dunno.. i would never use of something which it support already being terminated. just consider if got bugs / errors found later. i don't think it will be fix.. just check it last commit? been years ago.

well.. about this, i dunno.. u need to check it out by urself.. i never running on pre on rA.. not i'm sure on what episode it is..

Dude.. it is still the same. Either eA, rA or hercules. Still using the same grf.. u just need to grab Ragexe / RagexeRE client & Clientside English Translation to be made as GRF (Set the clientinfo.xml) and put these 2 inside the kRO Full Client and u are good to go

No problem. But u need find a mirror for older kRO & data folder (data.grf). If u are using 2017 kRO. U might end up getting client DC.. perhaps 2013 kRO or older.. i would rather choose over rA & just change server mode into pre-renewal. Less hassle.. and it is still 2nd job if in pre-renewal mode.