Update docs from Hercules.

2 files changed, 6 insertions, 27 deletions

diff --git a/server/other/map_cache.txt b/server/other/map_cache.txt
index 19ab92a..80a8366 100644
--- a/server/other/map_cache.txt
+++ b/server/other/map_cache.txt
@@ -3,7 +3,7 @@
 //===== By: ==================================================
 //= DracoRPG
 //===== Current Version: =====================================
-//= 20070724
+//= 20160820
 //===== Description: =========================================
 //= A complete manual for Hercules' map cache generator as 
 //= well as a reference on the map cache format used.
@@ -32,11 +32,8 @@ having slightly different maps. When building your cache, you should ensure you'
 
 The list of GRFs and/or data directory must follow the format and indication of the default file: as many "grf:" entries as
 you wish and optionally only one "data_dir:" entry with trailing backslash included. // comments are supported as usual.
-In fact, any file with one map name per line can be used as a map list, that's why the map index list is used as a default:
-we are sure it contains every map supported by the server. Anything after the map name is ignored, // comments are supported
-and if the first word on the line is "map:" then the second word is used as the map name instead: that allows using
-/conf/maps.conf as your map list, which is handy if you want to generate a minimal map cache for each of your multiple
-map-servers.
+A custom map list can be used, in order to generate a map cache file with different (or less) maps than the current Hercules
+configuration. For details on the map list format, see conf/map/maps.conf.
 The map cache file path can point to an already existing file, as the builder adds a map only if it's not already cached.
 This way, you can add custom maps to the base map cache without even needing kRO Sakray maps. If you wish to rebuild the
 entire map cache, though, you can either provide a path to a non-existing file, or force the rebuild mode.
diff --git a/server/other/md5_hashcheck.txt b/server/other/md5_hashcheck.txt
index d9064b1..0153938 100644
--- a/server/other/md5_hashcheck.txt
+++ b/server/other/md5_hashcheck.txt
@@ -3,7 +3,7 @@
 //===== By: ==================================================
 //= Hercules Dev Team
 //===== Current Version: =====================================
-//= 20140208
+//= 20160210
 //===== Description: =========================================
 //= This file outlines the login server's MD5 hash check.
 //============================================================
@@ -20,27 +20,9 @@ Please refer to your client diff tool manual for the appropriate patch
 tools or diffs it may have similar names.)
 
 The serverside settings for the hash check are located in
-conf/login.conf:
+conf/login/login.conf::login_configuration.permission.hash
 
-// Client MD5 hash check
-// If turned on, the login server will check if the client's hash matches
-// the value below, and will not connect tampered clients.
-// Note: see doc/md5_hashcheck.txt for more details.
-client_hash_check: off
-
-// Client MD5 hashes
-// The client with the specified hash can be used to log in by players with
-// a group_id equal to or greater than the given value.
-// If you specify 'disabled' as hash, players with a group_id greater than or
-// equal to the given value will be able to log in regardless of hash (and even
-// if their client does not send a hash at all.)
-// Format: group_id, hash
-// Note: see doc/md5_hashcheck.txt for more details.
-client_hash: 0, 113e195e6c051bb1cfb12a644bb084c5
-client_hash: 10, cb1ea78023d337c38e8ba5124e2338ae
-client_hash: 99, disabled
-
-To enable MD5 hash checks, set 'client_hash_check' to 'on' and add one
+To enable MD5 hash checks, set 'client_hash_check' to 'true' and add one
 'client_hash' entry for each client you want to use.
 The group_id can be any of the groups in conf/groups.conf, and it is
 useful in case if you want to allow GMs to use a different client