jaBote

Open the client with a hex editor, look for the string, then change it manually. It isn't way too hard but may be somewhat difficult if you haven't ever hexed anything. I suggest you to give it a try yourself.
 
IDK what hex editors are currently in use, I still use XVI32 which is still good in my opinion. Here is its official webpage for download: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm

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

with Renewal Features:
In src/map/status.c
str = (int)(rstr + (float)dex/5 + (float)st->luk/3 + (float)((TBL_PC*)bl)->status.base_level/4); change for:
str = (int)(rstr + (float)dex/5 + ((rstr/10)*(rstr/10))+ (float)st->luk/3 + (float)((TBL_PC*)bl)->status.base_level/4);

Yes, it is possible, but your server will only work within your LAN. Simply set your servers IP to your LAN IP and distribute a client that points to your LAN IP.
 
Beware your LAN IP will sometimes change, thus making your users unable to connect unless you change your IP and make all the clients have the same IP and so...

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

Hi.
 
Are you trying to make a direct upgrade from rAthena to Hercules by running our upgrades on top of a rAthena database? This doesn't work that way.
 
Try to get your rAthena database to its original state, then make a backup and work on the backup. Try using these upgrades I've just revised:
 
This one for the main database upgrade:
-- rAthena to Hercules main database upgrade query.-- This upgrades a FULLY UPGRADED rAthena to a FULLY UPGRADED Hercules-- Please don't use if either rAthena or Hercules launched a SQL update after last revision date of this file.-- Remember to make a backup before applying.-- We are not liable for any data loss this may cause.-- Apply in the same database you applied your main.sql-- Last revision: November 10, 2013, 19:00-- Drop table `skillcooldown` since it's not used in HerculesDROP TABLE IF EXISTS `skillcooldown`;-- Upgrades for table `cart_inventory`ALTER TABLE `cart_inventory` MODIFY `equip` INT(11) UNSIGNED NOT NULL default '0', MODIFY `bound` tinyint(1) unsigned NOT NULL default '0';-- Upgrades for table `char`ALTER TABLE `char` DROP COLUMN `moves`, ADD `slotchange` SMALLINT(3) UNSIGNED NOT NULL default '0', ADD `char_opt` INT( 11 ) UNSIGNED NOT NULL default '0', ADD `font` TINYINT( 3 ) UNSIGNED NOT NULL DEFAULT '0';-- Upgrades for table `guild_storage`ALTER TABLE `guild_storage` MODIFY `equip` INT(11) UNSIGNED NOT NULL default '0', MODIFY `bound` tinyint(1) unsigned NOT NULL default '0';-- Upgrades for table `inventory`ALTER TABLE `inventory` MODIFY `equip` INT(11) UNSIGNED NOT NULL default '0', MODIFY `bound` tinyint(1) unsigned NOT NULL default '0';---- Table structure for table `sql_updates`--CREATE TABLE IF NOT EXISTS `sql_updates` ( `timestamp` int(11) unsigned NOT NULL, `ignored` enum('Yes','No') NOT NULL DEFAULT 'No', PRIMARY KEY (`timestamp`)) ENGINE=MyISAM;-- Existent updates to enterINSERT INTO `sql_updates` (`timestamp`) VALUES (1360858500);INSERT INTO `sql_updates` (`timestamp`) VALUES (1360951560);INSERT INTO `sql_updates` (`timestamp`) VALUES (1362445531);INSERT INTO `sql_updates` (`timestamp`) VALUES (1362528000);INSERT INTO `sql_updates` (`timestamp`) VALUES (1362794218);INSERT INTO `sql_updates` (`timestamp`) VALUES (1364409316);INSERT INTO `sql_updates` (`timestamp`) VALUES (1366075474);INSERT INTO `sql_updates` (`timestamp`) VALUES (1366078541);INSERT INTO `sql_updates` (`timestamp`) VALUES (1381354728);INSERT INTO `sql_updates` (`timestamp`) VALUES (1381423003);INSERT INTO `sql_updates` (`timestamp`) VALUES (1382892428);INSERT INTO `sql_updates` (`timestamp`) VALUES (1383162785);INSERT INTO `sql_updates` (`timestamp`) VALUES (1383167577);INSERT INTO `sql_updates` (`timestamp`) VALUES (1383205740);INSERT INTO `sql_updates` (`timestamp`) VALUES (1383955424);-- Updates to table `storage`ALTER TABLE `storage` MODIFY `equip` INT(11) UNSIGNED NOT NULL default '0', MODIFY `bound` tinyint(1) unsigned NOT NULL default '0';---- Table structure for table `account_data`--CREATE TABLE IF NOT EXISTS `account_data` ( `account_id` int(11) unsigned NOT NULL default '0', `bank_vault` int(11) unsigned NOT NULL default '0', `base_exp` TINYINT( 4 ) UNSIGNED NOT NULL default '100', `base_drop` TINYINT( 4 ) UNSIGNED NOT NULL default '100', `base_death` TINYINT( 4 ) UNSIGNED NOT NULL default '100', PRIMARY KEY (`account_id`)) ENGINE=MyISAM; -- Saving bank_vault data from rAthena's login table-- to our account_data table. There may be some not working cases.INSERT INTO `account_data` (`account_id`, `bank_vault`) SELECT `account_id`, `bank_vault` FROM `login` WHERE `bank_vault` > 0 ;-- Dropping bank_vault column from login tableALTER TABLE `login` DROP COLUMN `bank_vault`; upaste.me mirror: http://upaste.me/7fbc8490ebb57a6a
 
 
And this one for the logs database:
-- rAthena to Hercules log database upgrade query.-- This upgrades a FULLY UPGRADED rAthena to a FULLY UPGRADED Hercules-- Please don't use if either rAthena or Hercules launched a SQL update after last revision date of this file.-- Remember to make a backup before applying.-- We are not liable for any data loss this may cause.-- Apply in the same database you applied your logs.sql-- Last revision: November 10, 2013, 19:00-- Upgrades to table `picklog`ALTER TABLE `picklog` MODIFY `type` enum('M','P','L','T','V','S','N','C','A','R','G','E','B','O','I','X','D','U') NOT NULL default 'P';-- Drop table `cashlog` since it's not used in HerculesDROP TABLE IF EXISTS `cashlog`; upaste.me mirror: http://upaste.me/a011849121f6f38c
 
