We need to decide now on how players take their turns. After some discussion we have three options, these are; (more detailed descriptions are included at the end)
1. Traditional; i.e. Civ style
2. Simultaneous; i.e. SMAC multiplayer
3. Plan first, then simultaneous move.
If you have already voted elsewhere on this you should vote again here.
Note this is for BOTH the single and multiplayer game.
At this point we are not considering any other options.
Voting ends at July 24th at 00:00 GMT.
1. Traditional
--------------
This is how Civ single player works. Players take their turns sequentially, whilst a player is taking a turn other players cannot move their units.
Advantages
----------
- We're all familiar with it. Gives players plenty of time to plan & strategise.
Disadvantages
-------------
- Too slow for multiplay.
- Old fashioned.
2. Simultaneous
------------
I believe this is how SMAC multiplayer works. There are still turns but all players can move at the same time.
Advantages
----------
- Suitable for multiplayer.
- More up to date approach which is more likely to appeal to a wider audience.
- Enforcing turns ensures that it doesn't turn into a RTS.
Disadvantages
-------------
- Combat model would have to change (from tradition Civ) as attacking a unit that has not yet move gives the attack an unfair advantage.
3. Plan first, then move.
-------------------------
Turns are first planned, then executed - all units move simultaneously, and all players plan the turn simultaneously.
Advantages
----------
- Some real-time elements, while remaining turn-based
- Fair combat; the quicker and more militaristic players don't get any unfair
Disadvantages
-------------
- Never been done before. Will take a lot longer to develop
- Lacks immediacy. Players want to see an immediate response to their actions
- Extra work needed to solve the possible conflicts in unit orders
- We need a possibility to pause the turn if something unexpected from some player's point of view happens, for example, if his units are attacked or his territory is entered.
[This message has been edited by dan ward (edited July 08, 2000).]
1. Traditional; i.e. Civ style
2. Simultaneous; i.e. SMAC multiplayer
3. Plan first, then simultaneous move.
If you have already voted elsewhere on this you should vote again here.
Note this is for BOTH the single and multiplayer game.
At this point we are not considering any other options.
Voting ends at July 24th at 00:00 GMT.
1. Traditional
--------------
This is how Civ single player works. Players take their turns sequentially, whilst a player is taking a turn other players cannot move their units.
Advantages
----------
- We're all familiar with it. Gives players plenty of time to plan & strategise.
Disadvantages
-------------
- Too slow for multiplay.
- Old fashioned.
2. Simultaneous
------------
I believe this is how SMAC multiplayer works. There are still turns but all players can move at the same time.
Advantages
----------
- Suitable for multiplayer.
- More up to date approach which is more likely to appeal to a wider audience.
- Enforcing turns ensures that it doesn't turn into a RTS.
Disadvantages
-------------
- Combat model would have to change (from tradition Civ) as attacking a unit that has not yet move gives the attack an unfair advantage.
3. Plan first, then move.
-------------------------
Turns are first planned, then executed - all units move simultaneously, and all players plan the turn simultaneously.
Advantages
----------
- Some real-time elements, while remaining turn-based
- Fair combat; the quicker and more militaristic players don't get any unfair
Disadvantages
-------------
- Never been done before. Will take a lot longer to develop
- Lacks immediacy. Players want to see an immediate response to their actions
- Extra work needed to solve the possible conflicts in unit orders
- We need a possibility to pause the turn if something unexpected from some player's point of view happens, for example, if his units are attacked or his territory is entered.
[This message has been edited by dan ward (edited July 08, 2000).]
True I can program somewhat better now at a lower level, and will have actual college credit for it, but...

Comment