I had an idea for a Gunboat game.
In this game players submit two sets of orders- one is the standard set and the GM only ever see those orders and another set of orders written in code.
The code orders (along with the standard set to the GM) would be due on a certain day and published one day before finalized moves were due. In between the code publication and final orders, players could change one unit's per every four units ( so if you have 4 units you could change 1 or if you had 8 you could change 2). Players would be allowed to change their code once in the game.
The schedule would look something like this:
Day 1 Spring Code Set and GM SET due and Code Published
Day 2 Spring Final Set Due with up to one unit per four changed - If there is a change, Change Code Published
Day 3 Spring Retreat Code Set and GM SET Retreats due and Code Published
Day 4 Spring Retreat Final Set Due (only one can be changed in retreat) If there is a change, Change Code Published
Day 5 Fall Code Set and GM SET due and Code Published
Day 6 Fall Final Set Due with up to one unit per four changed - If there is a change, Change Code Published
Day 7 Fall Code Set and GM SET Retreats due and Code Published
Day 8 Fall Retreat Final Set Due (only one can be changed in retreat) If there is a change, Change Code Published
Day 9 Winter Build Code and GM Set Due and Code Published
Day 10 Winter Code Published
The code needs to be given to the GM so the GM can spot check codes to make sure they're not just nonsense.
Thoughts on this?
In this game players submit two sets of orders- one is the standard set and the GM only ever see those orders and another set of orders written in code.
The code orders (along with the standard set to the GM) would be due on a certain day and published one day before finalized moves were due. In between the code publication and final orders, players could change one unit's per every four units ( so if you have 4 units you could change 1 or if you had 8 you could change 2). Players would be allowed to change their code once in the game.
The schedule would look something like this:
Day 1 Spring Code Set and GM SET due and Code Published
Day 2 Spring Final Set Due with up to one unit per four changed - If there is a change, Change Code Published
Day 3 Spring Retreat Code Set and GM SET Retreats due and Code Published
Day 4 Spring Retreat Final Set Due (only one can be changed in retreat) If there is a change, Change Code Published
Day 5 Fall Code Set and GM SET due and Code Published
Day 6 Fall Final Set Due with up to one unit per four changed - If there is a change, Change Code Published
Day 7 Fall Code Set and GM SET Retreats due and Code Published
Day 8 Fall Retreat Final Set Due (only one can be changed in retreat) If there is a change, Change Code Published
Day 9 Winter Build Code and GM Set Due and Code Published
Day 10 Winter Code Published
The code needs to be given to the GM so the GM can spot check codes to make sure they're not just nonsense.
Thoughts on this?