Hercules Wiki - User contributions [en]

Hercules Wiki:Welcome to the wiki

2013-07-07T16:00:53Z

Uzieal: Created page with "= Hercules Wiki = Welcome to the Hercules Wikipedia! Here, one may be able to find documentation pertaining to nearly all aspects of operation, configuration & implementation..."

= Hercules Wiki =

Welcome to the Hercules Wikipedia! Here, one may be able to find documentation pertaining to nearly all aspects of operation, configuration & implementation of the Hercules Ragnarok Online Emulation Project. One may use the Hercules Wikipedia to reference or follow many of the useful guides found here to properly preform some of the many complex or difficult tasks involved with emulation operation and function. All members of the Hercules Wiki are both allowed and encouraged to contribute to the development and expansion of the Wikipedia. So, have you contributed to your Wiki today?

Import folder

2013-07-03T08:02:18Z

Uzieal: /* Import folder Introduction */

=Import folder Introduction=
The Import Folder is used to import virtually all of your configuration changes and settings into the core of the Hercules emulator without ever making changes to any .conf files after it is initially configured. This is very helpful when Creating a New Server Build, Compiling , or Updating to the Latest SVN this will allow retention of all the settings you previously configured without having to deal with possible overwrite conflicts from an SVN Update or change over to a New Server Build.

=How it works=
So, It works as such; Once you have configured all of the files you wish to configure within the Conf directory of your server side you will take those same settings and copy them to the corresponding import directory files. For Example: Lets say you make the following changes to;

'''svn/conf/battle/client.conf''' ---> Make your desired changes, in this case we are changing hair and dye settings.
// Valid range of dyes and styles on the client.
min_hair_style: 0
max_hair_style: 27 ----> Changing to 40
min_hair_color: 0
max_hair_color: 8 ----> Changing to 200
min_cloth_color: 0
max_cloth_color: 4 ----> Changing to 100

'''svn/conf/battle/client.conf''' ---> We then simply copy only the changed setting lines into ---> svn/conf/import/client_conf.txt

max_hair_style: 40
max_hair_color: 200
max_cloth_color: 100

Since these three settings were the only ones we changed in this example these are the only configuration lines to copy from the .conf file into the corresponding import.txt file. This will now allow the server to directly import these changed settings. This can be done with any of the configuration files. The server reads .confs files within the conf directory first, however any settings configured within the /import/ folder will be read second, thus overwriting default settings. Please note over time settings have changed, so please compare Import.txt Files to any New Server Configuration Settings.

=Commonly Imported Settings=

The most common use of these files is for the following parameters:<br />
'''/conf/login_athena.conf''' -> /conf/import/login_conf.txt
login_port: 6900
account.engine: auto
account.sql.db_hostname: 127.0.0.1
account.sql.db_port: 3306
account.sql.db_username: ragnarok
account.sql.db_password: ragnarok
account.sql.db_database: ragnarok

'''/conf/char_athena.conf''' -> /conf/import/char_conf.txt
userid: s1
passwd: p1
server_name: rAthena
login_port: 6900
char_ip: 127.0.0.1
char_port: 6121
start_point: new_1-1,53,111

'''/conf/map_athena.conf''' -> /conf/import/map_conf.txt
userid: s1
passwd: p1
char_ip: 127.0.0.1
char_port: 6121
map_ip: 127.0.0.1
map_port: 5121

'''/conf/inter_athena.conf''' -> /conf/import/inter_conf.txt
sql.db_hostname: 127.0.0.1
sql.db_port: 3306
sql.db_username: ragnarok
sql.db_password: ragnarok
sql.db_database: ragnarok
char_server_ip: 127.0.0.1
char_server_port: 3306
char_server_id: ragnarok
char_server_pw: ragnarok
char_server_db: ragnarok
map_server_ip: 127.0.0.1
map_server_port: 3306
map_server_id: ragnarok
map_server_pw: ragnarok
map_server_db: ragnarok
log_db_ip: 127.0.0.1
log_db_port: 3306
log_db_id: ragnarok
log_db_pw: ragnarok
log_db_db: ragnarok
log_login_db: loginlog
use_sql_db: no

=Conclusion=
The Import Folder is a powerful tool and is often overlooked by amateur developers, but it saves a lot of time and effort it is highly recommended to use. The import.txt files can be saved and used in any new build, just ensure you double check the pathways and corresponding configuration settings. The import folder is often incomplete or blank when downloading latest revisions, you will have to add the necessary files or overwrite the blank template files.

Import folder

2013-07-03T08:01:28Z

Uzieal:

