Repository navigation
v0.8.5
0.8.5 (2026-11-03)
This release fixes what an audit of the corridor code found: a path
with NULL arrays crashed mnavSetCorridor, and corridors with a
position or target that is not finite were used instead of refused.
No results change.
Fixed
mnavSetCorridorchecked that a path has a polygon and a point,
but never checked itspolygonsandpointspointers or the points
it copies. A path with a count of 1 or more and a NULLpolygonsor
pointscrashed it. A path whose first or last point has a NaN was
loaded withmnav_success, leaving the corridor's position or
target NaN. Such a path is now refused withmnav_errorInvalid
before the corridor is touched. Paths frommnavQuery_FindPathand
mnavQuery_FinishPathload as before.
(#290)- No corridor call checked a corridor's
positionandtarget. With
a NaN position or target,mnavQuery_FindCorridorCornersand
mnavQuery_FindCorridorAreasreturnedmnav_successwith a NaN
corner and a NaN area run, and some moves and shortcuts succeeded and
kept the NaN. A well-formed corridor now has a finite position and
target, so every call that checks for a well-formed corridor refuses
one whose position or target is not finite withmnav_errorInvalid.
mnavSetCorridorreplaces both ends, so it does not check them.
(#291)