Jump to content

Mikegyver

Members
  • Posts

    399
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Mikegyver

  1. This is duplicate.. perhaps u could ask the following topic owner how he make it to maxl lvl 255
  2. it is impossible newbie got post more than 1K.. xD way to go sifu / master.. make it 2K.. xD
  3. wow.. here he go my master... looking forward the server get publish.. i volunteer to be beta tester.. ^ ^
  4. i think storing item in inventory, missing item in vending store & previewing equipment in both inventory & vending store already been fixed in those following rAthena git hash https://github.com/rathena/rathena/commit/9716233c842f731df3fed5281370e324b5f5f024 https://github.com/rathena/rathena/commit/55735ea8f88a1d68e3c39ab4f9140e05d56e50dd EDIT: for those who are using packets for 2017-01-25 & 2017-03-15 clients which got it from me. please check back the packet structure. it should always be packet_ver and then the keys. i guess i miss look & not really concern about the packet structure. thanks to @Lemongrass coz let me know about this. it should be like following. // 2017-01-25aRagexe packet_ver: 57 packet_keys: 0x066E04FE,0x3004224A,0x04FF0458
  5. I'm not farmiliar on compiling in windows OS as i don't like to have my computer to be install with lots of software.. for me, running on windows require u to install lots of softwares & each of the software is not that light.. i have heard some of it are heavy, in GB size.. seems i don't have extra storage, i install rathena inside linux server.. but for those who are not farmiliar with linux command, running on windows is much easier.. i think this guide / tutorial on server side running on windows. Perhaps this might help u.
  6. please clone rathena from rathena github repository. the one in svn no longer updated i think https://github.com/rathena/rathena
  7. try to patch recommended first.. i have see few cases.. some of the patches causing failed to connect to server.
  8. just check those following: 1st. packet_db_ver: default.. should be change into packet_db_ver: 53 2nd. do u disable packet encryption or not during patch the client with nemo patcher. if u disable it. u need to disable it too on server side at src/config/core.h in case u enable packet encryption, please check the packet_keys_use in the db/packet_db.txt.. the packet_keys should include with the key u diff with nemo patcher...
  9. hahaha.. yeah.. don't forget if u find the solution.. perhaps i can seek for help with my 2017-01-25aRagexeRE client too.. xD.
  10. Sorry.. i'm not too sure.. i myself not use that client. Instead i'm using 2017-01-25aRagexeRE client.. but, lots more patches fail on nemo for this client..
  11. well.. no so sure... i think @NeoMind just went hiatus for a while.. furthermore, at the time being, both rA & herc still not fully support yet 2015-11-04aRagexeRE client, thus both emulator not yet move support to 2016 client.. i think once all feature in 2015 client already fully support, then both emulator will added 2016 support to the emulator.. if both emu or either one of the emu already support 2016 clients & yet nemo patcher still not being fix with the several patches fail issue, then. we can conclude that nemo patcher is dead.. but, i don't think it will happen.. instead i think somebody among the dev will continue with the nemo patcher project.. just at the moment nobody bothering about this nemo patcher as both emulator development is currently still at 2015 client..
  12. i have see lots of private server using 2016 client already.. and as i told u.. nothing wrong with using newer clients. perhaps that the owner willing to contribute by proposing push request.. but, in this case, like what akkarin said, most of the server owner, they do their own background work and then don't bother sharing it, because "they're the best servers because they have newer stuff". in much more simple words.. the server owner want to be their server so exclusive.. and i have meet few of them.. so, if by helping others will help back this emulator in speed up supporting more newer client, so why not to contribute to it?
  13. just grab achievement_list.lub from this clientside english translation project. https://github.com/ROClientSide/Translation/tree/master/System
  14. well.. u should check on hercules github repository.. 4144 (one of the hercules developer keep pushing update on newer client packets). i'll bet hercules much more actively in support newer client.. see link below. most of 2016 packets already been added on hercules. so i guess it just matter of time of hercules will move support to more newer client (2017 clients).. besides that, there is nothing wrong with using newer clients. just consider ourself some kind of beta tester which later will provide info to the devs or might even propose a PR to support this newer client.. Looks like your post needs rewording. https://github.com/HerculesWS/Hercules/commit/ff8429634673855a1dc6e2924d4534aec8de6507 i think, the one will be problematic that causing the client is become unstable is nemo patcher as lots of patches failed.. anyway, glad to hear that & congrats to u. xD... about the missing itemInfo_sak.lub, u can patch the client to read itemInfo.lub in nemo patcher.. just look for Load Custom lua file instead of iteminfo*.lub. change to -> System/itemInfo.lub.. or either u can just rename itemInfo.lub into itemInfo_sak.lub
  15. perhaps u can create new title / status for those who actively involve. my suggestion, contributor title / status with some of donator privileage. just my suggestion...
  16. Yeap.. i agree too.. u can just reupload this client on hercules forum & seek help & advice there.. besides that, this kind of error i haven't yet experience by using rathena.. so i myself a little bit clueless here too..
  17. In src/common/mmo.h, do u define RE client code block?
  18. well.. that is weird tho.. that kRO full client is newer already compared to the RagexeRE client.. it should not bring any problem. do u use the latest version of nemo patcher?
  19. try this.. this is my nemo patch list.. so far i have no error with this patch list on any client version. but due to nemo not fully support 2016 & newer clients, i have to skip following patches as these patches failed on 2016 & newer clients Always use email for char deletion Ignore missing pallete Read msgstringtable Translate client Packet first key encryption Packet second key encryption Packet third key encryption Show cancel to service select 20170125 Profile.log
  20. Perhaps this could help u. This clientside translation should be the minimum to be clean grf. It just will translate the korean into english.
  21. Well.. i guess u just having problem with the packet encryption keys only..
  22. do u have try disable packet encryption on nemo patcher & disable packet obfuscation on src/core/config.h?
  23. I think u miss packet obfuscation / packet encryption...
  24. Perhaps this could help u to fix above..
×
×
  • Create New...