You can veto it. All vetoing means is that the proposal now can’t be enacted (a proposal can only be enacted if it “has not been vetoed or self-killed”).

I was kind of expecting ais to repeal this one.

because current blog templates don’t support a proposal being “vetoed with the symbol ”.

Oh, you know we could do it if we tried, Kevan.  : P

There is no current process by which I might veto it, thus this CfJ.

I’d say that “players are permitted to do X” means that we can just declare that we’re doing it. Or not even declare it; the proposal magically becomes vetoed as soon as anyone decides that they want to.

And unadminning an old, magically-vetoed proposal isn’t too helpful, here - it’d freeze the queue for 24 hours, as we can’t enact it (it’s vetoed) or fail it (it had loads of FOR votes). And if ais523 vetoed it for us, the last clause of the CfJ wouldn’t trigger, and Rule 2.1 would still be there, putting you right back where you started…

What’s wrong with that rule? Is it not the defining point of this dynasty??? Never repeal rule 2.1!

Nothing wrong with the rule, I was just looking for a way to use it. Although I do suppose the queue thing might be an issue.

Fyi delta, you can’t vote on a Call for Judgment.

Oops, sorry! 

... ? I’ll figure out this later…

Can someone please explain the whole “veto bait” issue for those of us who weren’t around during the last dynasty?

Is there some reason why we can’t just pass a proposal to “repeal rule 2.1”?

Regardless, it seems that Kevan is right that this would jam up the queue so

this is what happens when I try to not veto anything for a dynasty… let this be a lesson to the lot of you… :D

“Veto bait” was just the fallout of one five-minute conversation on IRC. Devenger mentioned being proud of his record of not having to veto anything, so a bunch of people immediately rushed over to make proposals he would “have” to veto.

CoV   , clicked the wrong button.

CoV , but let’s do something that allows me to veto “Veto Bait” in a truly satisfying way.