I guess the issue of recruitment and movement are linked. If movement is normal (slow), then there is more time to recruit and recruitment issues become more important. Instant battle from the outset would of course make the issue of recruitment in war time irrelevant.

Quote Originally Posted by TinCow View Post
My concern is which of the PvP movement systems we're using. Has that been decided somewhere that I've missed?
I'm suggesting what I understand to be the basic LotR system, but with the ability to switch systems if it is too slow:

(g) movement on the campaign map: normal rules apply, but if the GM thinks it best, he may propose alternative mechanics (e.g. phased movement; risk style movement; instant battle) which will be adopted if passed on an OOC vote (unweighted).

If we are going to have civil war about one third or more of the game, then I think just moving as far as the computer allows will be the easiest to implement. Players can do it directly without going via the GM. I also have a strong preference for this system on the grounds of transparency - everyone will know what they can do, how at risk they are etc. If it proves too slow and inconclusive, the GM can speed things up using the console etc.

However, there is an IGO-UGO problem with just letting players make normal moves in civil war. What determines who moves first in a given turn? Moving first may be a big advantage if it allows you to catch or evade your enemy. Conversely, moving second in some situations may be an advantage as you have seen the enemy move. Both are complicated by the issue of a deadline for making moves. How did you handle that in LotR?

One solution would be for the GM to identify which armies could potentially fight next turn (are in reach of each other) and ask players to submit orders to him rather than move directly. He could then work out some plausible implementation of simultaneous movement (WEGO) rather than rely on a rather gamey IGO-UGO. (Where armies could not meet in a turn, I would not worry too much about it.) This does somewhat negate the ease of implementation advantage I mentioned, but I gather the problem with this system was a lack of battles, so it may not crop up too much.