=Import folder Introduction=
The Import Folder is used to import virtually all of your configuration changes and settings into the core of the Hercules emulator without ever making changes to==== after it is initially configured. This is very helpful when Creating a New Server Build, Compiling , or Updating to the Latest SVN this will allow retention of all the settings you previously configured without having to deal with possible overwrite conflicts from an SVN Update or change over to a New Server Build.

=How it works=
So, It works as such; Once you have configured all of the files you wish to configure within the Conf directory of your server side you will take those same settings and copy them to the corresponding import directory files. For Example: Lets say you make the following changes to;

'''svn/conf/battle/client.conf''' ---> Make your desired changes, in this case we are changing hair and dye settings.
// Valid range of dyes and styles on the client.
min_hair_style: 0
max_hair_style: 27 ----> Changing to 40
min_hair_color: 0
max_hair_color: 8 ----> Changing to 200
min_cloth_color: 0
max_cloth_color: 4 ----> Changing to 100

'''svn/conf/battle/client.conf''' ---> We then simply copy only the changed setting lines into ---> svn/conf/import/client_conf.txt

max_hair_style: 40
max_hair_color: 200
max_cloth_color: 100

Since these three settings were the only ones we changed in this example these are the only configuration lines to copy from the .conf file into the corresponding import.txt file. This will now allow the server to directly import these changed settings. This can be done with any of the configuration files. The server reads .confs files within the conf directory first, however any settings configured within the /import/ folder will be read second, thus overwriting default settings. Please note over time settings have changed, so please compare Import.txt Files to any New Server Configuration Settings.

=Commonly Imported Settings=

The most common use of these files is for the following parameters:<br />
'''/conf/login_athena.conf''' -> /conf/import/login_conf.txt
login_port: 6900
account.engine: auto
account.sql.db_hostname: 127.0.0.1
account.sql.db_port: 3306
account.sql.db_username: ragnarok
account.sql.db_password: ragnarok
account.sql.db_database: ragnarok

'''/conf/char_athena.conf''' -> /conf/import/char_conf.txt
userid: s1
passwd: p1
server_name: rAthena
login_port: 6900
char_ip: 127.0.0.1
char_port: 6121
start_point: new_1-1,53,111

'''/conf/map_athena.conf''' -> /conf/import/map_conf.txt
userid: s1
passwd: p1
char_ip: 127.0.0.1
char_port: 6121
map_ip: 127.0.0.1
map_port: 5121

'''/conf/inter_athena.conf''' -> /conf/import/inter_conf.txt
sql.db_hostname: 127.0.0.1
sql.db_port: 3306
sql.db_username: ragnarok
sql.db_password: ragnarok
sql.db_database: ragnarok
char_server_ip: 127.0.0.1
char_server_port: 3306
char_server_id: ragnarok
char_server_pw: ragnarok
char_server_db: ragnarok
map_server_ip: 127.0.0.1
map_server_port: 3306
map_server_id: ragnarok
map_server_pw: ragnarok
map_server_db: ragnarok
log_db_ip: 127.0.0.1
log_db_port: 3306
log_db_id: ragnarok
log_db_pw: ragnarok
log_db_db: ragnarok
log_login_db: loginlog
use_sql_db: no

=Conclusion=
The Import Folder is a powerful tool and is often overlooked by amateur developers, but it saves a lot of time and effort it is highly recommended to use. The import.txt files can be saved and used in any new build, just ensure you double check the pathways and corresponding configuration settings. The import folder is often incomplete or blank when downloading latest revisions, you will have to add the necessary files or overwrite the blank template files.

Login Background

2013-07-03T07:15:15Z

Uzieal:

''( Wanted Page done by Uzieal ~ July 2, 2013 Please leave for contact / update / quality control reasons. Thank you! )''
=Login Background Introduction=

First of all there are a few formats to keep in mind, There are older Clients (before 2010-01-26 RagexeRE) that simply use one Login Background and Newer Clients which use Two Alternating backgrounds that are formed from slices that the Client uses to make up a single larger image. Where as Older Clients using the single background format do not make use of the split / sliced images to create a Client Login Background.

=Clients before 2010-01-26 RagexeRE=
These clients use "bgi_temp.jpg" (Single image as a Background)
For these older clients simply create a new 1024x768 Jpeg Image of your own and name it "bgi_temp.jpg" then place it in;
the folder ...svn/data/texture/À¯ÀúÀÎÅÍÆäÀÌ½º/

( ''Or Alternatively'' )

the folder ...svn/data/texture/유저인터페이스/
Then your done and you should have a working Login Background (Note: This is only for clients before "2010-01-26 RagexeRE")

