I think a four-hour lockout after succeeding at a Heist Action would accomplish your goal with less frustration. I like this.

Good idea, changed.

I also added a bypass of the lockout if the previous Heist Action succeeded and was Swift. If a Participant executed a Swift Heist Action, they are likely prepared to follow it up with another Heist Action right away.

For what it’s worth, my initial plan to avoid this issue was for players to just rapid-fire post dice roller comments within the space of a few seconds and update the ruleset afterwards, but that requires enough detail in the comments to know the details of the action that’s being taken, and people understandably haven’t been doing that to avoid giving away their plans if it fails (and it also requires being simultaneously online).

I am not convinced that a 4-hour delay is a perfect solution to the problem, though. Suppose you want to take three actions without being interrupted; depending on how the teams are distributed, it’s quite plausible that you could find an 8-hour timespan when the other team is asleep and just do the three actions “without interruption”. I used to do this sort of thing with daily actions quite frequently, and ended up posting a rant about how obnoxious it was. (That said, I do admire the fact that you’re looking for solutions.)

Would enabling the Virtual Actions building block be enough to fix things? That’s a pre-existing block for handling “a Mastermind queues up Participant’s actions” that already has most of the corner cases worked out (and it’d work interestingly differently from normal this dynasty due to the scope for a Mastermind to intentionally delay, in cahoots with the Participant who submitted it).

Hm, maybe that would work. The issue for me is that I really like the simplicity of the DICE48 mechanism, but if the Participant’s Actions are queued up, what do we use as the basis for comparing those actions to X? Or does X become whenever the Mastermind executes those queued-up actions? I think you’re suggesting the latter since you mentioned “intentionally delay”.

Let me give it a try and write up a competing Proposal (competing with myself!), and then let it get settled via votes.

The Virtual Actions block states that the time of the action is the time that a Mastermind performs it, so that would presumably compare the DICE48 to the time at which it’s actually performed.

Agreed. I have an alternate Proposal up now. I don’t mind using both of my slots for this, since I don’t currently have any other ideas to put forward. I kinda like having both ideas up nearly at the same time, and let the votes determine the best one.

This massively favours teams with fewer changes to make when they already have a gigantic edge in the first place.

Withdrawn in favor of SingularByte’s idea.