Skip to content

Pathfinding at the intersection of land-water environments does not work correctly #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AlexSnowLeo opened this issue Apr 23, 2023 · 1 comment

Comments

@AlexSnowLeo
Copy link
Contributor

When there are obstacles with angular movement and the squares are of mixed land-water type. Contiguous obstacles must prohibit diagonal movement.

For example on the tutorial map.

изображение

2023-04-23.18.29.07.mp4
@ProgerXP
Copy link
Member

Confirmed, related to:

Core/client/H3.PathCost.js

Lines 183 to 194 in 55cafe3

// XXX+I,C Some diagonal movements (where any adjacent tile is a ground?) are prohibited on water. For example, one cannot interact with Mermaids after boarding [S] here (Mermaids shifted by one to the left are reachable):
//
// [_][_][ ][ ] _ = ground
// [ ][ ][ ][ ] [ ] = water
// [ ][#][@][#] [#@#] = Mermaids
// [ ][S][H][_] S = ship, H = hero on ground
// [ ][ ][_][_]
//
// A simpler example where ² is only reachable via ¹:
//
// [ ²[_] _ = ground
// [ ¹[S]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants