Hey everyone,
I've started a repository at https://github.com/scshunt/agoranomic to
keep track of my reporting, and I encourage others to use their own
repositories for the same. Currently I haven't added score because
it's basically easier to do that by hand.
One of the problems that automated reporting scripts for nomics
frequently run into is one of maintainability, what with all the
dizzying pace of rule changes (DIZZYING, I TELL YOU). That's why I'm
doing this with various entities having data stored as flat files, in
the matter of typical web protocol transmissions: a header consisting
of Key: Value pairs, and an optional body section after a newline. The
idea is to make it so that when I get to automating it, the automatic
scripts will simply ignore headers they don't know, making them
backwards-compatible on old game state. The intent is to store
important but non-game-state data as fields with X- prepended, as is
common with web headers.
In order that this can be used for the ruleset, I would like comments
on the following proto-rule:
{{{
Notwithstanding the requirement that multiple Rule Changes cannot
occur simultaneously, the Rulekeepor CAN, in publishing the Ruleset,
generally format and make purely editorial changes to the rules as e
sees fit, and in particular, e CAN:
1) Change margins and spacing;
b) Fix inconsistencies in enumerated lists, such as doubled or
skipped numbers;
3) Change the numbering or bulleting style of a list;
4) Update cross-references;
5) Correct obvious spelling and grammar errors, where there is a
single obviously correct form; and
6) Establish a capitalization convention.
Such a change never affects the interpretation of a Rule. If the
Rulekeepor publishes a Ruleset containing a change which could
reasonably be interpreted differently from the previous form of the
rule or rules involved, then the change is INEFFECTIVE and the
Rulekeepor commits the Crime of Executive Meddling.
}}}
-scshunt
