client: Unbreak standalone build

[empserver] / doc / econfig

diff --git a/doc/econfig b/doc/econfig
index fcca4048926c8a7ac2265bc78f11bc1bec657327..794d814e5d8428f0c9f8abc0961795f9736b163a 100644 (file)
--- a/doc/econfig
+++ b/doc/econfig
@@ -30,7 +30,7 @@ For instance,
 configures the data directory to that place, and
     port "7777"
 configures the empire port to 7777,
-  btu_build_rate 0.0004
+    btu_build_rate 0.0004
 configures the BTU build rate, and so on.
 
 The programs look for the config file in a compiled-in location, which
@@ -69,6 +69,9 @@ pconfig econfig2 > e2 && mv e2 econfig2
 
 which will fill in all the missing keys and values with their defaults.
 
+You define your update schedule in the schedule file, in the same
+directory as your econfig.  See doc/schedule for details.
+
 Additional customization is possible through key custom_tables, which
 is a list of files containing tables in xdump format (see doc/xdump
 for technical information on xdump).  To customize a table, copy the
@@ -77,9 +80,6 @@ file next to your econfig, then name the file in custom_tables.  Do
 *not* edit the default table in-place!  That bypasses important
 consistency checks.
 
-Be careful not to put `holes' into tables, e.g. by commenting out
-entries.  That doesn't work yet.
-
 A word of caution: Just because you can customize something doesn't
 mean you should!  The server makes an effort to catch mistakes that
 could crash the game.  It has no chance to catch mistakes that
@@ -114,7 +114,7 @@ econfig parser.
 3. Use the variable in your code.  This normally looks like
 
          if (opt_DUMB) {
-            pr("You're being dumb\n");
+             pr("You're being dumb\n");
          } else {
-            pr("You're being really dumb\n");
+             pr("You're being really dumb\n");
          }