Idea 2:
Have the founding of the UN trigger fixed borders for all civs. The notion of culture causing a shift in borders doesn't seem too prevalent in the modern age if I'm not mistaken. I think at some point in the game the borders would become fixed everywhere and the founding of the UN seems like a good time...
@TheDisco & @dudeSDCA
Would you believe that the problems with Fixed Borders is half the reason I made them mandatory? I proposed sweeping changes to Fixed Borders, oh, probably 1 year ago now, but they universally rejected, and the current version has been kept since. I am not a fan of some parts of it, so I figure the controversy and complaints will help me fix the issues. Diabolical, I know.
1.) Excellent point. I am not against the 1 tile around the city limit, but I definitely agree that the first come first serve policy for already fixed tiles should be applied. I will change that.
I'm going to disagree with 2 & 3. I disagree that with the idea that more modern civilizations will have fixed borders, and this is reflected in the civic policies. The more modern the civilization, the more influence outside culture has on land, not less. One does not have to look hard to see that Israel is having a culture issue, the area being Palestine, and not receptive, or look at Pakistan and India, the split was over culture differences. Cultural issues are the main cause for the US Civil War as well (South accepted slavery, North did not, etc...). Culture plays more of a role today, than it has even before in the last 8000 years of civilized society. Just remember the timescale of Civ. Events that seemingly take lifetimes for us are 5 turns in game.
@TheDisco & @dudeSDCA
1.) Excellent point. I am not against the 1 tile around the city limit, but I definitely agree that the first come first serve policy for already fixed tiles should be applied. I will change that.
So no fixed borders in a modern non-Authoritarian society? Not sure I think that is realistic. Wouldn't that imply for instance the USA border might take a few tiles from Canada or Mexico over the last 50 years (or vice versa).
Idea number 1 sounds good but the problem arises when you capture a city & it will get surrounded by the enemy. Maybe captured cities always get tiles around them but the rest would follow the rule mentioned in idea 1.
Just curious, what time is this supposed to be played on now? I'm playing at a speed two slower then normal, and even then I'm hitting techs way earlier then I should. It seems to happen at every speed I try :/
There is no link between the date shown and the "tech date". It is just to hard to do for even one game speed let alone multiple game speeds.
Since we no longer have Animal units, you should remove Barracks bonus for Animal units. If for no other reason than to clean up the Civilopedia .
I've been complaining about this for a very long time. I spent a few games roughly working the game speed to fit with the techs. It's quite a mess, but I've essentially got techs appearing in the right decades at best. If you're interested, I could show you the alterations. Unless the game speed info has been changed for 1.76, as I did these changes for 1.75
I posted this on the bugs thread but it's probably a question for this thread? Since the CIVIC_VASSALAGE and CIVIC_PARLIAMENT have been deleted, what would make sense to change the civpack leaders that have listed those civics as the leaders "favorite civic." I have 7 civpack leaders from the core civpack that generate errors because of this, and I was thinking maybe I will manual change:
Favorite CIVIC_VASSALAGE to CIVIC_HEREDITARY_RULE
Favorite CIVIC_PARLIAMENT to CIVIC_DEMOCRACY
-----------------------------
Ok, based on some googling and wikipedia "research" I for the most part updated the favorite civs as above for those leaders that needed updating. I made an exception for IndiraGandhi though and changed hers to CIVIC_PUBLIC_WORKS instead of CIVIC_DEMOCRACY.
Not that these things really matter much, but just in case others were trying to get other Leaders to work without errors in 1.76 I figured I'd post what looked like the most logical changes, at least to me...