The files in this directory can be used to benchmark mooix.

A MOOstone is a real-world measure of how many commands per second can be
processed by the moo, while one user is logged in, on an otherwise unloaded
machine. They will vary from machine to machine. It is up to you to make
sure that the machine is unloaded, and prevent anyone else from logging
into the moo while the benchmarking is in progress.

The benchmarking works by first setting up a builder avatar, and using
mooscript to feed a series of commands to it, from a .bench file. The
results are saved to a .results file with the same prefix as the .bench
file, and are then processed to generate an overall MOOstone number for
that benchmark, and optionally a set of MOOstone numbers of smaller
granularity for subsets of the benchmark.

To delimit subsets, have the avatar emote lines beginning with "starting".
Ie:

  :starting: attacks
  attack the monster
  attack it
  attack it

Subsets named "setup" and "cleanup" are not included in the results; use
them for doing stuff that is necessary for housekeeping tasks but should
not be benchmarked.

.bench files are preprocessed with cpp before being run, so you can use
#includes in them. Since the avatar starts out in the void, your .bench
file will typically start by making a room for the benchmark to run in
and moving the avatar there. There is a setup.bench that does that and you
can just #include it.

You can also use special commands to repeat a block of text
(they cannot yet be nested):

  ##repeat 100
  look
  ##endrepeat