Hope this helps you!

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

you could make a script for that
 
- script reloadnpcfile -1,{OnInit: bindatcmd "reloadnpcfile",strnpcinfo(3)+"::OnAtcommand"; end;OnAtcommand: if (getgmlevel() < 99) end; atcommand "@unloadnpcfile " + .@atcmd_parameters$[0]; atcommand "@loadnpc " + .@atcmd_parameters$[0]; message strcharinfo(0), "NPC file " + .@atcmd_parameters$[0] + " reloaded if you didn't get any problem with the other commands. AVOID RELOADING ANY MOBS OR MAPFLAGS WITH THIS COMMAND."; end;}

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

* jaBote switches on @Ind mode *
 
rAthena to Hercules database converters
 
Hello~! What?!
I've observed a big rise of rAthena to Hercules database conversion requests this week, so I've just revised again the converters I made before and will be releasing on the repository so that people can find them more easily. What does that do?
We have two new .SQL files on our repository that make the conversion easy. One is for applying on the main ragnarok table (sql-files/rathena-main-upgrade.sql) and the other is for the logs one (sql-files/rathena-logs-upgrade.sql).Please remember to make a backup prior to converting the database, just in case something goes wrong. This is meant to convert a fully upgraded rAthena to a fully upgraded Hercules. If you have some uninstalled rAthena upgrades please install them first. Avoid using it if there has been an upgrade posted in rAthena newer than the date of the converter or, at least, you didn't apply it or know how to undo the changes (remember that main.sql is usually fully upgraded both in Hercules and in rAthena). Some data (especially the data we don't use here on Hercules may be lost on the conversion). We'll not be resposible for this. How does it work?
Plain and simple: just load them on the respective databases you have in rAthena, as if they were the original main.sql or logs.sql. Obviously enough, they won't work if you don't have CREATE, ALTER, INDEX and DROP permissions (and maybe others too) for the user(s) you'll be running this. These converters will NOT work if you changed the table names. Special thanks
rAthena staff for their database structure and upgrades. Hercules staff for the database structure and upgrades. All the users that requested the converters in their respective topics. for suggesting this to be committed to the repository. @Haru for last minute corrections. Disclaimer
As I warned before, there may be some intended or unintended data loss. Please make a backup before applying. This may get outdated quite quicly without me noticing about that. If that's so, please make a pull request or ping me to update the converter when I have time. I've avoided to name the files as "upgrades" here on the topic, but I've named them like that to make them have the name structure as the eAthena upgrade. This is NOT an offense to rAthena staff by any means. People are requesting this, so I made the conversion process easy for them, much like rAthena made a converter from eAthena and nobody got offended. Just that. Links~u!
Main database converter commit. Logs database converter commit. * jaBote switches off @Ind mode *

