arisgamers

As I told, I will check the questID2Display.txt soon, sorry for the delay ( ).. Changelog: Limitted all Quest Entries to 6 # @r130: https://github.com/ROClientSide/Translation/commit/9962586acd3f6f370018f5b6c56af79fc19f9d91 (~30 entries was having > 6 #'s) Sorry for my impatient, i just want to help. But, thanks for your attention.

Checked QuestID2Display.txt from Quest ID 10000 - 12000 Found 1 mistake : 11337

I just checked QuestID2Display.txt started from quest id 12000 and up, found some mistake in quest with quest id : most of them have extra "#", and 2 of them have double message. If you let me know which quest are updated in commit : 77b029cea467f87e07bebbea39f33e350bfd1094 may be i can do better check. I will check QuestID2Display_iro.txt

Ragexe is executable file for renewal RagexeRE is executable file for sakray (rarely used today)

Something left from eAthena : https://github.com/eathena/eathena http://eathena.org/eathena/

Now i use commit : aa623db3b82c1258a6f3df670c660a3d48e6f2a4 Everything works fine, even if in QuestID2Display.txt, some quest have 7 "#". And i didn't see any change in QuestID2Display.txt I don't know what was wrong before. Edit : Just noticed. Now, no quest is shown in quest window.

Older client may work with newer data, but can not use new content in it, you need newer client to use newer content. Example : if you use old client (client that released before rebellion class), and update the data to the recent date. your client will still work, but can not have rebellion class. Rebellion data is at there, but will never used by old client, because old client do not know Rebellion. In order to have rebellion you need newer client (client that released after rebellion class).

For today kro : 1. Ragexe.exe is renewal 2. RagexeRE.exe is Sakray They remove classic ! so rsu-kro-rag-lite.exe will update renewal and rsu-kro-renewal-lite.exe will update sakray About YourRO.exe : 1. you can run older YourRO.exe with newer data (up to date) but 2. you can not run newer YourRO.exe with older data. Example : last ossi's client is 2013-12-23 : 1. you run rsu-kro-rag-lite.exe and got newer data, and you do not change YourRO.exe. Result : your client will still work. 2. you change YourRO.exe with 2014 version, and do not run rsu-kro-rag-lite.exe. Result : your client may have trouble. You should have a patched client (YourRO.exe) to use hercules. About clientinfo.xml, if not inside palette.grf, it should be in YourRO.grf; I forgot the exact location

The clientinfo.xml in ossi's client is inside palette.grf, you can extract and merge it back after editing it with grfbuilder (this tool already included in ossi full client download, under Tool folder). YourRO.exe in this client is already patched. You have to check these lines in [hercules directory]srccommonmmo.h make sure the packetver is same with your client date. And if you make any change, don't forget to recompile it. NB : If you want to patch your own client you can find some unpatched Ragexe.exe in: http://k3dt.eu/Ragexe/unpacked/ 2014-02-05bRagexe.exe is the last stable one. Note : your client data should be updated first before you use newer client, this can be done by running rsu-kro-rag-lite.exe (this file made by Ai4rei, and already included in ossi's client)

You are doing some mistake when creating database, your database are not created. This is copied from patskie guide above (I add some hint for workbench 6.1 in bold note): I hope this can help.

Just rename ItemInfo.lua to ItemInfo.lub and place it in [your client dir]System

Your packet are not listed in : srcmappacket.h Make sure your client date is listed in that file. And don't forget to change packetver in : srccommonmmo.h and recompile your server. Note : As for now the best 2014 client is 2014-02-05bRagexe.exe

That QuestID2Display.txt work with your client ? What make it not work with mine ?

I think it has exactly 6 "#" : [Quest Number]#[Quest Title]#[sG_FEEL (not sure what is this )]#[Que_NOIMAGE (Quest Image, maybe )]# [Quest Message]# [Another Message (sometimes empty)]# edit : Quest number 14133 is not the only 1, there is some others like quest number 14125. I have removed extra "#" from 14125 & 14133, and still not working All quest which has more than 6 "#" will give trouble, not only those 2. If you can tell me which quest number is newly updated prior 8-1-2014, i will help you checking those quest.

That's happen to Eden Quest lvl 86 - 90 too. if you already done any of those quest, and turn in, the quest will be in waiting state (waiting for 3 hours before it can be re-taken again). And if you didn't re-take the quest again until reaching lvl 91 and up, those quest will stay in waiting quest (not removed from quest list)

It Crashes at what time? Crashed right after started, can not run at all. edit : found some suspicious lines : Isn't it has too many "#" ?

Update do not work again (I pulled on 8-1-2014). Make client crashed again.

I hope this link can help you : http://herc.ws/wiki/Category:Configuration

to change max base lvl, edit srccommonmmo.h : recompile your hercules, and edit the exp database : for pre-renewal : dbpre-reexp.txt for renewal : dbreexp.txt for job lvl: not found yet to change exp rates, you can edit confbattleexp.conf : to change drop rates, you can edit confbattledrops.conf :

If you mean your attack damage come a bit later after your attack animation, then check this file : confbattlebattle.conf and find these lines : and set delay_battle_damage to no. Note : By hercules default delay_battle_damage is set to yes; but it is better to set it to no.

What is your old client date ? I don't think setup.exe is changed. However if you patch your client it may replaced with the korean version, so it is recommended to back up your english version setup.exe (copy it to another folder) before patching your client.

bump

sound like your server failed to connect to mysql database. Check these : 1. Patskie's step 2-4 : in confchar-server.conf : in confmap-server.conf : Those userid & password must be match with the one in login database (Patskie's step 31, you should change s1 & p1 to whatever in your char-server.conf & map-server.conf) 2. from Patskie's step 11 : make sure in MySQL Workbench you have user with same name and password with those part from your confinter-server.conf (which written in bold)

I used MySQL 5.6 + workbench 6.1 prior changed it to MariaDB. The graphical interface is different but that shouldn't be a problem. After you installed Workbench you should have a connection named "root", it can be seen in first interface. You can open it by double clicking it, then you can make "hercules" & "log" schema, and follow the rest of the guide.

Will learn about that atcommand, and thanks for the answer.