=Clients beyond 2010-01-26 RagexeRE=
These clients use 24 sliced images to make up two 1024x768 Bitmap Images that Alternate from one login to the next.

( ''First Login Background'' ) - [''Alternating''] is made up of these slices;

"t2_¹è°æ1-1.bmp", "t2_¹è°æ1-2.bmp", "t2_¹è°æ1-3.bmp", "t2_¹è°æ1-4.bmp"

"t2_¹è°æ2-1.bmp", "t2_¹è°æ2-2.bmp", "t2_¹è°æ2-3.bmp", "t2_¹è°æ2-4.bmp"

"t2_¹è°æ3-1.bmp", "t2_¹è°æ3-2.bmp", "t2_¹è°æ3-3.bmp", "t2_¹è°æ3-4.bmp"

"t2_¹è°æ4-1.bmp", "t2_¹è°æ4-2.bmp", "t2_¹è°æ4-3.bmp", "t2_¹è°æ4-4.bmp"

( ''Second Login Background'' ) - [''Alternating''] is made up of these slices;

"t3_¹è°æ1-1.bmp", "t3_¹è°æ1-2.bmp", "t3_¹è°æ1-3.bmp", "t3_¹è°æ1-4.bmp"

"t3_¹è°æ2-1.bmp", "t3_¹è°æ2-2.bmp", "t3_¹è°æ2-3.bmp", "t3_¹è°æ2-4.bmp"

"t3_¹è°æ3-1.bmp", "t3_¹è°æ3-2.bmp", "t3_¹è°æ3-3.bmp", "t3_¹è°æ3-4.bmp"

"t3_¹è°æ4-1.bmp", "t3_¹è°æ4-2.bmp", "t3_¹è°æ4-3.bmp", "t3_¹è°æ4-4.bmp"

Just because newer clients use two login backgrounds does not mean to utilize only a single login background you have to use an older client. With newer clients through "Diffing" your "Client.exe" you may choose to only use either the first or second login backgrounds. Keep in mind however, even if you choose to use a newer client and Diff it so you only have one login background you will still have to utilize the split / sliced image method to create a view-able & working login background.

=Ragnarok Login Background Splitting Tools=
''(Always be cautious when downloading)''

Now that we know about the formats lets pick a method of creation for new clients. There are many tools developed by various members of the Ragnarok emulation community to take care of correctly converting the splicing and splitting of a single Jpeg image you would like to use as your Login Background. Using one of these tools is the fastest most efficient method of creating a working login background for (2010-01-26 RagexeRE) and Newer Clients.

