#1 - Not a bug per-se, just something which might help figuring out the H3C logic of hero path calculation. I noticed this by accident [size=75](I wanted to test if a 0.63 bug I never got the chance to report - accessing Archer’s Tower from the side - is still there in 0.64; but I see that has been fixed)[/size].
The capture below is from a test map I’m using sometimes to check things which are not easily reproducible. The hero is a the right edge of the Swamp terrain, and only 1 tile away from the upper edge of it. If I try to move him more than 3 tiles up, this is how VCMI calculates the path:
H3C on the other hand behaves quite interesting:
a. If I choose the same destination with the mouse, H3C creates a straight line path, which the hero afterwards follows.
b. If I choose the same straight-line path, but instead of moving the hero, I click “End Turn” - the selected straight path suddenly changes to the curved one from the VCMI shot above . However, that does not mean the hero follows that curved path. If I give the move command (mouse click, M or Move button), the hero ignores the curved path which appeared after End Turn, and moves up in a straight line.
Now, I don’t know if I didn’t actually just found a H3C bug, but I thought of posting this anyway, in case it would be of any help for figuring out how the path calculator worked in H3C. If you want to double check the behavior reported above, I’m attaching here the map I used for testing.
The map can be easily used also to check another bug, which we have since 0.63 and was not corrected yet:
#2 - VCMI crashes after hero reaches level 15.
just testing.h3m (3.55 KB)