106b44c1e7
* the login server storage, ipban and logging systems have been abstracted and now provide a common interface; the rest has been merged into a single login server core (no more login/login_sql duplicity) * storage systems are now added via compiler options (WITH_SQL / WITH_TXT) * multiple storage engines can be compiled in at the same time, and the config option account.engine defines which one will be used. * due to MySQL autoincrement limitations, accounts with id '0' will not be supported; account IDs from this point on should start from '1'. * login_log() functions now again record IP addresses in dotted format, not as 4-byte integers (undo from r6868). * removed config options that defined column names in the login table * removed `memo` and `error message` columns from login db/savefile * moved `loginlog` table to the logs database * added sql files upgrade_svn12975.sql and upgrade_svn12975_log.sql * due to changes to the login table layout, I added an !optional! sql file (upgrade_svn12975_view.sql) that will provide a certain degree of backwards compatibility with existing software; read the instructions inside carefully! * moved third-party includes/libs to a separate directory * updated project files / makefiles Changed the way GM levels are handled * removed conf/gm_account.txt * added the gm level column to the txt savefile (after 'email' column) * gm level information is now transferred along with account data For open problems see bugreport:1889. git-svn-id: https://svn.code.sf.net/p/rathena/svn/trunk@13000 54d463be-8e91-2dee-dedb-b68131a5f0ec
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