Jump to content

Mikegyver

Members
  • Posts

    399
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Mikegyver

  1. 12 minutes ago, luan122 said:

    Same, do you get this error with this patch?


    does packet obfuscation change something?
    in your patch i put since it hasn't

    
    61 Disable Packet Encryption

    because my source has the encrypt lines commented.

    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.

  2. On 8/15/2017 at 1:21 PM, melv0 said:

    i was install gcc-5 and g++-5 but when i run ./configure

    i got error like this

     

     

    20840159_10213744762443354_873618171_n.png

    OS debian 8

    version server : :last

    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

  3. 5 hours ago, mrjnumber1 said:

    let me know (in rathena discord) any time if there's something else you need, i put other stuff in secretdataz thread. it's just a matter of time before other patches break for the same reason.. so!

    I see.. i finally get what u mean earlier..

     

    15 hours ago, mrjnumber1 said:

    go to secretdataz thread, not this one.

    Thanks dude.. much appreciate for these releases.

     

  4. 20 hours ago, mrjnumber1 said:

    i have 6 or 7 update patches in secretdataz thread, i just posted those 2 here that were relevant to rytech and discussion of this client.

    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.

  5. 20 hours ago, mrjnumber1 said:

    go to secretdataz thread, not this one.

    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.

  6. 34 minutes ago, mrjnumber1 said:

    hey rytech, wanted to let you and the public know i updated the restore login window/cancel to login window patches to work.

    RestoreLoginWindow.qs https://paste2.org/pLb2InJt

    CancelToLoginWindow.qs https://paste2.org/IB61skXD

    ik shared these also with secretdataz for that fork of NEMO

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

  7. 7 hours ago, Kaze said:

    I'm trying to use this Client 2016-2-03RagexeRE.

    The rest is working fine.
    Is there a way we can use this? seems like NEMO Patcher is really outdated we can't able to patch them.

    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.

     

  8. 3 hours ago, hannicaldummy said:

    if i comment #define PACKET_OBFUSCATION too i can't login :/

    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

  9. 7 minutes ago, hannicaldummy said:

    You actually made that client for me xD

     

     

    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..

  10. 7 minutes ago, hannicaldummy said:

    I'm using a new one that i downloaded a few minutes before post here about the issue xD

    
    // Copyright (c) rAthena Dev Teams - Licensed under GNU GPL
    // For more information, see LICENCE in the main folder
    #ifndef _CONFIG_PACKETS_H_
    #define _CONFIG_PACKETS_H_
    
    /**
     * rAthena configuration file (http://rathena.org)
     * For detailed guidance on these check http://rathena.org/wiki/SRC/config/
     **/
    
    #ifndef PACKETVER
    	#define PACKETVER 20170517
    #endif
    
    #ifndef PACKETVER_RE
    	/// From this point on only kRO RE clients are supported
    	#if PACKETVER > 20170517
    		#define PACKETVER_RE
    	#endif
    #endif
    
    #if PACKETVER >= 20110817
    	/// Comment to disable the official packet obfuscation support.
    	/// This requires PACKETVER 2011-08-17 or newer.
    	#ifndef PACKET_OBFUSCATION
    		#define PACKET_OBFUSCATION
    
    		// Define these inside src/custom/defines_pre.h or src/custom/defines_post.h
    		//#define PACKET_OBFUSCATION_KEY1 <key1>
    		//#define PACKET_OBFUSCATION_KEY2 <key2>
    		//#define PACKET_OBFUSCATION_KEY3 <key3>
    
    		/// Comment this to disable warnings for missing client side encryption
    //		#define PACKET_OBFUSCATION_WARN
    	#endif
    #else
    	#if defined(PACKET_OBFUSCATION)
    		#error You enabled packet obfuscation for a version which is too old. Minimum supported client is 2011-08-17.
    	#endif
    #endif

    That's my packets.h, is alread commented :/

    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.

  11. 2 hours ago, hannicaldummy said:

    I'm also having this problem, but comment the line on pachets.h didn't solve :o

     

    What else can i do, i've searched all forum but ervery post about says to comment that line, i'm using latest svn

    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.

  12. 4 minutes ago, GodKnows Jhomz said:

    Ohh, i see. Thanks for the info. Hopefully the rA supports the client soon.

    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..

  13. 22 minutes ago, yuchinin said:

    Sorry for late reply, but I think I don't have the time to guide you step by step on how to host@@
    If you totally have no knowledge on hosting you may try host it locally by using XAMMP first, after you success about XAMMP on your local computer then you can copy the website file to real hosting.

    *Just a note that XAMMP are merely for development purpose, don't ever try to use it for real hosting unless you know what you are doing.

    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...

  14. 5 minutes ago, Wolfric said:

    And I can edit the grf JUST like back with eAthena in that pre-Renewal Mode?

     

    What else would be different?

    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

  15. 3 minutes ago, Wolfric said:

    Bleh..... Guess I'll have to see if I find a mirror somewhere on the internet.

     

    Thanks a lot for your replies!

    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.

×
×
  • Create New...