Skip to content

v0.8.5

Choose a tag to compare

@rawframe-release rawframe-release released this 03 Nov 01:07
1b2c29b

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

  • mnavSetCorridor checked that a path has a polygon and a point,
    but never checked its polygons and points pointers or the points
    it copies. A path with a count of 1 or more and a NULL polygons or
    points crashed it. A path whose first or last point has a NaN was
    loaded with mnav_success, leaving the corridor's position or
    target NaN. Such a path is now refused with mnav_errorInvalid
    before the corridor is touched. Paths from mnavQuery_FindPath and
    mnavQuery_FinishPath load as before.
    (#290)
  • No corridor call checked a corridor's position and target. With
    a NaN position or target, mnavQuery_FindCorridorCorners and
    mnavQuery_FindCorridorAreas returned mnav_success with 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 with mnav_errorInvalid.
    mnavSetCorridor replaces both ends, so it does not check them.
    (#291)