I know this idea has no chance of being implemented in cIV (my fav abbreviation of the new release), but for nostaglia's sake I'll bring it up.
In Civ2 and CtP1 (not sure about CtP2 since I didn't buy that game) the game came with a seperate poster showing a graphical flow chart of the science tech tree.
The Civ2 poster had units, governments etc. in addition to the science tech tree. This was hung above my computer in my home office so I could reference it during the game. The CtP1 poster had the tech tree on one side and lot of information about terrain, units, wonders, etc on the flip side. Very nice! ![Smile](https://apolyton.net/core/images/smilies/smile.gif)
I would love to see this in cIV, but I would assume there no chance of this ever being done again. This nicety and highly utilitarian component cannot be provided due to recent versions being released before completion. It seems the development teams wish to make changes months after product release. If that is the plan or expectation, then how could they deliver a nice foldout tech tree poster when changes will invalidate part of the poster? I am opposed to this business practice - it allows for sloppy programming as bugs, features, changes can be "fixed in the next patch" and made well after delivery of the product.
In Civ2 and CtP1 (not sure about CtP2 since I didn't buy that game) the game came with a seperate poster showing a graphical flow chart of the science tech tree.
![thumbs-up](https://apolyton.net/core/images/smilies/thumbs-up.gif)
![Smile](https://apolyton.net/core/images/smilies/smile.gif)
I would love to see this in cIV, but I would assume there no chance of this ever being done again. This nicety and highly utilitarian component cannot be provided due to recent versions being released before completion. It seems the development teams wish to make changes months after product release. If that is the plan or expectation, then how could they deliver a nice foldout tech tree poster when changes will invalidate part of the poster? I am opposed to this business practice - it allows for sloppy programming as bugs, features, changes can be "fixed in the next patch" and made well after delivery of the product.
Comment