In the rule “Reviews”, add a subrule named “Requests” with the following text:
A Request is a blog post in the Story Post category in which the author summarizes any changes they made to their current Draft and requests new Reviews. If a Drafter hasn’t done so within the past 24 hours, they may post a Request.
Making it a little easier for Drafters to notify each other that sufficient changes were made to be worthy of new Reviews for a Plan.
It’s true that anyone could just make a regular blog post asking for Reviews, but this canonizes it with a Story Post category. Is that important? Not really, but I like it for thematic reasons that Story Posts indicate a dynastic action taking place. We’re role-playing Drafters, so in those roles, officially asking for Reviews makes sense in my mind.
To be fair, it always seems a bit weird to me when I make an unofficial blog post – we seem to have a culture of not doing that very often (except for things like the post-dynastic discussion threads). And I think I make a lot more of them on average than most players do.
(I think it’s even Rules-possible to make an unofficial Story Post – as long as it doesn’t match the format of any rules-defined Story Post, it’s legal to post and still counts as a Story Post, but isn’t official.)
BlogNomic is powered by pMachine ExpressionEngine.
ais523: Supervisor
I’m still not sure what to think about proposals like this one that give people Rules-based permission to do something they could do anyway, but set a time limit on it.
(That doesn’t necessarily mean that I’m opposed – I can see how it’s useful to have the Ruleset set expectations or to prompt people to do things that they might not otherwise think of.)