Friday, April 21, 2023

Proposal: A1 Loophole Repair [Appendix]

Reached quorum 7 votes to 2. Enacted by Kevan.

Adminned at 23 Apr 2023 10:26:49 UTC

To the bullet point in “Number and Variables” that begins “If a game variable has a default value but no defined starting value”, add:-

For the purposes of this bullet point, the names of Engineers are not considered to be legal values for game variables, nor for list items within game variables.

Per SingularByte’s suggestion on Yellow Pages. If we create a variable that refers to a player but neglect to specify a starting value, perhaps it should become an undefined orphan variable for us to fix, rather than defaulting to a particular player alphabetically.

posted by Kevan at 21 Apr 2023 10:50:00 UTC Comments (10)

Comments

Brendan: he/himIdle

21-04-2023 14:37:30 UTC

for

Josh: Imperator he/they

21-04-2023 14:48:53 UTC

for

Taiga: he/himIdle

21-04-2023 14:53:56 UTC

for

Habanero: Idle

21-04-2023 15:03:10 UTC

for

JonathanDark: he/him

21-04-2023 15:34:49 UTC

for

jjm3x3: he/himIdle

21-04-2023 22:58:48 UTC

for

redtara: they/themIdle

22-04-2023 00:16:20 UTC

against Grafting another exception onto the rules instead of writing better rules.

Taiga: he/himIdle

22-04-2023 00:33:33 UTC

I guess Engineer names weren’t meant to be treated as plain strings. Rather than creating exceptions, I am perceiving this rule as a step towards a more type-safe BN.

I anything, what kinda (but still not really) irritates me is that “Numbers and Variables” aimed to make the behaviour of actions contingent on non-Orphan Variables well-defined, but this just declares the aforementioned action illegal.

Lulu: she/herIdle

22-04-2023 05:05:46 UTC

against per Redtara

Josh: Imperator he/they

23-04-2023 05:49:22 UTC

for Strictly better than the status quo