BlogNomic: The First Dynasty of Desertfrog

[ Fixing the veto loophole left open by Reductio Imperator, and rewording the Enactment rule into something more readably bullet-pointed while I’m here. ]

If Reductio Imperator failed, this proposal shall first make the exact changes that that proposal suggested.

Reword Rule 1.5 (Enactment) to:-

The oldest pending Proposal may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

• It has a number of FOR votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed.
• It has been open for voting for at least 48 hours, more than half of its votes are FOR, and it has not been vetoed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

• It has enough AGAINST votes that it could not be Enacted without one of those votes being changed.
• It has been open for voting for at least 48 hours and half or fewer of its votes are FOR.
• The Traveller who proposed it has voted AGAINST it.
• The Arbiter has voted to VETO it.

Whenever an Admin marks a proposal as enacted or failed, e must also mark eir name, and report the final tally of votes (or the fact that the proposal was self-killed or vetoed).

Also, add “If a Traveller votes against eir own proposal, that vote may not be changed.” (which I’ve removed from this rule) to the second paragraph of Rule 1.4 (Voting).