Richard:
I understand. You chose a more 'abstract' approach, in keeping with your preference of playing the game at the 'province' level. You prefer a similar abstract 'combat' system.
I respect your choice, altho I do disagree with it. I feel those should be options -- but the guts of the system should strive to model real-world objects in both cases.
And technically speaking, an 'ethnic group' as a 'component' of a civ does not 'inherit' anything from that civ. That would be 'subclassing' or 'extending' that civ object. I would not agree that an 'ethnic group' extends a 'civ'.
* * *
Boer:
That does indeed point out a major difference in approaches.
I am indeed of the opinion that a 'technology' is a 'knowledge' that allows an 'ethnic group' to take given inputs (resources and tools/infrastructure) to produce given outputs (buildings, food, etc).
The 'Technology' component that belongs to a 'civ' I would call 'infrastructure' -- in your example, the actual Nuclear Power Plant, Universities, etc. Because the people certainly would retain the knowledge on how to build a Nuclear Power Plant, along with all the realted infrastructure they built the first time, but the actual structures they could not take along.
And personally, I'd put the 'infrastructure' structures in the mapsquares they physically exist in -- because an enemy can destroy/capture that infrastructure.
* * *
Mark:
I respect the amount of time you put into that code. Please don't misunderstand me. You worked hard, and should be commended.
Altho I've seen this exact same pattern before. I know what caused that pattern then. And I believe I see the same dynamic playing here.
I understand. You chose a more 'abstract' approach, in keeping with your preference of playing the game at the 'province' level. You prefer a similar abstract 'combat' system.
I respect your choice, altho I do disagree with it. I feel those should be options -- but the guts of the system should strive to model real-world objects in both cases.
And technically speaking, an 'ethnic group' as a 'component' of a civ does not 'inherit' anything from that civ. That would be 'subclassing' or 'extending' that civ object. I would not agree that an 'ethnic group' extends a 'civ'.
* * *
Boer:
That does indeed point out a major difference in approaches.
I am indeed of the opinion that a 'technology' is a 'knowledge' that allows an 'ethnic group' to take given inputs (resources and tools/infrastructure) to produce given outputs (buildings, food, etc).
The 'Technology' component that belongs to a 'civ' I would call 'infrastructure' -- in your example, the actual Nuclear Power Plant, Universities, etc. Because the people certainly would retain the knowledge on how to build a Nuclear Power Plant, along with all the realted infrastructure they built the first time, but the actual structures they could not take along.
And personally, I'd put the 'infrastructure' structures in the mapsquares they physically exist in -- because an enemy can destroy/capture that infrastructure.
* * *
Mark:
I respect the amount of time you put into that code. Please don't misunderstand me. You worked hard, and should be commended.
Altho I've seen this exact same pattern before. I know what caused that pattern then. And I believe I see the same dynamic playing here.
Comment