When I try to ship resources it shows one time for traverling. When the resources are loaded and traveling the time is longer than what was shown before I clicked send. Don't think it affects military ships.
(reported) Trading ships times are wrong
-
- Bug
- EN
- Pi
- Cassiopea
-
-
Do you use Poseidon ?
Because, it could explain this difference.
Since few updates, if you use Poseidon to sent ressources or troups and the miracle ended before the ressources or troups are loaded, the time travel is not affected by the miracle.
For example, if you have Poseidon 5 for 10 minutes but the loading will take 15 minutes, the game will say [15 minutes + (travel time/2)] but in fact it will be [15 minutes + time travel]
-
I use it, but the miracle was not in cooldown. Try it in your world and see for yourself. I can reproduce this in all my accounts. All you need to do is send 1 cargoship somewhere and check the times.
-
I’m also seeing this behavior. For example, intra-island transport is showing 8 minute travel time in my trading port, but takes the usual 10 minutes once the goods are loaded.
-
I'm seeing this, too. Here's what it says when I am looking in the trading port. (I'm sending 1000 goods to a neighbor on the island and currently have Poseidon running.)
And yet when I actually send the goods, it's the normal speed.
I checked with sending goods between adjacent islands and got the same thing. The trading port is reducing the predicted travel time by 20%, but when the goods are actually being moved the time is normal.
-
Do you have a Premium account active? If so I'll hazard a guess that you're seeing the 10% reduction in build time from the latest update being incorrectly applied.
-
Do you have a Premium account active? If so I'll hazard a guess that you're seeing the 10% reduction in build time from the latest update being incorrectly applied.
I do not have a premium account active, and I am still seeing this behavior. It applies to freighters also.
-
That particular account does have premium, but I've checked other accounts that aren't running it and they also have this issue. So I don't think it's the premium account causing it.
-
It was ok for some days, but it is happening today.
-
Issue is known and forwarded.