I've noticed that the pathfinding tool will sometimes show an incorrect distance that your selected army can travel in the current turn. When this happens it consistently shows the army as being able to move one tile further than it actually has the movement points to do. When you give the move order the army ends up one tile short of what was indicated, which can have painful consequences when you are trying to sneak by hostile forces safely.

I am seeing that too. One thing that also happens is that when the projected route leads through a city, the tool does not account for the one free movement and shows the possible destination as one tile shorter than you can actually go.

It's some variable involving road travel and possibly also moving through cities where its calculating that the unit can move one tile further than it actually can. Unfortunately from a bug squashing perspective it's not a very reproducible bug, but I'll see what I can do to pin it down further for you.

Yes, it is tricky to document ... you don't realize the game gave an incorrect estimate for how far a unit can move until after it moved, at which point it is too late to take a screenshot of how far it had estimated you could move before you actually moved.

Yes, it is tricky to document ... you don't realize the game gave an incorrect estimate for how far a unit can move until after it moved, at which point it is too late to take a screenshot of how far it had estimated you could move before you actually moved.

Good point.

I'd love the ability to easily setup scenarios to test stuff, but as it stands now I'd either need to get heavily into modding (which could invalidate the results) or use an existing game, which doesn't always work out since I don't have access to everything.

I've seen this in a non-road situation also. It occured with a unit I had split a from a stack with Tireless march.

When this happens on the road situation, if you move your cursor around, it will recalculate and give you the correct distance. Very difficult to reproduce. I've been trying to get a good screenshot for a while now.

... and after right clicking on that 3rd tile (which math indicated it couldn't make it to), indeed this is the result:

As you can see, its movement is still set to the 3rd tile, but it only made it to the 2nd tile despite the mouse-hovering path (before issuing the move command) indicating it could make it to the 3rd tile in one turn.

When this happens on the road situation, if you move your cursor around, it will recalculate and give you the correct distance. Very difficult to reproduce. I've been trying to get a good screenshot for a while now.

This is my experience, as well. Move your cursor and re-position it and it will show you being one move short.

Thinking on it, especially since I started looking to try to document it, it seems to be a weird rounding error when fractional movement points are used (either because the terrain, such as hills or swamp, consumes one-and-one-half-movement points, or roads which moving upon consumes only one-third or so of a movement point). It isn't simply rounding up, though ... no matter how small of a fraction remains, you seem to actually be able to move at least one tile (so it should always be rounded up) but for some reason, an extra rounding up seems to occur sometimes, seemingly making half a movement point for some reason rounding up to 2.

I've found my earlier theory about fractional movement points inaccurate, as its overestimating how many tiles can be travelled the first turn even on normal plains with a single movement point cost. :/