This should be #1 on the Essential List.

Asynchronous multiplayer - players submit orders to a server which adjudicates on a schedule, with the AI taking turns for players who do not submit orders - would be a great boon for multiplayer Civilization.

Few players actually have the time to play a game via direct-connect, it's hard to match up schedules with your opponents, and it feels rushed. PBEM allows the time to micromanage where desired, yet suffers severely from lag time between turns. Asynchronous multiplayer would solve both of these problems.

Finding server space to host games is trivial these days. One person could easily host several hundred games with little impact on their network connection provided the design was optimized to reduce the size of the files transmitted.

first can you define what the problem is? is it a significant problem? how does your ideas fix that problem specifically? does your fix effect any other areas of the game? if it does effect another area does it upset game balance in those other areas? is there a simpler way to fix the problem? does your idea hurt gameplay? why out of all of the ideas does your fix belong on this list?

So, for one example, PBEM turns should be handled via a system that automatically zips and sends the file to the next player (the next time you are on-line). This alone would make life much nicer.

On top of that, I understand that a game can be coded in such a way that it is LAN/on-line friendly.

And then there is the fact that we'll need a good place to meet to play on-line games. Hopefully Firaxis has given some time to dedicated server space for such a use, including rated play, ladder play, etc. Though the MS Zone has lots of problems, it's certainly better than nothing. I hear BattleNet is great, too.

Multiplayer support for Civ2 was greatly welcomed by fans. Civ3 should reflect the even greater importance multiplayer support could play in its success. Along those lines:

• Allow for simultaneous turns. Not only will this speed up MP games, but it lends tremendous strategic possibilities and surprises.
  
• PBEM turns should be automatically zipped and sent to the next player. There should also be a way to handle running several PBEM games at once without confusing which turn is being played in which game.
  
• Hotseat and LAN support.
  
• A host site similar to The Zone or BattleNet should be in place and well-tested before the game releases. And like the Zone, rated and ladder play should be offered along with "friendly" and theme rooms.
  
• Finally, the game should be written from the start in such a way that game information can be efficiently sent between computers.
  

Final Consensus Draft

by Adm.Naismith (aka mcostant) and ChrisShaffer

EC3 New Idea #15: Simultaneous Turns of Play

The Problem

• The current turn-based model uses an unrealistic sequence, where a player can move units, attack a defender, and repeat. The defender can't properly react (reinforce, counterattack, etc.). All war declarations have a "Pearl Harbor" feeling, with significant advantages for attackers.
  
• Multiplayer is too difficult.
  

Abstract

• All players (human and AI) receive a turn report, which can be reviewed and replayed as desired.
  
• All players create a set of potential orders for units, cities, and diplomacy.
  
• All players submit orders.
  
• All orders are adjudicated (on schedule or when all players have submitted orders). Conflicting orders are decided using a rule-based priority system.
  
• Game generates turn reports.
  
• Repeat.
  

Advantages

• More realistic combat model. Forces players to consider both offence and defence. Eliminates the problem of "rolling attacks" where the defender has little or no opportunity to react. First strike nuclear attacks more difficult.
  
• Practical multiplayer options. In direct-connect mode, simultaneous orders creation saves considerable time. Eliminates the lag problems inherent in PBEM, as games could be hosted on web or email servers with set turn schedules. Players could receive turn reports, create orders, and submit them to the server for the next adjudication. The AI could create orders for players who do not meet the deadline. Eliminates most opportunities for cheating in multiplayer.
  
• Increased realism and excitement. In the real world, everyone acts at the same time, they don't wait until their turn. More tension in the rush to achieve objectives such as wonder building.
  

Needed to implement this proposal

• Development of a priority mechanism to settle conflicting orders, such as movement, resource allocation by competing cities, etc.
  
• Turn reports combining animation and text that allow detailed review of events. "Replay" of any portion of the turn report as desired by players.
  
• Options for reactive movement and combat. Multiple defensive and offensive postures for units. Method of determining whether a unit is attacking, defending, or both. For example, a unit could be ordered to "attack and hold," "charge," "attack and advance," "counterattack if attacked," and so forth.
  

Conclusion

• Simultaneous turns of play is more like a strategic level of command, where you make decisions and orders about the general plan, and then things happen according to your overall plan before you (the main commander) can change your mind.