Posted February 24, 2013
SirPrimalform: I think it's just 'too broad' a wording on Robbeasy's part. I'm pretty sure he just meant the type of situation we're talking about, i.e. being caught lying and then getting out of it by blaming it on a non-existent mod mistake.
Zchinque: I know, which is why I decided not to leave a slightly more sarcastic reply. But trying to regulate it will only yield the opposite problem. If certain communications with the mod is not allowed to lie about, any such communications becomes de facto modconfirmed. Once a game has started, the mod should meddle as little as possible, imo.
In my opinion, it would be best not to make any legislation about it in one way or another, but treat any unverifiable claims about communications with the mod with suspicion - as you would any other unverifiable claims. If the only thing keeping a player from being lynched is that the he claims the mod must have made some sort of mistake, it's probably best to just lynch them.
Further, I think you will have a hard time wording any such rule to the point where it limits the kind of lying some would find objectable, without infringing on the tools needed for the game to function.
And finally, this has only come up in one game so far, correct? I wouldn't think it worth to make specific rules targeting behaviour that has popped up in a single game, out of 14. Unless said behaviour could easily and reliably ruin/break the game as a whole, of course (see the rule about cryptoclaiming as an example).
My suggestion would be to treat it as a learning experience. Think "you got us this time, but next time we won't be as gullible", if you will.
I agree the mod should meddle as little as possible, this is why I think it's really dirty to involve the mod like that if they haven't actually made a mistake. I would say although this doesn't break the game (unless the mod is forced to comment), it does unfairly affect the game.
Oh yeah and nmillar and I got our very own rule after one instance. <.<