Civ4 Beyond the Sword Patch v3.17 is out

Thanks, Im going to try that now since its been like 3 hours and nothing...

update... I went to the downloads section and got it, took about 15 minutes....much better.
Thanks to all for this great site!!
 
Hmm.. What does "New Colonies have their parent civ's tech brokering restrictions" mean?
Does it mean that my colonies won't trade off techs which I didn't give to AIs?
 
Glad they came out with another patch, its always good to fix bugs, but there are to many things they changed for "gameplay" reasons.

What does this mean?
Siege weapons cannot attack amphibiously

Does that mean that if I give my catapults Anphibious Attack it won't do anything?
 
Does that mean that if I give my catapults Anphibious Attack it won't do anything?
Isn't that now impossible if you can't promote them up the combat line?
 
Is there something wrong with the auto-update feature? Why don't you just use that? I just used it for the first time yesterday, and although it took 30-40 mins it worked without a hitch. It downloads as an ordinary executable file.

In game updater was slower than any of the 3 1st sites put up. 40 minutes for a 1/2 meg out of 177MB IS not acceptable even when I had dial-up!

CFC.net proved to be the most reliable but not the fastest. Took 45 minutes for CFC and it didn't time out like Atomicgamer. :P

JosEPh
 
Isn't that now impossible if you can't promote them up the combat line?

Well I can make my own Catapult Anphibious Attack promotion that I give to catapult units when they are in certain kinds of ships. But now Firaxis has decided that I can't do that. Would have taken them less then half an hour to add a new tag to the unitinfos bCanAttackAnphibious.

EDIT: Or heck, even easier, a new GlobalDefine option, CAN_SIEGE_UNITS_ATTACK_ANPHIBIOUS.
 
If you see XML tags in the above screens, e.g. TXT_KEY_GAME_OPTION_LEAD_ANY_CIV, and are using BUG Mod, make sure you update to the latest release of BUG -- 2.30 -- or update from SVN.

BUG used to include a replacement "XML/Text/CIV4GameText_BTS.xml" file, but it was removed recently. The latest 3.17 patch moved some text keys from one XML file to the above XML file, and thus you may see text problems with older versions of BUG.

Again, this doesn't affect gameplay, but it doesn't look nice.
 
So...very long thread with some disappointment. I don't really have time to try to parse through it all, so short question: is it better to patch, or stick with the Bhuric patch?
 
is it better to patch, or stick with the Bhuric patch?

I would stick with Bhruic's patch for a while yet. Hopefully in a week or so most of the major hiccups will have been identified and have workarounds and/or Bhruic/Solver/ A.N.Other fixes. At that point you can better assess what to do.
 
The only issue, atm - if you aren't using a 19+CIV map/DLL (they need to be recompiled for version 3.17) is that Tanks don't benefit from Barrage promotions, aside from a couple display hiccups: for civs you haven't met.
If that issue is a sticking point - then wait, I believe Solver will be releasing a quickfix shortly, if Firaxis doesn't.
 
Correct me if I'm wrong but the barrage issue comes up in the Final Frontier game as well, and particulary badly. Since so many units have no native collateral damage yet there are collateral damage promotions, the promotions don't work. At least they haven't been working for me. :(
 
So...very long thread with some disappointment. I don't really have time to try to parse through it all, so short question: is it better to patch, or stick with the Bhuric patch?

Stick with Bhuric patch for now until things like BUG mod become compatible, because this patch may have broken a lot of things.

Personally, I'll wait until -at least- Amra's mod is 3.17 compatible.
 
BUG ( in the 2.30 version ) is fully compatible with 3.17.... EmperoFool already said that.
Earlier versions will give the text problem I posted in the Bugs forum.
 
@ PieceOfMind, no yer correct, it affects any unit that doesn't have native Collateral damage. The true fix will likely need to be a recompiled DLL, a temporary fix would be to give the respective units +1 collateral damage - I forget the fieldLabel, its discussed in the Barrage thread.
@ AlmightyDF, BUG mod is fine.

Honestly, though I 'magine a number of haters will disagree/contradict me ;-)
One bug plus a few display hiccups, for the scope of this patch, is pretty impressive.
 
I'm a little against the XML quickfix of the barrage problem ,because you'll have to do it to all units that can get Barrage and that don't have native collateral ( Tanks, Panzer, Modern Armour, battleships,...... ). The DLL solution is much more cleaner IMHO

About the patch: it looks to be a far better job than 3.13 so far... in spite of some more recent Bh stuff would fit there well ( like the changes in the "beutification of capitals" algorythim .... )
 
Back
Top Bottom