Proposal: Take the consequences
Procedurally Vetoed. - lilomar
Adminned at 04 Aug 2010 08:57:24 UTC
In Rule 2.2.1 replace “Whenever the High-Programmer makes a blog post, he may assign any number of Commendations and Treason Points to Citizens (with a maximum of one Commendation and one Treason Point per Citizen), in that blog post.” with:
Whenever the High-Programmer makes a blog post, he may assign any number of Commendations and Treason Points to Citizens, in that blog post.
In said Rule replace “If a Citizen’s Treason score is 6 or more, any Citizen with a higher Clearance Level may Terminate them by posting a blog post announcing such an action.” with:
If a Citizen’s Treason score is 6 or more, they or any Citizen with a higher Clearance Level may Terminate them by posting a blog post announcing such an action.
First a little fix. Why should the High Programmer be restricted to assign only one Commendation/Treason Point per Post and Citizen. There is no restriction of making such posts, so if he wants to assign 5 Treason Points, he could do this in 5 Story Posts. Besides, there were Story Posts which tried to assign 2 Treason Points, if I am right?
Second the gist of this proposal: I thought of an automatic death mechanism, but wanted to keep the Clearance idea in said Rule, so I added just the “suicide” mechanism. Generally, if I were the High Programmer, I would terminate each Citizen which at least 6 Treason Points, but of course I am not clever (just RED cleverness) enough to understand the actions done by the High Programmer.
Comments
lilomar:
Oh, I can’t terminate Citizens with 6 or more Treason, ULTRAVIOLET Citizens are above that sort of thing. Literally, it’s a VIOLET rule, I’m not a Citizen as far as it is concerned.
Keba:
Oh right… Well, the High Programmer should be able to terminate, too. Someone should fix this.
lilomar:
I am holding off to vote, as I am not sure how I feel about the suicide clause. My gut is that it is a bad idea though.
I like the first part.
Keba:
[lilomar] I rather don’t like the dependency on the “mood” of Citizens of higher Clearance Levels to terminate someone. As I stated above, I would also vote for a automatical mechanism, but that would introduce suicides, too.
Well, I know suicides could lead to scams. There has been a dynasty (before my time), where someone won because he died (and being the first in the near of the corpse, if I remember correctly).
But I don’t assume that will happen again, at least not in this dynasty. Clone Numbers are not that important, currently they mean nothing and I don’t expect them to become major part of this dynasty.
scshunt:
glopso:
Wakukee:
Kevan: he/him
An earlier proposal in the queue repeals the first sentence you’re replacing, so we’re just voting on the suicide clause here.
lilomar:
ais523:
There’s a more complicated timing issue here. Suppose (under the current rules) the High Programmer needs to give someone -18 treason points (one at a time, rather than all at once); then it’s in the recipient’s interest to self-promote after the first -6, and again after the next -6. That requires getting into a timing war with the High Programmer, which is not fun and requires staying online continuously trying to check for the timing of their actions. (I would submit a fix for this, but I can’t without it being treasonous; I’m currently trying to work out a fix to allow me to submit a fix for the issue…)
This proposal (the only half of it that works) would introduce the same issue for deaths. Thus
.
(Both issues would be fixed if death and promotion moved the Treason counter towards 0 by 6 places, rather than just resetting it to 0, incidentally; that way, the timings wouldn’t matter.)
Purplebeard:
Rodney:
Keba:
S/K
per ais523.
But there need to be a fix!
lilomar:
procedural