Bring a Galley Ship home

docbud

Emperor
Joined
Feb 14, 2012
Messages
1,518
I realize that those ships can't cross ocean tiles.

But I captured a few from Barbs and converted them, and tried to bring home.

I clicked on the ship and clicked on a capital water tile, and it said it would take 10 turns. I figured it would do automatically. I clicked the ship and the appropriate water tile....

But no...next few turns it sat there. So I tried to bring home again, and then it was 18 turns. And then 23, and then 48, and now up to 73 turns.

I thought once I gave directions, it would keep on moving and do what I wanted.

I finally deleted the damn things after 50 turns as it was pretty much apparent that it would take a million turns to bring into my territory.

Any ideas why my clicking the ship and clicking my home territory would not work? I mean, it's basically telling those ships to automate and come home. But they move one hex and then sit there. And when I try to bring home again, it says it will take longer, and they move one hex, and sit there again.

Mac version, and prior to Fall patch.

Moderator Action: Moved to General Discussion, because it's rather a question about some game mechanics and not about strategy ;).
 
Don't automate. Yes, it can be tedious to manually shepherd those ships to your capital, but autopathing is fraught with unexplainable decision making, as you have observed.
 
Galley, trireme and gallease can't go across the ocean tile. Need to bring them into your own border and upgrade them.
 
Any ideas why my clicking the ship and clicking my home territory would not work? I mean, it's basically telling those ships to automate and come home. But they move one hex and then sit there. And when I try to bring home again, it says it will take longer, and they move one hex, and sit there again.

Unexplored areas will be treated like they can be moved on (except hidden barbs for civilian units). But as you get closer you unveil that the unexplored area are mountains or ocean tiles in your case.
 
It's what FeiLing said. Even though it may be obvious to you based on map type and common sense that there is no coastal path in the fog of war the AI doesn't know it. It will chart a course that goes to the nearest fog of war then through the fog of war to coast that is connected to wherever it is headed.

The reason the estimated time keeps going up is probably because it keeps revealing more impassable terrain that it has to go around to reach the fog of war each turn. The reason it rises so dramatically is because, for whatever reason, the pathfinder plans on moving through the fog of war at a rate of only 1 tile per turn so making the journey longer makes the estimated time go up quickly.

You should be able to see this in the course that the pathfinder shows you.

I don't know if I would characterize it as a bug. I like the ability to path a unit through some fog of war when I'm not worried about what's in the fog. It wouldn't really be reasonable for you to use the pathing system to get information about what's behind the fog of war, so you're left with the way it is now. It's more just one of those things you learn and know about civ.
 
Thanks for the explanations, gang. I ended up deleting them as it was just too much of a bother trying to move them back home.

I may reconsider naval battles with barbs across the ocean in the future, as once I capture the ships, they may be hard to get back home.

MOD: Thanks for moving. I didn't realize it was a general question topic. Thanks again.
 
Back
Top Bottom