Judas

Lol! Nope. This guy: http://www.eathena.ws/board/index.php?showuser=277725

Just noticed, that that client has shorter LEA byte-code, so the tail check failed. Fixed.

Even it's for fun, i think it's quite bad for the community, some of them can't help because they don't have enough time... Just saying, just saying....

Judas Ragnarok Services   I’ve been involved in Ragnarok for a quite a while. I’ve gained experience in the clientside and making various customizations. Below are the services that I provide:   List of Services: ➢ Full Server/Client Setup -  ($15)  
  Addons:  
Troubleshooting: If current customers run into problems regarding their setup, within my capabilities there will be no charge.   Accepted Payments: PayPal Only!     Notes: You are free to pm me about your concerns and discounts can be provided if needed.   If you would like a consultation about the above service, please PM me regarding that as well.     Fractured Dimension Instance (Tales of Xillia Inspired)
 

@Ossi: i would say drop this shit. this guy took 200$ for this tool and dissapeared after just some years of development. you dont even get a daim for your work where this guy got so much money for.
 
I decided to support InternalGuard from now on. its still in childhood but the tool have a big potential, im pretty sure with the right help Kaju will create something better then ten harmony.

Happy birthday to Judas

HAPPY BIRTHDAY

HAPPY BIRTHDAY JUDAS !!   

JUDAS

yep I tried with 2010-06-16 and it does indeed work. Make sure mmo.h is set correctly

UPDATE Harmony_Full_3.3.12_V3
 
special thanks to
 
Haruna
 
 
All Compiling errors/Warnings fixed under Linux.   Tested with linux 64 Bit system ,  if someone use a 32 Bit system and still get errors pls report them.
 
Added a  Full Patch File Harmony_Full_3.3.12_V3.patch
 
Added a Small Fix file to upgrade an existing V2 patch to  V3
 
links have been added on first post

Thanks Yommy/Rytech <3.
I'm working my ass off to get a hercules christmas patch out before the 25th, including some secret things as well as the new features this client provides (market, new gm tool, oktoberfest costume, and more)!

Hello folks!
 
I just want to suggest (if possible) to make a source-based-like per episode on Ragnarok Online story.
 
For example, If I want to be Juno Episode only, then, it will disable all renewal items/job classes and item_db's and NPC.
 
//Choose your Ragnarok Episode from 1 - 15.//1 - The beginning//2 - War of Emperium//3 - and so on....base on kRO.#define RO_EPISODE 5  
But this will not affect the RE and PRE-RE, you should do this manually in renewal.h. 
 
 
Is this possible or too much work for this?

you are missing some textures it seems ,
 
you can download my client file package if you want and merge it with your GRF or data folder
 
http://paid.endlessro.de/2013-08-07_Client_Side_Files.rar

i believe you need to use the onscript changebase ID

Actually the plan is to support all clients but yes already WeeDiff is there for 2012 so I am not too concerned for older clients right now.
Ofcourse you can post any bugs you find. 
 
 
 
 
I have added Custom Font patch. Test it out and let me know. Also Increase Attack Display patch has been fixed.

yeah they are pretty stable 2013-03-20 and 2013-08-07 are good.
data you can look at the clientside release section I beleive.

well 2013 neomind made a patch to make it fully functional as it did before. For 2012 clients I'm not aware if there is a patch for it.
The cancel probably is due to diffs or the clientinfo

this is what is needed: if you're using  a patcher that doesn't have the patch for it
 
 
6A 20 53 FF D6 83 C4 08 
 
to
 
6A 21 53 FF D6 83 C4 08

The provided converter is to transition from the old to the new format. It's already there.If you need to use the file for any other purpose I'd recommend you to look at the db2sql plugin code, and modify that to suit your needs. All the item db info is available there (including the default values for the missing fields), and you can change the fprintf format strings to suit your needs.
 
I am aware of that. But that's not an excuse for being stuck in the past with unreadable file formats. Tools can be easily edited and/or rewritten. Regular expressions are much harder to use (if not impossible), but that doesn't prevent you from writing a tool to convert the file to whatever format you find more suitable, and back to the libconfig format. The file in the repository is fine as it is, at least when it's updated, diffs are easier to read, and nobody can sneak in nasty, subtle changes that would pass unnoticed.Actually, it's been discussed since May 2013. 
Feel free to release one. I personally won't, as there's no need for it to be in the repository (other than making the Hercules database usable with other server emulators, which is outside our scope.) 
On a side note, the format has now new (optional) fields (see BindOnEquip). Those can't be converted to the "old" format, unless you add another field to it (but then it won't be the same old format anymore - that was one of its biggest weaknesses, it was impossible to add fields in a sane way without rewriting the entire file)
Yep. Hated the comma separated version (for anything other than machine parsing) since I saw it the first time. And as fields got added to it, it became harder and harder. 
 
There's a reason not to do that. We'd be back to a hard to read file format (the import scripts). I personally find it pointless to have the item db in SQL (other than for control panels and such), because, well, it's an info that gets read once on server startup, and cached in any case. SQL is useful if you only need to look up parts of it (like a control panel does), but quite pointless (and an annoyance to keep up to date) if all you need is to SELECT * on server startup.If one of the two formats were to go away, to me it'd be SQL. But it's gonna stay, mostly for Control Panel purposes.
You misunderstood the 'Inherit' point. Please re-read how it works.Inherit can only be used in the item_db2 to inherit the values defined in item_db for *the same item*. You can't have inheritance chains, as it's only a boolean. If your custom Knife[3] has 'Inherit: true' set, and you only define a script (i.e. because you want it to have 100 Atk instead of its standard value), it means it'll be exactly a Knife[3], with all other standard parameters from the item_db, and only the Atk you have overridden will be changed. This means that, if for some reason the official item is updated to have a different weight, you wouldn't need to edit yours, as the change will be propagated (unless you override it.)

that's just an etc item. So it doesn't need a viewID I beleive. All it needs is the sprite/texture stuff.
You can just duplicate it via iteminfo and see how it is setup. Then duplicate the item_db entry for it

this is what is needed: if you're using  a patcher that doesn't have the patch for it
 
 
6A 20 53 FF D6 83 C4 08 
 
to
 
6A 21 53 FF D6 83 C4 08

that's just an etc item. So it doesn't need a viewID I beleive. All it needs is the sprite/texture stuff.
You can just duplicate it via iteminfo and see how it is setup. Then duplicate the item_db entry for it

Update:
1) Allow chat flood has been modified to accept only till 127 (max chat is actually supposed to be a byte so values from 128-256 get considered as negative numbers).
2) So what if you want no limits? I have added a new patch which removes the chat limitation itself .
 
@kyeme - i will look into the rest today when i get home.
 
EDIT: please check out from the repository. I didn't get time to make a new rar yet.

I believe in login-server.conf
use_MD5_passwords: no  
Then you have this as well: ( I think this is what you wanted though, which sevenz posted below)
// Client MD5 hash check// If turned on, the login server will check if the client's hash matches// the value below, and will not connect tampered clients.// Note: see docmd5_hashcheck.txt for more details.client_hash_check: off// Client MD5 hashes// A player can login with a client hash at or below the account group_id.// Format: group_id, hashclient_hash: 0, 113e195e6c051bb1cfb12a644bb084c5client_hash: 99, cb1ea78023d337c38e8ba5124e2338ae