MegaMek / Bugs / #4568 Certain jumps "illegal", or path-planned incorrectly

Derrick Turk - 2015-06-18

This also can occur traversing a downward elevation change; e.g. see attached.

bad_jump_1.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1 +1 @@
-Since recent revisions, certain legal jump moves are difficult or impossible to enter. E.g. try jumping a mech out of a 1-level depression to a hex in its rear arc. I believe this may be due to the changes introduced to fix #4567; possibly the updated heuristic needs to consider jump MP as a special case.
+Since recent revisions, certain legal jump moves are difficult or impossible to enter. E.g. try jumping a mech out of a 1-level depression to a hex in its rear arc. I believe this may be due to the changes introduced to fix [#4567]; possibly the updated heuristic needs to consider jump MP as a special case.

Nicholas Walczak - 2015-06-19

assigned_to: Nicholas Walczak

Resolution: none --> accepted

Milestone: undetermined --> stable 0.42
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nicholas Walczak - 2015-06-19

Fixed in [r11973].

You're exactly right, the ShortestPathFinder.getLevelDiff term for the heuristic should always return 0 if the MovePath is jumping. I had a feeling I was missing a case when I was writing the case...

As an aside, it's convenient if you attach a saved game of your test setup. In this case, it didn't take me long to reproduce it, but in general it saves me a lot of time if I can just load up a saved game.

Related

Commit: [r11973]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nicholas Walczak - 2015-06-19

(As a note, I left the entry for this bug out of history.txt. The bug was only in existence for about 7 hours. I feel like an entry in history.txt will be meaningless for people looking for a release changelog, and anyone who is going to encounter this bug is already going to be watching the commit messages.)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nicholas Walczak - 2015-06-19

Resolution: accepted --> fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dylan Myers - 2015-08-05

Status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Certain jumps "illegal", or path-planned incorrectly

Milestone

Searches

Help

#4568 Certain jumps "illegal", or path-planned incorrectly

Related

Discussion

Related