On Sun, 2022-03-20 at 19:38 -0400, Jason Cobb via agora-business wrote:
> On 3/20/22 18:13, ais523 via agora-business wrote:
> > I point my finger at Jason for violating rule 2143, committing the
> > Class 2 Crime of Tardiness, via failing to perform the Rulekeepor's
> > weekly duties in the week of 7 March 2022.
> > 
> > [We haven't had the SLR published for two weeks now, so it seems like
> > time to bring out the fingers.]
> > 
> 
> Admitted, but I've generally only been publishing SLRs after assessments
> (trying for within a week after it) and nobody's suggested they have a
> problem with it until now? I'm happy to actually publish weekly if
> people want that.

It probably isn't a huge deal – it's the sort of thing you only notice
if you go to find the SLR, realise there hasn't been one recently, and
then have to wonder how out-of-date the one you find is. (It could also
be a problem for new players playing via email – idling for a week is
intended to be enough to find all the critical reports.) It's also
worth noting that the Ruleset changes most weeks as a consequence of
Mad Engineer experiments (generally in irrelevant ways, although a
"stale" ruleset did end up mattering recently because it caused me to
accidentally mis-order list items within the Device rule).

There was a big batch of proposals enacted this week, so the need for
an SLR is a little higher than usual. Additionally, having an up-to-
date ruleset (ideally the online FLR, which is my usual source) ASAP
would be very helpful for me because it affects my Mad Engineer rule
randomization roll; I currently have it automated, but if the published
Rulesets are out of date with respect to which rules exist, I have to
do it manually because if the dicebot is misinformed as to which rules
exist, it will roll a dice with the wrong number of sides and thus
cause my entire Mad Engineer weekly action to be invalid.

(As a side note, it's probably to your benefit to publish the SLR every
week regardless, as doing so would get you Officer duty pay.)

-- 
ais523

Reply via email to