Describe the effect on the Empire clock.

Warn against manual disable/enable and point to the schedule file.

diff --git a/info/disable.t b/info/disable.t
index 169374aa7f700e476820fdc4218fb18e4e45bf1d..924a0405930b6574e184538eb26e92d858e35beb 100644 (file)
--- a/info/disable.t
+++ b/info/disable.t
@@ -4,4 +4,15 @@
 .SY "disable"
 No updates will fire if you disable them.  "UPDATES ARE DISABLED" will
 show up in the output of the "update" command.
-.SA "update, enable, Deity"
+.s1
+Disabling updates this way does not stop the Empire clock.  Stuff
+using the clock, like BTU growth, continues normally.  Should a
+scheduled update be actually missed, however, the Empire clock
+automatically recalibrates, to maintain the fixed number of ETUs
+between updates.  This effectively stops the clock.
+.s1
+You should not use this command as a tool for implementing your update
+schedule!  Enabling and disabling updates by hand is far too error
+prone, and your players can't trust the update command to find out
+when the next update really is.  Use the update schedule file instead.
+.SA "update, enable, Time, Deity"