Add cycle and maximum cycles to RUN_PROGRESS

docs/corewar/match_settings.md

@@ -1 +1,24 @@
-# Match Settings
+# Match Settings
+
+The following settings can be specified for a given match allowing for a great variety in the types of Corewar matches that can be run.
+
+## Core Size
+
+The number of instructions which can be stored within the [Core](core).  This number is also the maximum number which can be represented within the simulation.  See [Addresses](core#addresses) for details.
+
+## Maximum Cycles
+
+The number of Cycles to execute before the Round ends in a draw.
+
+## Maximum Processes
+
+The maximum number of [Processes](processes) that each Warrior can have at one time.  Attempting to generate further processes using the [spl](../redcode/opcodes#spl_split) will have no effect - effectively acting as a [nop](../redcode/opcodes#nop_no_operation).
+
+## Maximum Warrior Length
+
+The maximum number of instructions which each Warrior can be composed of.  Writing a warrior longer than this limit will result in a [Parser](../redcode/parser) error.
+
+## Minimum Separation|The [Loader](loader) will not place Warriors closer than this number of addresses at the start of a Round|
+|Standard|Which redcode [standard](../redcode/#standards) should be used when parsing warriors|
+|Read limit|Instructions beyond this distance from the currently executing instruction cannot be read| 
+|Write limit|Instructions beyond this distance from the currenlty executing instruction cannot be written to|

docs/developer/index.md

@@ -76,7 +76,9 @@ Used to monitor progress towards the end of the round
 
 ```
 { 
-  runProgress: number // Indicates current cycle as a percentage of maximum cycles
+  runProgress: number   // Indicates current cycle as a percentage of maximum cycles
+  cycle: number         // The current cycle
+  maximumCycles: number // The maximum number of cycles, after which the round will end in a draw
 }
 ```