N.E.M.O. - Neo Exe Modification Organizer

Why another client patcher? well
1) WeeDiffGen - isn't working for 2013 clients + it depends on dlls (not that its a bad thing but i like scripting )
2) xDiffGen - yes its scripted but we need to depend on xdiff files.

so i made a new one based on xDiffGen and here it is. The patches are written in QtScript format.
Details of making a patch have already been written in a seperate topic - although now it needs to be updated with more details.
I have already converted most of the patches from xDiffGen.

Why this name? - well I didn't want it to be called * Gen No offense  
plus someone keeps calling me Nemo in IRC which gave me the idea

Snapshot
-----------------


How to use?
---------------------
1) First you need to specify your client file in Input Exe file box. If you browse to select the file name, Output Patched box gets updated with a _patched suffix filename automatically. Ofcourse you can select your own name for the output.
 
2) Next we need to load both the client and the scripts (patches & addons). so click Load Client button.
 
3) Select the patches you want . In case you patched once before (for whatever date) they will be saved in your local and you can use the Select Previous button to select them again. Also you can try using the Select Rcomnded button to select all the Recommended patches.
 
4) So your patches are selected and client is loaded what next but to Apply Patches  which will generate the output file. In 2.0 version , NEMO also generates a .secure.txt file containing the MD5, SHA1 and CRC32 values of the output exe file which you can use in various tools.
 
5) You can use the Save Profile and  Load Profile buttons for saving/reloading a set of patches & input values, that you have selected (even if they are not applied) for future use.
 
6) Whenever you apply patches to a client, NEMO updates the patchlist.log file (along with Inputlist.db) in the folder where NEMO.exe is. This file will contain the list of patches you have applied along with their IDs (do not tamper with either of them).
 
Changes in 2.0:
----------------------
1) I have made some obvious modifications to the interface (you can definitely see the change in case you have seen v1.0).
     i) Buttons have come downwards and is no longer strippable (toolbar has been fixed in position)
 
     ii) New status Label has been added which shows your currently loaded client date and how many patches are selected.
 
     iii) NEMO now has support for Addons - scripts that are meant to retrieve data from the client and do its own thing (not patch the client).
          All the Extract xDiff patches has been added here already. 1 extra addon will be coming soon once i can fix it.
 
     iv) New Filter box has been added which does live search (i.e. filter as you type) for filtering out only the patches u want to see.
           For e.g. if you type color, it will only show patches that have the string color in either it's name or the description.
          You can also use regular expression . Also you can sort the columns now
 
    v) An upcoming feature - Test Patches. this one you can use for testing a newly added patch for a variety of clients that you select.
 
2) NEMO is no longer there in SVN. I have shifted it to GitHub . The rar file uploaded has the .git file so you should be able to directly pull to get updates. But just in case I have also provided the repository link below.
 
Remember to pull for updates before using NEMO and let me know if you are facing any bugs or issues or if i have missed out on anything. Enjoy .
 
Repository: https://github.com/MStr3am/NEMO.git
 
Download Link: NEMO zip file 

Make the NPC have the same script as of a dead branch or adjust it to your needs.
 
