0000335: VCMI pathfinder seems to go for the most cost effective path at end of day, while H3 went for the most intuitive choice.

Notes
(0000559) Warmonger (administrator) 2010-01-02 07:41	I guess in original game road bonus works only if we move according to its direction.

(0000560) Zamolxis (viewer) 2010-01-02 11:28 edited on: 2010-01-02 11:29	It's not really that. If Ivor would have enough MP to move one extra tile on the road, the path would overlap perfectly in VCMI as well. You can test that by editing the map attached, putting Ivor 1 tile lower. It really looks like VCMI is smart enough to handle the last remaining ~70 MP of the hero, depending on his next move the following turn (which would cost him only 50 MP, i/o 70 for the diagonal step in H3). While this is a smart behavior, I am just a bit concerned the players will fall into the same trap I fell when first noticing this, thinking it's a bug.

(0000615) Tow (developer) 2010-02-10 03:44	Pathfinder has been designed to find the most optimal path, using rules of movement from H3. In this case I'd treat current VCMI behaviour be that as bugfix for problem present in H3 (offering suboptimal path). So - it's not a bug, it's a feature! :-) (however we should consider documenting it somewhere)

(0000745) Zamolxis (viewer) 2010-03-02 21:30 edited on: 2010-07-24 14:53	FYI - If you don't mind, I'm going to leave this one in Resolved, without moving it to Closed, until we document it properly somewhere. EDIT: Another reason why I prefer to not close it yet, is because a few times the path chosen seemed quite unrealistic for the eye, so it may bother the players. I want to keep monitoring this for a while. I'm also moving this from "no change required" to "suspended". If the path chosen seems unrealistic for the player, perhaps we should still consider one of the following: - go back to the H3 system (sacrificing an almost insignificant bonus, for the sake of a more realistic looking choice) - or else maybe find a way to "store" the sacrificed movement points lost, and give them as bonus in the beginning of the next day (it'll be like hero "going to bed earlier" in order to "wake up earlier" the next day) //Apologies if I get annoying insisting on this, but if I have the feeling the hero makes strange path choices - even though I know it's for the sake of most efficient use of movement points, I can imagine other players will get the feeling VCMI implemented pathfinding rules "worse" than H3 (and we can't expect them all to read all that we documented to understand why it is like this). But of course, this is by no means a priority. It can wait for finer tuning till after the 1.0 release.//

Issue History
Date Modified	Username	Field	Change
2010-01-01 19:44	Zamolxis	New Issue
2010-01-01 19:44	Zamolxis	File Added: VCMI_Tests2.h3m
2010-01-01 19:44	Zamolxis	Issue generated from: 0000327
2010-01-01 19:44	Zamolxis	Relationship added	related to 0000327
2010-01-01 19:45	Zamolxis	File Added: 2010-01-01_H3Path.jpg
2010-01-01 19:45	Zamolxis	File Added: 2010-01-01_VCMiPath.jpg
2010-01-01 20:05	Zamolxis	Priority	normal => low
2010-01-01 20:05	Zamolxis	Severity	minor => feature
2010-01-01 20:05	Zamolxis	Summary	Pathfinder does not always look for a path going down as much as possible (with respect to the condition of the least cost) => VCMI pathfinder seems to go for the most cost effective path at end of day, while H3 went for the most intuitive choice.
2010-01-01 20:05	Zamolxis	Description Updated	View Revisions
2010-01-01 20:05	Zamolxis	Additional Information Updated	View Revisions
2010-01-02 07:41	Warmonger	Note Added: 0000559
2010-01-02 11:28	Zamolxis	Note Added: 0000560
2010-01-02 11:29	Zamolxis	Note Edited: 0000560	View Revisions
2010-02-10 03:44	Tow	Note Added: 0000615
2010-02-10 03:44	Tow	Status	new => resolved
2010-02-10 03:44	Tow	Resolution	open => no change required
2010-02-10 03:44	Tow	Assigned To	=> Tow
2010-03-02 21:30	Zamolxis	Note Added: 0000745
2010-07-13 10:51	Zamolxis	Note Edited: 0000745	View Revisions
2010-07-21 15:42	Zamolxis	Note Edited: 0000745	View Revisions
2010-07-24 14:41	Zamolxis	Resolution	no change required => suspended
2010-07-24 14:53	Zamolxis	Note Edited: 0000745	View Revisions
2014-05-30 17:39	beegee	Status	resolved => closed