Monday, April 10, 2023

Proposal: High Risk High Reward

Fewer than a quorum not voting AGAINST. Failed 2 votes to 6 by Kevan.

Adminned at 12 Apr 2023 13:52:52 UTC

Update the Rule Threat to be called “Monumental Moments”. Then replace every instance of Threat with “Monumental Moments”. Replace every instance of Disaster with Moment.

Update first bullet of the communal action to read as follows:

* Carry out the Effect of the Moment corresponding to the non-blank, left most item in the Monumental Moments and remove that Moment from the Monumental Moments. Repeat this step until the Monumental Moments is blank.

Add a bullet point to the end of the list consisting of:

* Create a Story Post describing the results of the Monumental Moments action

Add the following rows to the table:

| Kaiju Attack || Set the building’s stability to 0 and increase the accidents of the last engineer who performed the build action by 1 || OH NO It’s a large lizard or big moth or monkey or something |
| Stroke of Ingenuity || Randomly select 5 blocks which are _ and change their contents to Rebar || Wow we should have thought of that sooner |
| Performance Bonus || Increase the Safety Checks of the last engineer who performed the build action by 10 || Hey good on ya! You benefit from a recency bias in the workplace |

Reworking Threat a bit to give folks a reason to trigger it, in addition i am attempting to address what looked like an infinite loop in how Threat would have been processed.


JonathanDark: Publisher he/him

10-04-2023 16:46:04 UTC

Do you think that removing the left-most Moment from the list is sufficient to shift the remaining Moments left, or should there be an explicit direction to shift them left? One could argue that removing a Moment leaves a blank in its place and the others remain where they are in the list.

jjm3x3: he/him

10-04-2023 18:10:59 UTC

I don’t totally know. Part of my thought process to post this as is was around the fact that based on the definition of a moment/threat and that there is no such thing as a “blank” moment because it’s not named and doesn’t have an effect etc… But perhaps I can think of a rewording that will make that even clearer.

jjm3x3: he/him

10-04-2023 18:14:56 UTC

Added a “non-blank” qualifier.

Brendan: he/him

10-04-2023 22:20:57 UTC

against I think this is constructed fine but the flavor of it is not for me.

Lulu: she/her

11-04-2023 00:30:28 UTC

against as much as i want kaiju attacks

Kevan: he/him

11-04-2023 07:56:36 UTC



11-04-2023 15:44:33 UTC

for I like this.

JonathanDark: Publisher he/him

12-04-2023 02:07:16 UTC


Taiga: he/him

12-04-2023 13:35:00 UTC


Raven1207: he/they

12-04-2023 13:50:25 UTC