Out-of-order fails are a bad idea as proposals often build on mechanics established by other pending proposals, and enacting them out of order can cause a huge pain in the ass.

I’ll be against this as written.

This rule doesn’t say anything about Enacting proposals, only Failing them, and only it was going to fail anyway.

The idea of failing self-kills out of order is an old one that has upsides and downsides - from a gameplay perspective here, admin advantage will loom even larger, if admins can casually and repeatedly self-kill-and-repropose to iterate an idea or an elevator move, and non-admins can’t.

We could add a line that says admins can’t fail their own self-killed proposals. It doesn’t preclude collaboration but at least it sets the bar somewhat higher.

Generally I’m in favour of this proposal.

I added your suggestion, redtara. Also, there’s still the 3 proposals per day limit, and the 12-hour grace period, so I don’t think this is that OP.

@Zach True.

I think I’m still against; with this many players I just don’t want the queue to run quicker.

As per the community guidelines, the game shouldn’t run hot; a player checking in once every 48 hours shouldn’t have an overwhelming amount of stuff to catch up on, and frankly we’re pushing the line on that as it stands.

@Josh, exactly. I check in once or twice a day, and it can be an overwhelming amount even then. Can only imagine how bad it would be for people who check in less often if we sped it up.

[Zack] Fair point on the limits, but I think the general downsides of admin advantage and splitting the conversation across multiple posts (which we already saw with the two Moore’s Law proposals) are best avoided.

If “it’s going to be tough if both your slots are tied up on proposals that aren’t liable to pass” then maybe we could have additional slots that are limited to certain types of proposal. Although, really, the game being tough may be no bad thing.

Fair points all around, s/k