New policy for retreats and builds

[Jeff Kaufman]

Because there are often only a really small number of retreats, people
rarely revise these orders, and I don't like needing to delay the
game, I'm adding a rule 12:

For retreats and builds, if all orders are in before the
deadline, the GM may resolve early. Any revised orders
submitted after the point at which the GM starts resolving will
be ignored.

If you have issues with this new rule, please talk to me. It should
help me keep us on schedule.

Also, spring 2378 moves are tonight and I still lack orders from two
powers.

Jeff

[Todd Nelling]

In general, I don't like this approach. I prefer the "marked 'FINAL'" approach. That allows people to submit prelims without being concerned that they'll be treated as final.

[Jeff Kaufman]

Todd Nelling wrote:
>
> In general, I don't like this approach. I prefer the "marked 'FINAL'"
> approach. That allows people to submit prelims without being concerned that
> they'll be treated as final.
>

Hmm. How about orders can be marked "final" or "not final"? If all
the orders are in and "final" then I may start resolutions early. The
default for move orders would be "not final" and the default for build
and retreat orders would be "final". How's that?

Jeff

[Todd Nelling]

That works.

[Tom Emmons]

works for me too

[Chris Segal]

As somehow who has in fact sent e-mails marked version 2 if not
version 3, this sounds workable.

[Jeff Kaufman]

Chris Segal wrote:
>
> As somehow who has in fact sent e-mails marked version 2 if not
> version 3, this sounds workable.
>

Revised rule 12:

Orders may be marked 'final' or 'nonfinal'. For unmarked orders,
move orders will be assumed to be nonfinal while retreat and build
orders will be assumed to be final. If all orders are in and
final before the deadline, the GM may resolve early.

Jeff