Proposal: Core rules gamestate challenge patch
Antiquorumed, 8-1 -Darth
Adminned at 10 Dec 2009 16:12:48 UTC
In rule 1.7 “Gamestate Tracking”, add
All updates to the GNDT are logged - if a Adventurer feels that an alteration made less than one week ago goes against the Rules (as they were at the time of the alteration), he may simply undo the effects of that alteration. If such an undoing is disputed, a Call for Judgment shall be raised.
If the factual accuracy of a record of the gamestate in the GNDT, or the rules listing on the wiki page http://blognomic.com/wiki/index.php?title=Ruleset, is not challenged by a GNDT comment, blog post, comment, or edit or edit summary on the wiki page in question for a week, then that record of the gamestate is considered to have been correct at the time it was made; if it was originally incorrect, the gamestate is changed to what it would be if that record had been correct. Additionally, if a proposal, CFJ or DoV made after this sentence was added to the rules is not marked as invalid at any time during the week after it was posted to the blog, then it is considered to have always been valid, and if it was originally invalid, the gamestate is changed to what it would be if that proposal, CFJ or DoV had been valid.
as a new paragraph immediately before the last paragraph, then delete
All updates to the GNDT are logged - if a Adventurer feels that an alteration goes against the Rules (as they were at the time of the alteration), he may simply undo the effects of that alteration. If such an undoing is disputed, a Call for Judgment shall be raised.
from that rule.
In other words: if there’s a mistake in the gamestate or rules and we don’t notice it for a week, that mistake becomes law. The GNDT and wiki page are probably watched closely enough to prevent people scamming this by editing incorrect changes into the gamestate record and hoping nobody notices; likewise, this only checks validity of future CFJs, proposals and DoVs, so that invalid official posts far in the past don’t suddenly become valid because nobody remembered to mark them valid.
I’ve been meaning to do this for a while, but the mild controversy about how the last dynasty ended shows that this is needed; in this case, the DoV was valid although people weren’t sure about it, but imagine if it had happened the other way round (the DoV was invalid but nobody noticed); we’d end up with a different Emperor from who we thought we had! Recovering from that sort of thing makes up about 90% of the gameplay at B Nomic; we really don’t want BlogNomic to end up like that too.
Josh: Imperator he/they
Eh. Don’t we usually common-sense these problems away? Not very nomic-y, perhaps, but I think you’re too trusting of people not to break rules letter-by-letter while hoping that no-one notices. (An admin could, for example, change a key word while enacting another proposal - the manual checking and following up will increase the burden of play dramatically, and that’s the best case, we-find-them-and-they-fail scenario.)