ultramage fc9d14b1bd Command code cleaning (refer to topic:169759)
* separated the execution part of command code into interface part and internal part to better see which checks are done and when (fixes problem where 'nocommand' mapflag blocked server npcs)
 * moved the internal commands list (array) to the end of the file, this let me discard that long block of ACMD_FUNC() declarations
 * removed enum AtCommandType from command headers and commands array; its purpose was perhaps to identify aliased commands, but apparently it was never finished because the rest of the code doesn't use it (also doing aliases like this is not a very good idea)
 * internally, commands are now referenced to using their function name
 * removed the @/# symbols from the command lists; all lookup functions will now properly deal with strings with- and without a command symbol (commands interface still requires the symbol tho', so TODO for later)
 * removed several unneeded commands (*id2 code, dmalloc debug commands)
 * reverted atcommand config from alphabetically-sorted to how it was before (with additional fixes; see /conf changelog)
 * added missing code for #dropall / #storeall
 * added a warning when trying to set gm level of an undefined command

The structure of the commands table has changed, please adjust docs/guides to match the new format (sorry for the inconvenience).


git-svn-id: https://svn.code.sf.net/p/rathena/svn/trunk@11607 54d463be-8e91-2dee-dedb-b68131a5f0ec
2007-10-29 09:16:39 +00:00
..
2007-10-18 08:04:53 +00:00

What is the import folder for?

Most people don't know the real use of the import folder. After you do, you will wonder 
what you ever did without it.

The main thing it does, is provide a way for you to change your config settings without
having to update the files every time you update your server. You store your changes, and 
the rest are updated with eA (usually though SVN).

How does this work?

Well, you place only the settings you have changed in the import files. I'll use 
battle_athena.conf and battle_conf.txt for my example. Everytime you update you conf 
folder, using the normal method, you have to go and edit the configs again. So, you have to
redo your rates, redo your ip addresses, you have to redo it all. Well, not with the import
system.

Say you want to change your base experience rate from the default (100)to 7x (700). Well 
then you would place this in your import/battle_conf.txt:

// Rate at which exp. is given. (Note 2)
base_exp_rate: 700

You don't need the comment (duh, it's a commnet), but I usually leave them for clarity 
sake.

So, now this new setting take place over the setting in battle_athena.conf. You just keep 
this file everytime you update, and your setting will always be there. Neat, isn't it?

So, yeah, that's what the import folder is for. I hope to see a lot more people use it, to 
make my life as a managed server runer better.

Semi-guide by Ajarn