Sunday, March 27, 2022

Proposal: Object Oriented Materials

Times out 3-0 and is enacted -SingularByte

Adminned at 29 Mar 2022 11:09:17 UTC

In the rule “Probulator Operation”, replace the text “a forecast value output (which is generally the next output that the Function should return if used (though may not be, as the actual output is determined by the method))” with “a default forecast value output”

In the rule “Probulator Operation”, immediately following the text “a list of Functions (which must consist only of names of Functions as detailed in subrules to this rule, and which must include at least one such Function)” add “, a forecast value output for each of those functions (which is generally the next output that the Function should return if used (though may not be, as the actual output is determined by the method))”

Set all newly created forecast value outputs to the forecast value output that their functions were holding immediately before enactment.

It seems kinda weird that we’re tracking gamestate in the rules rather than on the gamestate page.

Comments

TyGuy6:

27-03-2022 05:35:14 UTC

Sensible change.

MadisonSilver:

27-03-2022 05:56:06 UTC

If I’m not misreading the current rules/your proposal, I think that this slightly changes the behavior of the Functions.  Specifically, under the ruleset as written there’s one Forecast Output for each Function (which is shared between Materials), but this proposal changes it so that each Material has its own separate Forecast Output(s).  That isn’t necessarily a problem (and I’m probably going to vote FOR either way), but if this supposed to retain the same behavior then you might want to change it.

SingularByte: he/him

27-03-2022 06:39:49 UTC

That bit is intentional, yeah.

Thunder: he/him

29-03-2022 03:22:44 UTC

for

Josh: Observer he/they

29-03-2022 08:20:29 UTC

for