Fix minimap priority for impassable terrain pathfinding πΊοΈ#4361
Conversation
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. π€ Files selected but had no reviewable changes (1)
β Files ignored due to path filters (2)
βοΈ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: β Files ignored due to path filters (2)
π Files selected for processing (1)
You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughIn ChangesMinimap tile priority: Water > Impassable > Land
Estimated code review effortπ― 2 (Simple) | β±οΈ ~5 minutes Suggested reviewers
Poem
π₯ Pre-merge checks | β 5β Passed checks (5 passed)
βοΈ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description:
Changes the minimap downscaling priority in the Go map generator from
Impassable > Water > LandtoWater > Impassable > Land.Tristar noticed this bug and reported it in the discord map-maker-area:
Previously, any 2x2 block containing even one impassable tile would become impassable on the minimap, completely erasing narrow rivers inside or bordering impassable terrain. Since the water pathfinder runs on the minimap, this caused pathfinding failures near impassable terrain.
With water taking highest priority, narrow rivers are preserved on the minimap regardless of surrounding impassable terrain, ensuring the water pathfinder can route through them correctly.
Please complete the following:
Please put your Discord username so you can be contacted if a bug or regression is found:
FloPinguin