Import Files

Caution:

• These files are meant for conf/import directory
• Athena will use the contents of these files in place of corresponding contents of files in conf folder. For example, autoloot: 0 in atcommand_conf.txt will override autoloot: 10 in atcommand_athena.conf.
• Settings in battle_conf.txt will override those in /conf/battle files.

Sample Files:

• The following files contain popular settings which are identical to corresponding lines in the respective conf files. You can edit those settings to put your Athena on air quickly. However, you should not be restricted by these files. You can easily make your own import file by copying the content of a conf file with an editor, save it as an import file and edit to suit your requirements.
• The contents of the following sample files are default Athena settings. Their presence in the import folder will not affect the default files in the conf folder. However, if you choose not to use import folder, you should empty its contents or comment off the import lines in the respective conf file. As mentioned earlier, battle_conf.txt will also override files in battle folder.
• atcommand_conf.txt
• battle_conf.txt
• char_conf.txt
• charcommand_conf.txt
• inter_conf.txt
• log_conf.txt
• login_conf.txt
• map_conf.txt

Q&A

Why use import files?

The contents of grf-files.txt and lan_support.conf are almost never changed while GM_account.txt (Athena TXT) are changed only with turnover of GMs. You probably can remember those contents and will have no problem reconstructing those files.

The bulk of Athena configuration is in those conf files. When you have a stable set of configuration, it is quite certain that you want to use it with the next revision. However, changes to Athena are made revision-wise in conf files. If you were to use existing conf files, you have to go through all configuration lines and edit new ones into your set. Of course, you can use diff and patch to do that. A tidy way is to configure Athena using the import folder and use that in future revisions without missing updates from the Developers. If you want to use any new one, you can easily copy the new line into the import files.

You can duplicate an import folder and edit settings for testing purpose. You are less likely to forget about certain lines because of the relatively smaller contents.

How do I make an import file?

You can make an import file by duplicating the content of the corresponding conf file, e.g. login_athena.conf to login_conf.txt. Delete settings which you are unlikely going to use so that the resulting file will be small and easy to manage.