ais523 via agora-business [2025-06-23 01:38]:
> CoE on the most recent Absurdor's Report: I don't think the boulder's
> Slope should be 2 – it's been reported as 2 for many weeks, but rule
> 2683 implies that it should change every week. Some of this has self-
> ratified by now, but some of it hasn't.
Welp, you're right. When I read it after it passed, I understood it
to mean that the Slope should be set to however many times the Boulder
was pushed the previous week, unless that amount was smaller than the
current Slope (then everything is reset, obviously).
{
At the beginning of each week, if the boulder was pushed in the
previous week at least as many times as the Boulder's Slope, then
the Boulder's Slope is increased by 1; otherwise, the Boulder's
Height is set to 0, and the Boulder's Slope is set to 1.
}
Rereading, it's obvious that that's not the case. In fact, I don't know
how I understood anything else.
However, this does mean that the Boulder's height is limited (because
the number of players can't keep increasing over time). Maybe that's
a problem.
Anyway, it just occurs to me that I don't understand how ratification
and claims of error interact. If I publish a revision, will it change
the values for switchs as of publication of revision or as of publication
of original report? Or even later, when the revision self-ratifies?
I could create a CFJ to satisfy the requirements of Rule 2201, but that
will delay fixes. Therefore, as there aren't any hard requirements on
the responses for CoEs, I'll DENY the claim of error, but will update
the boulder logic in code before I release my next report later today.
If this is not satisfactory, I ask for further Claims of Error to be
accompanied with responses to my previous doubts.
--
juan
Absurdor