[http://rathena.org/board/index.php?app=core&module=attach&section=attach&attach_id=1882 Ragnarok Online Login Screen Generator (ROLSG)] --- ( Credit: Wiskovisky )

"[http://rathena.sourceforge.net/tools/login_background/ rAthena / Tools / Login_Background]" ---------------------- ( Credit: rAthena )

[https://raijero.svn.sourceforge.net/svnroot/raijero/dev/Brian/convert.php Convert.php] ----------------------------------------------------------- ( Credit: BrianL )

[http://rathena.org/board/files/file/2561-ragnarok-background-splitter/ RagBgSplitter_0.2] -------------------------------------------------- ( Credit: mkbu95 )

Most of these programs will split a 1024x768 Jpeg Image into 12 slices &

convert plus save them into Bitmap Image Slices in a specified directory.

=After Splitting Tool Conversion=

After using one of the above splitting tools to create our newly converted Jpeg to Bitmap images we then locate the directory in which the images were converted and stored or saved and we proceed to move these newly created slices from said directory in which they were saved into by the image slicing tool and (Depending on if you Diffed your Client to only allow one background or not) you then place all 12 or 24 of the spliced images into
the folder ...svn/data/texture/À¯ÀúÀÎÅÍÆäÀÌ½º/

( ''Or Alternatively'' )

the folder ...svn/data/texture/유저인터페이스/

=Alternative Manual Conversion=

Alternatively one could split a 1024x768 Jpeg image into 12 equal slices / segments using any number of programs and save them each individually in the Bitmap format then properly place and name the 12 manually sliced Bitmap images. For each of the Alternating Login Backgrounds if you choose to use both. Instead of using one of the Ragnarok Login Background Splitting Tools. Then save to the same directory listed in the above formatted steps.

=2012+ Clients Change Introduction=
Please note that in 2012+ Clients there seems to be a new format gravity has introduced to their Login Background. This change is from Dual Alternating Login Background Clients toa once again fixed single Login Background however there are other changes, most notably the image format. To create this single Login Background it should be comprised of the following files;

"t_¹è°æ1-1.bmp", "t_¹è°æ1-2.bmp", "t_¹è°æ1-3.bmp", "t_¹è°æ1-4.bmp"

"t_¹è°æ2-1.bmp", "t_¹è°æ2-2.bmp", "t_¹è°æ2-3.bmp", "t_¹è°æ2-4.bmp"

"t_¹è°æ3-1.bmp", "t_¹è°æ3-2.bmp", "t_¹è°æ3-3.bmp", "t_¹è°æ3-4.bmp"

"t_¹è°æ4-1.bmp", "t_¹è°æ4-2.bmp", "t_¹è°æ4-3.bmp", "t_¹è°æ4-4.bmp"

"t_¹è°æ1-1.tga", "t_¹è°æ1-2.tga", "t_¹è°æ1-3.tga", "t_¹è°æ1-4.tga"

"t_¹è°æ2-1.tga", "t_¹è°æ2-2.tga", "t_¹è°æ2-3.tga", "t_¹è°æ2-4.tga"

"t_¹è°æ3-1.tga", "t_¹è°æ3-2.tga", "t_¹è°æ3-3.tga", "t_¹è°æ3-4.tga"

"t_¹è°æ4-1.tga", "t_¹è°æ4-2.tga", "t_¹è°æ4-3.tga", "t_¹è°æ4-4.tga"

So far it is unknown if there are any tools to convert an image into this format automatically (hint hint), however you may manually create your own image. This is still sliced into 12 quadrants both in Bitmap and Targa format. If you do not wish to use this format, all you need to do is simply remove the existing images from the GRF / data folder directory. The newer GRF's have yet to get rid of the previous images for the Alternating Dual Login Backgrounds so if you decide that is the format you would rather use you should be able to use the previous format of Alternating Dual Login Backgrounds or Diff your Client to use the first or second login background.

Login Background

2013-07-02T08:57:24Z

Uzieal:

''( Wanted Page done by Uzieal ~ July 2, 2013 Please leave for contact / update / quality control reasons. Thank you! )''

'''Login Background Introduction-'''

First of all there are a few formats to keep in mind, There are older Clients (before 2010-01-26 RagexeRE) that simply use one Login Background and Newer Clients which use Two Alternating backgrounds that are formed from slices that the Client uses to make up a single larger image. Where as Older Clients using the single background format do not make use of the split / sliced images to create a Client Login Background.

'''Clients before 2010-01-26 RagexeRE''' use "bgi_temp.jpg" (Single image as a Background)
For these older clients simply create a new 1024x768 Jpeg Image of your own and name it "bgi_temp.jpg" then place it in;
the folder .../data/texture/À¯ÀúÀÎÅÍÆäÀÌ½º/
Then your done and you should have a working Login Background (Note: This is only for clients before "2010-01-26 RagexeRE")

'''Clients beyond 2010-01-26 RagexeRE''' use 24 sliced images to make up two 1024x768 Bitmap Images that Alternate from one login to the next.

( ''First Login Background'' ) - [''Alternating''] is made up of these slices;

"t2_¹è°æ1-1.bmp", "t2_¹è°æ1-2.bmp", "t2_¹è°æ1-3.bmp", "t2_¹è°æ1-4.bmp"

"t2_¹è°æ2-1.bmp", "t2_¹è°æ2-2.bmp", "t2_¹è°æ2-3.bmp", "t2_¹è°æ2-4.bmp"

"t2_¹è°æ3-1.bmp", "t2_¹è°æ3-2.bmp", "t2_¹è°æ3-3.bmp", "t2_¹è°æ3-4.bmp"

"t2_¹è°æ4-1.bmp", "t2_¹è°æ4-2.bmp", "t2_¹è°æ4-3.bmp", "t2_¹è°æ4-4.bmp"

( ''Second Login Background'' ) - [''Alternating''] is made up of these slices;

"t3_¹è°æ1-1.bmp", "t3_¹è°æ1-2.bmp", "t3_¹è°æ1-3.bmp", "t3_¹è°æ1-4.bmp"

"t3_¹è°æ2-1.bmp", "t3_¹è°æ2-2.bmp", "t3_¹è°æ2-3.bmp", "t3_¹è°æ2-4.bmp"

"t3_¹è°æ3-1.bmp", "t3_¹è°æ3-2.bmp", "t3_¹è°æ3-3.bmp", "t3_¹è°æ3-4.bmp"

"t3_¹è°æ4-1.bmp", "t3_¹è°æ4-2.bmp", "t3_¹è°æ4-3.bmp", "t3_¹è°æ4-4.bmp"

Just because newer clients use two login backgrounds does not mean to utilize only a single login background you have to use an older client. With newer clients through "Diffing" your "Client.exe" you may choose to only use either the first or second login backgrounds. Keep in mind however, even if you choose to use a newer client and Diff it so you only have one login background you will still have to utilize the split / sliced image method to create a view-able & working login background.

'''Ragnarok Login Background Splitting Tools''':
''(Always be cautious when downloading)''

Now that we know about the formats lets pick a method of creation for new clients. There are many tools developed by various members of the Ragnarok emulation community to take care of correctly converting the splicing and splitting of a single Jpeg image you would like to use as your Login Background. Using one of these tools is the fastest most efficient method of creating a working login background for (2010-01-26 RagexeRE) and Newer Clients.

[http://rathena.org/board/index.php?app=core&module=attach&section=attach&attach_id=1882 Ragnarok Online Login Screen Generator (ROLSG)] --- ( Credit: Wiskovisky )

"[http://rathena.sourceforge.net/tools/login_background/ rAthena / Tools / Login_Background]" ---------------------- ( Credit: rAthena )

[https://raijero.svn.sourceforge.net/svnroot/raijero/dev/Brian/convert.php Convert.php] ----------------------------------------------------------- ( Credit: BrianL )

[http://rathena.org/board/files/file/2561-ragnarok-background-splitter/ RagBgSplitter_0.2] -------------------------------------------------- ( Credit: mkbu95 )

Most of these programs will split a 1024x768 Jpeg Image into 12 slices &

convert plus save them into Bitmap Image Slices in a specified directory.

'''After Splitting Tool Conversion'''

After using one of the above splitting tools to create our newly converted Jpeg to Bitmap images we then locate the directory in which the images were converted and stored or saved and we proceed to move these newly created slices from said directory in which they were saved into by the image slicing tool and (Depending on if you Diffed your Client to only allow one background or not) you then place all 12 or 24 of the spliced images into
the folder .../data/texture/À¯ÀúÀÎÅÍÆäÀÌ½º/

'''Alternatively'''

Alternatively one could split a 1024x768 Jpeg image into 12 equal slices / segments using any number of programs and save them each individually in the Bitmap format then properly place and name the 12 manually sliced Bitmap images. For each of the Alternating Login Backgrounds if you choose to use both. Instead of using one of the Ragnarok Login Background Splitting Tools. Then save to the same directory listed in the above formatted steps.

'''2012+ Clients Change Introduction'''
Please note that in 2012+ Clients there seems to be a new format gravity has introduced to their Login Background. This change is from Dual Alternating Login Background Clients toa once again fixed single Login Background however there are other changes, most notably the image format. To create this single Login Background it should be comprised of the following files;

"t_¹è°æ1-1.bmp", "t_¹è°æ1-2.bmp", "t_¹è°æ1-3.bmp", "t_¹è°æ1-4.bmp"

"t_¹è°æ2-1.bmp", "t_¹è°æ2-2.bmp", "t_¹è°æ2-3.bmp", "t_¹è°æ2-4.bmp"

"t_¹è°æ3-1.bmp", "t_¹è°æ3-2.bmp", "t_¹è°æ3-3.bmp", "t_¹è°æ3-4.bmp"

"t_¹è°æ4-1.bmp", "t_¹è°æ4-2.bmp", "t_¹è°æ4-3.bmp", "t_¹è°æ4-4.bmp"

"t_¹è°æ1-1.tga", "t_¹è°æ1-2.tga", "t_¹è°æ1-3.tga", "t_¹è°æ1-4.tga"

"t_¹è°æ2-1.tga", "t_¹è°æ2-2.tga", "t_¹è°æ2-3.tga", "t_¹è°æ2-4.tga"

"t_¹è°æ3-1.tga", "t_¹è°æ3-2.tga", "t_¹è°æ3-3.tga", "t_¹è°æ3-4.tga"

"t_¹è°æ4-1.tga", "t_¹è°æ4-2.tga", "t_¹è°æ4-3.tga", "t_¹è°æ4-4.tga"

So far it is unknown if there are any tools to convert an image into this format automatically (hint hint), however you may manually create your own image. This is still sliced into 12 quadrants both in Bitmap and Targa format. If you do not wish to use this format, all you need to do is simply remove the existing images from the GRF / data folder directory. The newer GRF's have yet to get rid of the previous images for the Alternating Dual Login Backgrounds so if you decide that is the format you would rather use you should be able to use the previous format of Alternating Dual Login Backgrounds or Diff your Client to use the first or second login background.