Likely next steps

• Bugfixing for standard use cases.

What I Expect in a Finished Product

1. Graphics

   • A visual indication of how big a city is, with higher-population cities having more buildings spread across a larger area.
   • Coastlines
   • Borders that respond more sensibly to standing water.
   • Mountains with ridges and rough surfaces.
   • Rivers that flow properly.
   • River estuaries into standing water that handle a river's flow gracefully.
   • A better distribution of trees in forests and jungles.
   • Features for farms.
   • Features for oases.
   • Proper riverbank textures.

2. Cities

   • The ability to hover over values in the UI (like yield, happiness, etc) and get a breakdown of how they were calculated.
   • Less obtrusive city summary panels.

3. Resources

   • Models for various specialty resources.
   • Icons for various specialty resources.
   • Modified appearance when a resource is being extracted by an improvement.

4. Improvements

   • Models for improvements that look like what they are.
   • Icons for various improvement types.

5. Diplomacy *

6. Units

   • Appropriate models for the various units.
   • Icons for each unit type.
   • Walking, attacking, working, and dying animations.
   • Walking attacking, working, and dying audio.
   • Numeric indicators for the number of turns it'll take for a unit to move to a particular cell.
   • The ability to spend gold to upgrade units into their more modern equivalents.

7. Civilizations

   • A full implementation of the barbarian AI.

8. Technologies *

9. Wonders

   • All wonders up to the Medieval era.

10. Social policies

    • The Liberty policy tree.
    • The Honor policy tree.

11. General

    • An Options menu with useful options.
    • More obvious and formal exchange of turns.
    • Victory conditions.
    • Icons for various yield types.
    • Background music.
    • Sounds for interacting with the UI.
    • Turn-changing sounds.
    • Version tolerance for saved games and maps, so that old versions of saved games don't throw exceptions and are not immediately invalidated when small changes are made.

12. Performance

    • A startup time for a Standard map at max player count of no more than 45 seconds.
    • A startup time for a Large map at max player count of no more than 45 seconds.
    • A startup time for a Huge map at max player count of no more than 45 seconds.

13. Documentation

    • Documentation for map generation's goals and high-level design.
    • Documentation explaining the goals and architecture of triangulation.
    • Unit tests covering map rendering.
    • A thorough analysis of the sorts of documentation and unit testing the codebase still needs.