Wednesday, July 14, 2021

Proposal: A New Beginning

Self-killed. Josh

Adminned at 15 Jul 2021 08:23:17 UTC

In the rule Run Initialisation, to the paragraph that reads “Richardo’s starting location is a publicly tracked Room. Whenever a Room is Pacified, if Richardo found an Ingress while applying the effects of that Room’s featrures, Richardo’s starting location becomes that Room. Whenever Richardo’s starting location would not be a Lit Room, Richardo von Nestor or any Vampire Lord can change Richardo’s starting location to a random Lit Room”, add:

When a Room becomes Richardo’s starting location for the first time, remove any effects in that Room and any Lit room orthogonally adjacent to it. If any Vampire Lord has a sepulchre in any of those rooms than that Vampire Lord may once change the location of their sepulchre to another legal location before Richardo’s next Enter the Crypt action; if they have not done so by the next time the Organ is Playing then while the Organ is Playing any Vampire Lord or Richardo von Nestor may set them to having no sepulchre.

Remove all effect in the Grand Sluice and any Lit Room orthogonally adjacent to the Grand Sluice. If the Vampire Lords named ais523 and/or Kevan named a Lit Ordinary Room that is not already another Vampire Lord’s Sepulchre in their EVC to this proposal then set their respective Sepulchre to that room; otherwise, set their Sepulchres to blank.

Comments

Clucky: he/him

14-07-2021 15:21:23 UTC

My biggest problem with this proposal is that people need to plan their moves based around when the starting location is

Clucky: he/him

14-07-2021 15:40:02 UTC

it also just seems less fun, and weakens placing an ingress a whole lot

Bucky:

14-07-2021 16:47:07 UTC

I would be somewhat disappointed to have my one contribution to the map outright erased like this.

ais523:

14-07-2021 17:13:40 UTC

against (, (”) (”)

I think part of the gameplay is dealing with Ingresses moving to interesting places. Obviously, I’m somewhat in danger as a result of the move, but this is the sort of thing I have to live with (and this may well have been an intentional move to attack my Sepulchre, as there were no other easy ways to get there).

Josh: Observer he/they

14-07-2021 17:17:53 UTC

Grand Sluice was chosen randomly, although I’m sure that Brendan and Clucky made a note of all the interesting possibilities when they made a self-destructing ingress in Forgotten Corridor, but it’s hard to call this really targeted.

If it’s bad news for anyone, though, it’s Bucky; at the moment Richardo cheesegraters himself over Grand Sluice two or three times per run, with slender odds of escape…

Clucky: he/him

14-07-2021 17:20:37 UTC

sure but there are two rooms around it people can add to help deal with that problem. and even more around the underwater cavern that can help him completely escape.

I think the rules are robust enough we can at least give them a chance to fix this problem

against

ais523:

14-07-2021 17:44:43 UTC

Put it this way: I foresaw placing “Richardo moves to a random location” effects as one of the best ways available to attack Sepulchres. lemonfanta spent much of her Puissance on Secret Passage Maps recently (and they did indeed have the desired effect of attacking Sepulchres). The “random ingress” is just another way to do that.

Kevan: he/him

14-07-2021 17:48:29 UTC

I’ll have missed any Slack chat, if this came out of something there: what is this proposal meant to be addressing?

Josh: Observer he/they

14-07-2021 18:21:15 UTC

Nothing more than the a grand sluice being a somewhat unfriendly place for Richardo to pop out

Bucky:

14-07-2021 20:30:40 UTC

Note that Richardo doesn’t suffer the effects of the starting room unless he moves out and back in.

ais523:

14-07-2021 20:33:35 UTC

I just noticed a typo in this proposal that means that it doesn’t actually amend the rules; there’s a typo in the text you’re matching to determine which part of the rules get changed, so it can’t find any text to append to and doesn’t work.

Josh: Observer he/they

14-07-2021 20:35:13 UTC

That typo is actually present in the ruletext (I copy-pasted it) but given that I can correct typos in both the ruleset and this proposal freely, I shall do so. Thanks!

Josh: Observer he/they

14-07-2021 20:36:24 UTC

Having said that, Creature Feature is going to make this unmatchable, so against s/k.

Raven1207: he/they

14-07-2021 21:45:41 UTC

against