This is also posted at the FreeAC forums, but I'd love as much feedback as possible so I've posted here too. Do you think you would like a game using such a model? Play it? But first, read on
This is a game model which AFAIK has not been used before, it's a RTS TBS hybrid which could possibly be played as both (kind of like RoN, but aimed more at TBS)
Time is divided into fundamental quantizations, but instead of the Planck time we will use fractions of "years" which for this purpose I'll refer to as "months" or "microturns".
In brief, every turn is comprised of a set number of microturns, for example one year might be 10 microturns, or 16, or some other number, but it is likely to be one of 10, 12 or 16 because these numbers have nice properties (in particular the many factors of 12 - 2,3,4,5,6 and 16 - 2,4,8 make them attractive). The shortest possible turn will be 1 microturn, and gameplay will proceed at a snails pace! (but possibly okay for WW2 style scenarios)
Every month basically everything may do one thing, for example an army might move a small distance, or engage in one round of combat vs nearby enemy armies.
Production will be done in terms of months, it might take 3 months to build a cruiser, if a turn is 10 months then 3 full cruisers will be built, and there will be one 1/3 complete cruiser. Additionally if an enemy army attacks the city on turn 7, it will find 2 complete cruisers in the port.
Research will be similar, a research project might require 9 months to complete and so with 10 month turns the project will be complete, and the next project will be just started.
Some events may happen every N months, perhaps farms generate food every 4 months (example only)
(Queued) Orders will work the same regardless of how many micro turns they cover, orders will be given like "Move to there" and the army will take as many microturns as required. This means it will be quite impossible to do things like moving armies with arrow keys (this lacking wont seem at all odd for players of RTS games, the last game to allow units movement by keys was Dune2 AFAIK - which also happened to be the first RTS game)
Every micro turn will be resolved completely before the next microturn is resolved, this means no mathematical approximations are made (in the cruiser example, there will be 10 separate deductions of resources towards the construction costs, rather than the game calculating 3 complete cruisers requiring 3xcruiser cost resources...)
What are the advantages of such a system?
Individual actions are kept very simple. Individual combat is single-round only basically in bombard style.
Unit movement is smooth and realistic, armies wont "jump" from tile to tile, making it possible to do things like realistic interception (ie patrolling unit scans for threats, and moves to intercept, rather than having to resort to things like intercept probability and zone of control.)
Because things are resolved realistically, less need for highly detailed, complex models.
In some cases may allow for economic models that would be too complex expressed as mathematical formula.
Fundamentally realistic rather than fundamentally abstract.
Puts mechanisms in place for the player/scenario maker to control game pace, from highly tactical to empire building.
Offers the *intriguing possibility of a game that can be played equally as RTS and TBS, in RTS mode orders are transmitted as they are generated by the player, in TBS mode orders are collected for the current turn and sent in one go.
More familiar to RTS gamers.
What are the disadvantages?
Possibly more CPU intensive as calculations must be carried out more often.
Not familiar to TBS gamers of the Civ line (who are used to action-reward play style)
Smooth movement complicates route finding.
Engine Requirements: The primary one is that armies have full freedom of movement, like in many RTS games and some TBS games. The order queuing system must be powerful and flexible.
This is a game model which AFAIK has not been used before, it's a RTS TBS hybrid which could possibly be played as both (kind of like RoN, but aimed more at TBS)
Time is divided into fundamental quantizations, but instead of the Planck time we will use fractions of "years" which for this purpose I'll refer to as "months" or "microturns".
In brief, every turn is comprised of a set number of microturns, for example one year might be 10 microturns, or 16, or some other number, but it is likely to be one of 10, 12 or 16 because these numbers have nice properties (in particular the many factors of 12 - 2,3,4,5,6 and 16 - 2,4,8 make them attractive). The shortest possible turn will be 1 microturn, and gameplay will proceed at a snails pace! (but possibly okay for WW2 style scenarios)
Every month basically everything may do one thing, for example an army might move a small distance, or engage in one round of combat vs nearby enemy armies.
Production will be done in terms of months, it might take 3 months to build a cruiser, if a turn is 10 months then 3 full cruisers will be built, and there will be one 1/3 complete cruiser. Additionally if an enemy army attacks the city on turn 7, it will find 2 complete cruisers in the port.
Research will be similar, a research project might require 9 months to complete and so with 10 month turns the project will be complete, and the next project will be just started.
Some events may happen every N months, perhaps farms generate food every 4 months (example only)
(Queued) Orders will work the same regardless of how many micro turns they cover, orders will be given like "Move to there" and the army will take as many microturns as required. This means it will be quite impossible to do things like moving armies with arrow keys (this lacking wont seem at all odd for players of RTS games, the last game to allow units movement by keys was Dune2 AFAIK - which also happened to be the first RTS game)
Every micro turn will be resolved completely before the next microturn is resolved, this means no mathematical approximations are made (in the cruiser example, there will be 10 separate deductions of resources towards the construction costs, rather than the game calculating 3 complete cruisers requiring 3xcruiser cost resources...)
What are the advantages of such a system?
Individual actions are kept very simple. Individual combat is single-round only basically in bombard style.
Unit movement is smooth and realistic, armies wont "jump" from tile to tile, making it possible to do things like realistic interception (ie patrolling unit scans for threats, and moves to intercept, rather than having to resort to things like intercept probability and zone of control.)
Because things are resolved realistically, less need for highly detailed, complex models.
In some cases may allow for economic models that would be too complex expressed as mathematical formula.
Fundamentally realistic rather than fundamentally abstract.
Puts mechanisms in place for the player/scenario maker to control game pace, from highly tactical to empire building.
Offers the *intriguing possibility of a game that can be played equally as RTS and TBS, in RTS mode orders are transmitted as they are generated by the player, in TBS mode orders are collected for the current turn and sent in one go.
More familiar to RTS gamers.
What are the disadvantages?
Possibly more CPU intensive as calculations must be carried out more often.
Not familiar to TBS gamers of the Civ line (who are used to action-reward play style)
Smooth movement complicates route finding.
Engine Requirements: The primary one is that armies have full freedom of movement, like in many RTS games and some TBS games. The order queuing system must be powerful and flexible.
Comment