“if the Lifeform’s counted vote had the effect of an AGAINST vote and the resolved Proposal failed without being self-killed or vetoed”
So, even more incentive to shoot down everyone’s proposals, or to SK your own if they look like they’re going to fail? This has too many uses beyond how I assume you intended it.

Oh, and, err… This thing: 

Admin’s Hell!!!!!!!!!!!!!!!

Because it not only ruins the strategic voting (now people are encouraged to vote FOR simply to complexity++) but it also gives benifits depending on which way people vote. Meaning somenoe, even though they dislike a proposal, might vote FOR simply because the need the complexity boost. I like the idea, but find a better way to implement it.

Well, I of course am not claiming to know all the ramifications of the proposal, but here was my thought process in any case.

I did realize that the way it’s worded, that obstructionism might be a problem, which is one of the reasons that I made self-killed proposals not count.  If it looks like people are shooting down a proposal just to get the complexity, then the author can just self-kill and no one gets anything.  Thus, this gives an incentive for people to vote for a decent proposal (it will get passed, and they also get a complexity point to boot).  The other reason to make SK’s/vetoes not count is to prevent people from making a proposal just for obtaining complexity (though a group of people could conceivably do this, but this is no different than DNA and as the rules stand right now).

I also am not sure that it ruins the strategic voting.  As it currently stands, there is no reason to vote for a proposal that looks like it will pass if one votes against it, since that just gives 8 DNA points to the author.  Now, there’s a trade-off; the 8 DNA points to the author vs. 2/3 of a complexity point for you.  I think that the overall effect of the proposal will be to encourage votes and speed up the game.  If a proposal looks like it’s going to pass, people will be more likely to vote for it, and thus it’s more likely to reach quorum.  If a proposal looks bad and like it’s going to fail, then more people will vote against it, or the author will self-kill.  In both cases, there will be fewer proposals holding up the queue.

I do realize that it’s more work for the admins, but a lot of that work is done with the DNA (have to determine who’s voted; who votes for/against).  The bulk of the work is updating another field for the Lifeforms, but I think we should move to a more distributed model for doing that anyway.

But yeah, I’m open to another mechanism if you guys think it’s flawed, or any other suggestions.

If you repropose in some other incarnation, I would suggest doing away with any bonuses from failed proposals.  And the DICE.  (i.e. just make it my 1 complexity point vs. author’s 8 DNA points in the case where it passes)

I like how it makes my vote matter more on proposals that are likely to pass.  As opposed to the current system, which incentivizes everyone to let proposals squeak by with the minimum number of FOR votes.

Thanks.  I’m not too attached to the getting the point from rejection (though I don’t think it would necessarily hurt either).  The for vote part is more important.

The reason I had the dice is that I didn’t want to penalize people who couldn’t vote on every proposal.  This way, they still get something (like how they get the lower of two values for DNA).  Also, if the roll is a 1, it simplifies the bookkeeping, since everyone will just get a point.

As Hix mentioned, getting proposals to pass by higher margins wouldn’t be a bad idea (since right now reaching quorum is near impossible) and I would probably vote for something that gives incentives to vote For. Not a LOT of incentive, just enough where it’s actually worth considering whether to vote strategically or not.

What I anticipate happening is that 90%+ proposals will be trivial, and people may vote down excellent proposals while trying to strategically vote, and make the author re-propose them trivial anyway. I hope I’m wrong…