BlogNomic: The First Dynasty of Desertfrog

Does this actually do anything beyond forcing all players to pay for their Wagers, if the Global Effect is “roll again” and the Payout doesn’t pay anything out?

And I’d personally prefer the Segments to all have randomly generated names, for the sake of this dynasty’s aesthetic. (Is it only Annoyingness that wasn’t, right now?)

Annoyingness is the only thing not on the list.

No, but I will modify it, so that everyone doesn’t have to pay for their wagers.

I’ve also changed the name to make it random.

A much better name, but your modification means that this Segment now does even less: it’s as if the spin was never made.

(The only game effect I can see is that its Global Effect might get picked up by the Random Segment.)

Well, it’s not as if a spin was never made because it sets the clock back, as a result, at least two more spins will be allowed immediately.

Oh, got it, I mistakenly thought the clock was set relative to the time of the Spin, each time, not relative to its previous value. Hmm.

“The Wheel’s due date is set to 37 hours prior to the time that it was before this spin occurred”

I like the idea but I’m a little worried that someone could say, set it to *any* time that it was before the spin occurred. And thus set it to several days ago and generate several new spins rather than just the intended 37 hour reset. Do we need a “directly” in there to ensure no such shenanigans?

I don’t think that’s a reasonable interpretation, but I see no harm in adding it later.

This could allow (read: require) as many as three additional and immediate Spins, and that’s assuming a Spin is actually made when it becomes Past Due. And with the chance that it could chain and go pseudo-infinite, it’s a hard pass from me. 

I don’t think the directly is needed, and anyone who tried that scam would almost certainly loose the CFJ.

The infinite spin concern is valid: we need a way to break the loop.  cov. sorry.

Not sure I see how you could read “37 hours prior” as “at least 37 hours”, or anything other than “exactly 37 hours and zero minutes prior”, really.

It does become a bit weird for (per the atomic rule) having to set the clock to 37 hours before the time that you finished the atomic action, before you’ve finished it. But I guess you can retroactively correct it if needed.

, anyway. I’m impressed with the mechanics of the solution here, but I’m not especially excited by the idea in practice, particularly if we roll a couple of Doubles in a row.

> Not sure I see how you could read “37 hours prior” as “at least 37 hours”, or anything other than “exactly 37 hours and zero minutes prior”, really.

Its not that. The problem is that right now, the wheel due date is at 5th June 2020, 21:00:00 UTC

Lets say a week from now, the wheel is spun and lands on this. Someone could argue “5th June 2020, 21:00:00 UTC” is a time the wheel was at before the spin occurred. And thus set the due date to be 4th June 2020, 8:00:00 UTC”, 37 hours before that date.

But the infinite spin this is enough of a problem that even if we fixed this to “the time that it was immediately before this spin occurred” it still wouldn’t work so