Saturday, March 11, 2023

Proposal: It’s a game of Tag, after all

Withdrawn and therefore failed -SingularByte

Adminned at 12 Mar 2023 17:35:00 UTC

Create a new rule called “Score”:

All Runners have a score, which is a publicly tracked non-negative integer defaulting to 0.  If a Runner has a score that is at least 1,000 and is higher than any other Runner’s Score, they have achieved victory.

In “The Stack”, append the following after “If the total Size of Disks on a Stack ever exceeds its Capacity, that Stack has Overflowed; the Runner or Gridmaster whose action caused a Stack to Overflow must repeatedly Pop that Stack until it only contains one Disk, then reduce its capacity by 1, unless reducing the capacity this way would cause the Stack to be Overflowed.”

Then, the Runner who’s Stack Overflowed has their score halved, rounding down.  The Runner who caused their stack to Overflow gains 100 score if they are a different Runner; if it was the Gridmaster, all other Runners gain 50 score instead.

 

Throwing an idea for a wincon.  Probably needs more methods of scoring though

Comments

lendunistus: he/him

11-03-2023 14:23:22 UTC

should probably define the score value as non-negative if we want to allow spending score, since we’ve had hiccups with that in the past

Lulu: she/her

11-03-2023 14:25:38 UTC

good idea, added

lendunistus: he/him

11-03-2023 14:26:42 UTC

personally would prefer something like “the runners that escape fast enough are thrown into a final stratum”, score seems boring

I should probably propose that then

lendunistus: he/him

11-03-2023 14:35:44 UTC

oh, and score also isn’t tracked so you probably want to fix that

Lulu: she/her

11-03-2023 14:46:21 UTC

fixed

Lulu: she/her

11-03-2023 14:47:41 UTC

your idea sounds cool but idk how to implement it.  that’s why i didn’t implement it.  if you do make a new wincon please don’t entirely delete Score

SingularByte: he/him

11-03-2023 15:06:37 UTC

The main downside I can see of this way of doing it is that if one person manages to overflow a handful of people repeatedly, then a third party might just need to overflow a single person to win.

I’d prefer if it gave score to the one who caused the overflow, if possible. Giving it to everyone can just be a fallback when the one who caused the overflow can’t be worked out.

Lulu: she/her

11-03-2023 15:30:01 UTC

good idea

SingularByte: he/him

11-03-2023 19:22:16 UTC

for

Raven1207: he/they

11-03-2023 21:06:00 UTC

for

Kevan: he/him

12-03-2023 12:00:44 UTC

against Cautiously against a victory condition based around actions that we haven’t successfully taken once yet. I’d rather see some working gameplay before agreeing that “cause 10 overflows” is non-trivial.

SingularByte: he/him

12-03-2023 13:46:51 UTC

An overflow honestly seems difficult enough that I don’t see much risk in it. You have to hit someone multiple times in a row with a Send without them just popping the stack immediately to remove all the junk, and then you have to repeat that feat 10 times.

Given that the only way to Send for free is via a terminal, you’re gonna be Sending either once every 2 days using power, or once every 4 days with a Terminal.

Habanero:

12-03-2023 16:36:26 UTC

for

JonathanDark: he/him

12-03-2023 16:44:24 UTC

for

SingularByte: he/him

12-03-2023 17:13:19 UTC

CoV against
I hadn’t realised that you could push disks onto other people’s stacks, which means if this is voted through, the dynasty could potentially end right here.

To cut a long story short, there’s no limit to how many times you can execute in a turn (since it only limits executions *within* the Gridmaster’s Tick atomic action). Habanero can place the overflowed disks in a convenient row, then yank them all onto someone again, overflow them, and rinse and repeat until 1000 points have been racked up in a matter of moments.

I was gonna use the scam myself via repeated Sendings, but it’s too risky if Habanero has all the pieces in place to win on the spot.

Habanero:

12-03-2023 17:16:23 UTC

Foiled again!

Lulu: she/her

12-03-2023 17:30:33 UTC

against Withdrawn

SingularByte: he/him

12-03-2023 17:34:23 UTC

Thanks, Misty