Dead branch script:
monster "this",-1,-1,"--ja--",-1,1,""; the -1 after the "--ja--" parameter is the monster ID. If you change it to -2 it'll get a mob from the porings list and if you change it to -3 will summon just like a bloody branch. Also, if you set that to a valid mob ID it'll summon the monster with that ID.

For first error: Try enclosing all arguments to the monster script command in brackets? Some changes were made to the script parser engine yesterday, so I'm still new to this because I haven't had time to test yet.
 
For the second error, it seems you're missing a file in your GRF. Maybe it's a custom item you wanted to have a custom sprite and didn't add it properly?

¡Hola!
 
Me alegro de que hayas decidido volver al universo de Ragnarok Online. Comenzaré por comentar las diferencias básicas entre Hercules y rAthena para que puedas decidir emulador. Es obvio que, como estás en el foro de Hercules, la gente intente hacerte quedar con el emulador Hercules, aunque trataré de ser lo más neutral posible para que tengas una idea objetiva:
 
En Hercules los desarrolladores son muy activos aunque la comunidad es algo menos activa; en rAthena la comunidad es muy activa aunque los desarrolladores lanzan comparativamente muchas menos revisiones de código. Simplemente hay que contrastar las 59 revisiones que hizo rAthena entre septiembre y octubre con las 266 revisiones (¡más del cuádruple!) que Hercules lanzó en ese mismo tiempo. Dado que los desarrolladores son muy activos, hace ya tiempo se hicieron unas revisiones de optimización de uso de recursos en Hercules que rAthena nunca hizo, por lo que ahora Hercules se puede ejecutar (sin usuarios ni NPCs) en ~90 MB de RAM, comparados con los ~256 MB que consume rAthena (y consumía Hercules antes de la optimización) para lo mismo. También se mejoró el uso de proceso pero no he llegado a medirlo bien. Los desarrolladores de scripts y entradas en las bases de datos son más activos en rAthena, por lo que aquí vamos algo más lentos en ese apartado. Asmismo, los desarrolladores terceros de complementos al servidor están más activos en rAthena de momento debido a que tiene mucha más popularidad: Hercules es aún una comunidad reciente. Hay miles de puntos de comparación más, aunque veo feo hacer una comparación completísima cuando solo pides soporte, así que solo he ido a los puntos más clave. Por ejemplo, de momento rAthena ha añadido recientemente las skills de Rebellion aunque se basan en una información que no es muy precisa; en Hercules estamos esperando a tener información precisa antes que implementarlas de cualquier manera.

 
Lo anterior es mucho texto pero te ayuda muy poco a obtener el emulador y lo que necesitas para hacerlo funcionar.
 
Para obtener el emulador necesitas un programa que sepa manejarse con Git. Para Windows están TortoiseGit (para el que a su vez necesitas instalar mSysGit) o alguno otro. Hace tiempo hice una guía (aún totalmente válida) sobre cómo hacerlo: enlace. Los sistemas GNU/Linux ofrecen soporte nativo simplemente con instalar Git.
 
Además, para hacer funcionar el emulador en tu máquina necesitas tener instalado (en Windows) al menos algún compilador como Microsoft Visual C++ (versión 2009 o superior, de momento la versión 2013 no tiene soporte). Para ello puedes utilizar mi guía de compilación (el método de obtención de Microsoft Visual C++ ha cambiado ligeramente, pero no es nada difícil aún aún): enlace. También hay guías de instalación y compilación para sistemas GNU/Linux: aquí. Como anotación, recuerda compilar tu emulador con soporte a la fecha del cliente que quieras utilizar.
 
No sé cuánto tiempo llevas sin manejar un servidor, pero antes había capacidad de guardar los personajes bajo un motor de tablas de texto (emulador TXT). Ahora esa capacidad ha sido eliminada y únicamente se permite utilizar emuladores en SQL (debes instalar MySQL) debido a que ofrece muchísima mejora respecto a los antiguos emuladores TXT pero complica ligeramente la instalación y puesta en marcha de un servidor de juego.
 
