BlogNomic: The First Dynasty of Desertfrog

i’d vote for 48, but not 72

Perhaps if we had a shortcut where we could also run a Cycle early if everyone (except Darknight, I guess) had a Hot Machine.

@lemon Let’s split the dif on 60. (Half-days means that the threshold will cycle around timezones.)

@Kevan I’ve added something in; does that work?

It doesn’t kick in immediately as 21% of our workforce (Darknight, Chiiika, Pokes) don’t seem to be taking actions. But I think it will feel a bit harsh when it does start to activate - anyone who takes more than 12 hours to submit orders risks missing each of their turns.

Okay - added an absolute time check.

Greenstick, I like the flexibility, though it might make the “wait for X to pass so you can do it one cycle ahead of everyone else” game even more intense.

the day + 12 hours is good because it helps ensure that the end of cycle doesn’t always fall at the same time.

but I would rather see rules that make missing a cycle less punishing than ones that slow the game down by making people have to wait two days to do anything.

@Clucky I’d rather not force people into a faster pace that they’re able to commit to. It’s a game we play asynchronously for fun, if a timer is too fast for some players to keep up, I’d rather slow down the timer than keep some players out.

Yeah, I am honestly proposing this directly because it’s a matter of changing the pace or idle out for me.

I don’t think this is too fast for me, but I do think it’s worth listening to people when they say it’s too fast for them – it’s important not to force people to overcommit to nomic-playing.

I will note that one potential issue with a 60-hour timer is that it makes it possible to miss a proposal entirely, having it be proposed and time out while you’re offline. Presumably, the best fix here is to slow down the queue in addition to the dynastic gameplay.

Would be good to maximise both players and pace. Have proposed a simpler take on the 85% thing.