Jump to content

RCharles

Members
  • Posts

    154
  • Joined

  • Last visited

Posts posted by RCharles

  1. Do it in sql by querying.

     SELECT <column_name> FROM inventory WHERE <cloumn_name> = '<item_id_number>;

    this will display all that has eg. item no. 7777 in the inventory

    to delete:

     DELETE FROM inventory WHERE <column_name> = <item_ID>;

  2. When diffing your client using Shinn Diff Patcher do not enable

    - Read Data Folder First

    - Load Lua before Lub

    Also you need to use Lua that matches your client version:

    http://subversion.assembla.com/svn/ClientSide/Lua_Project/lubs/Lub%20Files%205.0.2/

    Also for some reason they said that every client comes with a compatible setup.exe

    There is someone here in rA that uploaded 3 different setup.exe, You may want to try it.

    http://rathena.org/b...&attach_id=1402

  3. The usual reason on why this happen is because your password is encrypted using md5 feature.

    Back from your 3ceam, I you enabled md5 feature. Do this:

    login_athena.conf

    // Store passwords as MD5 hashes instead of plaintext ?
    // NOTE: Will not work with clients that use <passwordencrypt>
    use_MD5_passwords: yes

    Config.php of ceres is like this:

    $CONFIG['md5_pass'] = '1'; 

    Thus when you aren't using md5 back from your 3ceam, disable md5. Do this:

    login_athena.conf

    // Store passwords as MD5 hashes instead of plaintext ?
    // NOTE: Will not work with clients that use <passwordencrypt>
    use_MD5_passwords: yes

    change to no to disable the use of md5

    Config.php of ceres is like this:

    $CONFIG['md5_pass'] = '1'; 

    change 0 to disable the use of md5

    I hope this helps.

  4. They said that there are version of setup.exe that does not fit with the client. Here is some setup.exe that you want to try http://rathena.org/b...&attach_id=1402

    It contains 3 setup.exe of different kind

    However, check your:

    mmo.h

    packet_db.txt

    make sure that your client match up to what lua version are you using

    don't patch with hklm to hkcu

    The popping out of setup.exe when running the client means that the configuration in the setup.exe is not saving.

  5. Im not 100% sure about this, but I have found this one:

    trunk/conf/battle/player.conf

    // The amount of HP a player will respawn with, 0 is default.
    // (Unit is in percentage of total HP, 100 is full heal of HP, 0 is respawn with 1HP total.) 
    restart_hp_rate: 0 
    
    // The amount of SP a player will respawn with, 0 is default. 
    // (Unit is in percentage of total SP, 100 is full heal of SP, 0 is respawn with 1SP total.) 
    restart_sp_rate: 0
    

  6. Details for command getpartyleader:

    * getpartyleader <party id>{,<type>};

    This function returns some information about the given party-id's leader. When type is ommitted,

    the default information retrieved is Character name of the party leader. Possible types are:

    1: Leader account id

    2: Leader character id

    3: Leader's class

    4: Leader's current map name

    5: Leader's current level as stored on the party structure (may not be

    current level if leader leveled up recently).

    If retrieval fails (leader not found or party does not exists), "null" is returned instead of character name,

    and -1 is returned for the other types.

  7. Be sure that you edit:

    mmo.h <trunk/src/common/mmo.h>

    #define PACKETVER 20120410

    change 20120410 to your client date. Dont FORGET to recompile

    Check your clientinfo for:

    <address>121.54.2.28</address>

    change 121.54.2.28 to your IP address

    <version>25</version>

    version that fits your client

    - clientinfo.xml should be located on RoFolder/data

  8. Hello my friends!

    I have created this topic to ask what is the most stable client (bug free and all) for the newst revision of rAthena. I know there is a lot there but to inform everyone what is the stable client is really great. So I hope you can reply on this thread.

    Thanks!

  9. I've noticed that when you are really outdated with your svn and when you like to run a update, you are faced with bunch of errors upon compiling.

    So, is there a way for the late outdated svn to update without facing this errors? and should not also affect the src mods you've made.

×
×
  • Create New...