Solver's unofficial BtS 3.17 patch

With the exception of from transports (thus I always figured it was an unlisted ability of them or for a later tech), I had never been able to (nor had the AI) attack from sea before without amphibious assault.

And yes, that's exactly what happened.... the first time I tried the official patch, right from the get go, I had barbarian swordsmen attacking my swordsmen on my galley that was at sea. I hadn't saved it before then (I don't usually save until well after that point), and I just quit the game after my "What a load of crap!" exclamation after losing my units that should have been safe at sea (again, at least from land units).


Well, I just tried a small testbed, and I couldn't attack an enemy's units on a ship, from land.

I'll need to see you either post a game file or a test bed, to check if what you are saying is true. Until then, I'm assuming the game does not allow land-to-ship attacks, which is always the way it's been in every game I've played. (Including the 3.17 patch.)

I'm not using Solver's patch, so perhaps that is the difference. (If Solver broke something.) But you seem to be claiming that it's not a bug with Solver's unofficial patch.

I suspect you didn't properly take note of the combat. Maybe there was a fort involved or something like that.
 
No.... it was really early in the game, and I was completely isolated, so there wasn't anything else to take note of. I was moving a couple units to take a barbarian city on another island, and my galley was still one square away from where I'd want to land my units in order to attack the city (after it had moved), and then they attacked my units on board my ship.

Like I said, it was well before I ever make my first save in a game, and I just quit the game after it happened, so I don't have anything to share. That, and it's off the official patch only. I've never installed any non-official things before, and that's one reason I'm a bit reluctant to even install this, but if fixes what it seems that the official patch broke..........
 
Unfortunately, in an attempt to recreate it as best I could, all the auto saves got overwritten; and with the barbarians refusing to do anything for me to try it. :(
 
I was moving a couple units to take a barbarian city on another island, and my galley was still one square away from where I'd want to land my units in order to attack the city (after it had moved), and then they attacked my units on board my ship.

I've never seen anything like that either, in any version. Do you know that your units will disembark if you click a land tile for the boat to 'aim at', while the boat is still on the coast with no move left? Maybe that was it, your units got killed on land after disembarking unnoticed by you?

I'll take this opportunity to add my thanks Solver, much appreciated :)
 
I've never seen anything like that either, in any version. Do you know that your units will disembark if you click a land tile for the boat to 'aim at', while the boat is still on the coast with no move left? Maybe that was it, your units got killed on land after disembarking unnoticed by you?

Or, he clicked on a land square that a few turns earlier, to move the boat there. The units would automatically disembark, and if there happened to be a barbarian on that land square an attack would happen. It might look like the barbarians attacked your ship, but in reality it was you that gave the orders to do an amphibious assault on them.

Given that no one else has apparently seen the behaviour being claimed, I'm going to attribute it to "user error".
 
I've been playing for years, so I know you can have it automatically land units. But.... I never do that as the situation on such a tile changes each round. It was on the boats, as the barbarians moved over the water to attack my unit that was floating on the water (the galley wasn't being attacked, so it wasn't the top unit displayed).

I'm just saying what my experience was when I updated to the official patch, and thus am asking if this is suppose to fix it. If that's not a quintessential bug (which is what this is suppose to fix, right?), then I don't know what is! I mean, I've never encountered any of the other bugs that have ever been listed in patch updates. I wish I had a save that I could prove that this actually did happen, since obviously nobody believes me! I've never experienced any sort of problem playing the game, EVER, and then this happens within an hour of starting my first post-patch game, out of the blue.
 
I wish I had a save that I could prove that this actually did happen, since obviously nobody believes me! I've never experienced any sort of problem playing the game, EVER, and then this happens within an hour of starting my first post-patch game, out of the blue.

Well, I don't see how you can expect Solver to fix this "problem", since no one else has seen it, and you don't have a save game to show it.

If it ever happens again, exit your game and back up your autosaves.

Set AutoSaveInterval = 1 to make sure you autosave every single turn.

Until then, I'm presuming the bug doesn't exist.
 
Well, I don't see how you can expect Solver to fix this "problem", since no one else has seen it, and you don't have a save game to show it.

If it ever happens again, exit your game and back up your autosaves.

Set AutoSaveInterval = 1 to make sure you autosave every single turn.

Until then, I'm presuming the bug doesn't exist.

This sounds like a worthwhile idea.
Where does one find the AutoSaveInterval to change it?

Thanks,
sb
 
Well, I don't see how you can expect Solver to fix this "problem", since no one else has seen it, and you don't have a save game to show it.

If it ever happens again, exit your game and back up your autosaves.

Set AutoSaveInterval = 1 to make sure you autosave every single turn.

Until then, I'm presuming the bug doesn't exist.

Now I am not saying this did or didn't/couldn't happen. I will also assume you are an experienced player. Are you saying that you've never seen weird crap happen in this game? Whether its a repeatable bug or a glitch, your presumption of whether it happened or not means nothing. Get over yourself. He was simply asking whether others have had this issue. Take it for what it is and if you've never seen it don't make the guy sound like an idiot. Crap happens whether you have proof or not. And try decaf, it's juist as tasty as regular these day.
 
Where does one find the AutoSaveInterval to change it?

_Civ4Config Shortcut
you can find the it in the folder you installed Civ4. It references C (OS Drive):\Documents and Settings\Username\My Documents\My Games\Beyond the Sword\CivilizationIV.ini"

You will also need to set a decent number on:
MaxAutoSaves, 10+ should be enough. Just remember to reload the turn the bug occurs and resave it in a standard format so that it will not get overwritten.
 
_Civ4Config Shortcut
you can find the it in the folder you installed Civ4. It references C (OS Drive):\Documents and Settings\Username\My Documents\My Games\Beyond the Sword\CivilizationIV.ini"

That's not the one you want to change. Your need the actual ini file in My Documents\My Games\Beyond the Sword, not just the shortcut.
 
To Viking:

Edit the file

CivilizationIV.ini

in your My Documents\My Games\Beyond The Sword directory.

Look for the line

AutoSaveInterval = 4

and change it to

AutoSaveInterval = 1

You might also want to change the line above it to

MaxAutoSaves = 50

or some other number bigger than the default value. That way, you can go back 50 turns (or whatever you set it to).


To Dartan. Okay, I'll "get over myself" if you want. But I'm still placing my bets against JSwartz's bug ever happening. He only joined this forum a month ago, so it's not like he's one of the experts posting a bug without proof. (If he was an expert, he'd have proof, and there'd be no need to ask for it.)

All I'm asking for is some evidence. If that means I'm full of myself, so be it.
 
Hey everyone, though I'm sure this has been asked before I'm curious if this or another patch will change the infamous 3.17 capitulation thresholds back to those in 3.13 or prior? That's pretty much the only thing keeping me from updating my game, and I'd like to know if I could go around it. (galley barbs too, but I think I could handle those)
 
obviously nobody believes me!

No, it's not that, just trying to eliminate user error and clarify things :)

I've had weird rare glitches happen too at times, just like with all software I use a lot. One example possibly related to yours is seeing boat passengers "walking on water", another is units running in from the side of the screen. They're very rare though, and I always assume a temp graphics glitch.

I can't recall having an operational glitch like yours though, involving action--only "looks funny" glitches. Chances are very high what you got was a weird extremely rare glitch, rather than a bug as generally defined [ie reproducable error]. Soldier on :)
 
It'd be easier to live with the glitch if it was just purely graphical, but I guess I have to this time too, if that is in fact what it is. Perhaps I'll be able to muster up a desire to play again that this killed quite swiftly and effectively. :)
 
so, what happened to the new version of Solver's??? Wasn't it supposed to be available this past weekend?
 
IMO, for hobby projects like this that will automatically have to wait anytime "real life" interferes, the only ETA one should ever give is "when it's done". ;)
 
Back
Top Bottom