Por último, no conozco mucho de los clientes (soy muy malo en ese aspecto), aunque parece que la descarga de cliente que ofrece @ossi0110 en su tema (enlace al tema en inglés) está teniendo mucho éxito, porque en la misma descarga ofrece un cliente de kRO completo junto a un exe de prueba prehecho, más el mismo exe y todas las herramientas necesarias para trastear con el cliente.
 
Espero haber sido de ayuda. Quizá he sido muy extenso aunque prefiero extenderme a no ser claro .
 
¡Un saludo!

You can make a script using getrandmob for this:
 
- script randomdisguise -1,{OnWhisperGlobal: if (getgmlevel() < 60) end; // Change the 60 to any minimum GM value you want to check set .@randmob, getrandmob(150,0); // 1st parameter = max level of the mob; 2nd parameter: 0 if fetching from dead branch list, 1 from poring list, 2 from bloody branch list atcommand "@disguise "+.@randmob; message strcharinfo(0),"You've been disguised as: " + strmobinfo(1,.@randmob); end;} Just whisper to it while having enough GM level to get disguised.

The only one I know is recording the replay yourself and then capture it with a screen recorder which allows saving to mp4. 

Try this:
- script Map killer -1,{OnMinute00: if ((gettime(3)%5)==0) atcommand "@killmonster2 gef_fild13"; // CHANGE THE MAP NAME end;}

From the script of Master Jabote, you will need to whisper "randomdisguise" in your chatbox.

Now I realise I've maybe been too short on that explanation. I'll add a sample script of nested menus to elaborate a bit:
 
prontera,119,199,4 script DJ with categories 985,{ mes "Hey, I can play a song for you."; mes "What category do you want to browse?"; switch(select("Rock:Jazz:Rhythm and Blues:HipHop:Nevermind")) { // a : means a new category on a select. case 1: // Rock mes "Select song"; switch(select("Rock 1:Rock 2:Rock 3:Nevermind")) { case 1: playBGMall "Your Rock 1 BGM","prontera"; break; case 2: playBGMall "Your Rock 2 BGM","prontera"; break; case 3: playBGMall "Your Rock 3 BGM","prontera"; // No break needed // No default case, so this won't do anything and go to the NPC ending. } break; // Directly finishes the switch statement. if not present this will also trigger case 2 and followings. case 2: // Jazz mes "Select song"; switch(select("Jazz 1:Jazz 2:Jazz 3:Nevermind")) { case 1: playBGMall "Your Jazz 1 BGM","prontera"; break; case 2: playBGMall "Your Jazz 2 BGM","prontera"; break; case 3: playBGMall "Your Jazz 3 BGM","prontera"; // No break needed // No default case, so this won't do anything and go to the NPC ending. } break; case 3: // R&B mes "Select song"; switch(select("R&B 1:R&B 2:R&B 3:Nevermind")) { case 1: playBGMall "Your R&B 1 BGM","prontera"; break; case 2: playBGMall "Your R&B 2 BGM","prontera"; break; case 3: playBGMall "Your R&B 3 BGM","prontera"; // No break needed // No default case, so this won't do anything and go to the NPC ending. } break; case 4: // HipHop mes "Select song"; switch(select("HipHop 1:HipHop 2:HipHop 3:Nevermind")) { case 1: playBGMall "Your HipHop 1 BGM","prontera"; break; case 2: playBGMall "Your HipHop 2 BGM","prontera"; break; case 3: playBGMall "Your HipHop 3 BGM","prontera"; // No break needed // No default case, so this won't do anything and go to the NPC ending. } break; default: // Case 5 or any other not observed in that menu mes "OK, I'll not play anything"; // Break not needed in the last case } mes "cya!"; close;}  
For more info about the commands used here, please refer to doc/script_commands.txt.
Hope this helped you a bit more.

Set use_md5_passwords to yes in conf/login-server.conf:
// Store passwords as MD5 hashes instead of plaintext ?// NOTE: Will not work with clients that use <passwordencrypt>use_MD5_passwords: yes  
If you've already done this and are still experiencing errors, execute sql-files/tools/convert_passwords.sql in your main schema to convert your existing passwords into MD5 hashes.