Note: seems maybe simpler to remove the only-this-way clause from Grading?

Note: Probably, now that you mention it. I think I have a habit of over complicating things. I think I was thinking that new scoring methods could be introduced too easily if that was the case.

Note: The thing is, the only-this-way clause isn’t the only problem. Grading says a rule only lets a player score if that rule has a 3 letter code (none of them do), that that code can’t be used more than once, which would make Map scoring a one time thing, and that when a Scribe scores they gain a Project based on said 3 letter code. (and that Projects are only rewarded this way) Finally, I just noticed this final clause at the end of the rule. “This Rule takes precedence over other dynastic rules for the purpose of determining when or whether a Scribe Scores.” This method might actually be the simplest fix that doesn’t involve removing the rule Grading entirely.

Note: Ah right [MAP] does have a code. Most of my points still stand though.

Note: with your fix, I could guess over and over again. ANY rule that states otherwise? Including this one?

Note: The method of scoring itself specifies that the Rule used couldn’t have been guessed at before.

So, that’s not really a loophole.

But I’m with Brendan.

Self kill. Going to have to put a lot more thought into this.

You leagaly could have edited it, all Note: comments.

I’m aware.

Oh.

I don’t think this is necessary.  Grading explicitly lets other (qualified) rules cause Scoring.  The clause you’re worried about bars (e.g.) Scoring by CfJ or Proposal.