When we screwed with this a few games back it caused a lot of hassle, because everyone has to do it, I knew beet had prior experience doing it and no problem doing it, it required no major group effort and was explicitly relevant to the question at hand. It was also specifically phrased as a request, had he refused I would not have raised this issue later as evidence against, mostly it I did it to lift a potential burden on beet to claim first, which I think would be unfair in this circumstance, this eliminated that.



Basically, I'd rather we didn't give people a strong motive to turn this game into a code making and breaking back and forth, particularly since that tilts game advantage to the mathematically skilled and potentially makes people devote large amounts of time to doing that. Ultimately, it would be a game-killer as the new day 1 would be 'Everyone produce your code within 48 hours or you will be lynched', not pro-game, tactically sound but not pro-game. This was case specific.



Yep. I view coding as acceptable strictly for this kind of one on one time-critical aspect. It hasn't been banned in the rules yet because we haven't really discussed it as a group to determine what should or shouldn't be banned, but we'll obviously at a minimum have to ban day 1 mass code-claims.