|
conmcb25
|
 |
Angmar
Aug 2002
time: 23:35
|
|
Another rules clarification.
Vote for one, 48 hours. (Does anyone know how much con is beginning to hate these rules???  )
What exclusions should there be, if any, to the restrictions on use of the Automation commands (including stack movement)?
1. No exclusions. Only worker tasks (roading, mining, irrigating, etc.) and stack/individual unit movement that concludes in the current turn can be automated.
2. Local exclusions only. Automation of worker tasks (roading, mining, irrigating, etc.) is permitted. Stack & individual unit movement that concludes within currently (when order is given, not when units arrive) defined national borders can be automated.
3. Line of Sight exclusions. Automation of worker tasks (roading, mining, irrigating, etc.) is permitted. Stack & individual unit movement that concludes within territory currently (when order is given, not when units arrive) visible (ie. not in the fog of war) is permitted.
4. Local exclusions with oversight. Automation of worker tasks (roading, mining, irrigating, etc.) is permitted. Stack & individual unit movement that concludes within currently (when order is given, not when units arrive) defined national borders can be automated. Automated moves are subject to administrator oversight. Contested moves that result in an unfair advantage (ie. reinforcing a poorly defended city or location, etc.) will remain a violation of this rule.
5. Line of Sight exclusions with oversight. Automation of worker tasks (roading, mining, irrigating, etc.) is permitted. Stack & individual unit movement that concludes within territory currently (when order is given, not when units arrive) visible (ie. not in the fog of war) is permitted. Automated moves are subject to administrator oversight. Contested moves that result in an unfair advantage (ie. reinforcing a poorly defended city or location, etc.) will remain a violation of this rule.
|
28-04-2004 08:21
|