Why is the game changing when there has not been a patch for years?

The things have always been like this on Settler, Barbs never entered your territory even back in VANILLA.

Thanks.
If you are certain of this as others also seem to be, then that is good enough for me.

And in VANILLA City-States only gave you 1 quest, and that 1 quest was always only active, so that's why the only real way to ally them was to give them a of bunch gold.

I mentioned this earlier, I am questioning more the content of the one quest. I can't recall having problems becoming allied to City States in the past, as far as I can recall the most common early quest used to be to take out an offending barb camp, now the most common quest is to wipe out another CS. I have also tried several games with raging barbs on quick speed but even that has no effect.

As for Workers not working the tiles in G&K? I really don't know what is the cause of it? :dunno:

As far as I know there has never been a problem with workers on G&K.
 
I can't verify from game inception, but can state that the time stamp for CivVHandicapInfo (vanilla version) is September 19, 2011; so that hasn't changed since then for Vanilla players.

But I can also confirm that some of the patches releases after G&K and BNW came out had impact to Vanilla.
For instance, in that same directory for vanilla I can see the timestamp of CivVGameOptions & CivVPlayerOptions both are July 7, 2013. I'm thinking a new multiplayer option was added for everyone then (and not just BNW players).

Thanks joncnunn, for your detective work!

So what you are saying is that VANILLA was finalised in Sept 2011, but patches and Hotfixes for G&K and BNW are sometimes having an effect on the earlier version/versions?
 
Thanks joncnunn, for your detective work!

So what you are saying is that VANILLA was finalised in Sept 2011, but patches and Hotfixes for G&K and BNW are sometimes having an effect on the earlier version/versions?

Not even that much; I'm just saying that the handicap info xml file was finalized in Sept 2011 for Vanilla. * Some files are even older.

* If Firaxis wanted to, they could still change it with a future patch, but it's doubtful with BNW's handicap file being different ["AI default handicap" was only added to BNW; prior to that the AI used Chieftain.]
 
As far as I know there has never been a problem with workers on G&K.

Uh actually sorry mate... I misread your previous post. If you meant that Workers stop working when Barbs are nearby, that has always been the case since VANILLA and on every difficulty. It is simply there to remind you that the Worker might be stolen by Barbs (even on Settler when something like that will never happen as long as they are in your territory). If you want to make the game stop reminding you that every turn just kill the Barb or put some Military Unit over the Worker.
 
Uh actually sorry mate... I misread your previous post. If you meant that Workers stop working when Barbs are nearby, that has always been the case since VANILLA and on every difficulty. It is simply there to remind you that the Worker might be stolen by Barbs (even on Settler when something like that will never happen as long as they are in your territory). If you want to make the game stop reminding you that every turn just kill the Barb or put some Military Unit over the Worker.

This is a confirmed bug on vanilla only, and this only came about in Oct 2012 which is a year later than the last patch for Vanilla from what joncnunn is saying!! So if this is the case, then it is quite reasonable for me to start this thread as an enquiry about other changes that might be happening.
 
This is a confirmed bug on vanilla only, and this only came about in Oct 2012 which is a year later than the last patch for Vanilla from what joncnunn is saying!! So if this is the case, then it is quite reasonable for me to start this thread as an enquiry about other changes that might be happening.

Over a year from the last patch that impacted the vanilla handicap xml file.

I already noted two different vanilla files which were impacted last fall.

That particular bug refereed wasn't in the XML but in the main core of the game; and that file is still changed every single patch.
(It was even impacted when Conquest of the New World Deluxe came out and the only change was [for those with BNW] access to it.)
 
Back
Top Bottom