Patch 5.0.8 - TileCheckRule get_runtime_issues() Bug Fix

Release Date: May 15, 2026 Version: 5.0.8 Type: Maintenance / TileCheckRule Bug Fix Release

Highlights

TileCheckRule.get_runtime_issues() bug fix — custom rules that override get_failing_indicators() to call get_runtime_issues() now work correctly. Previously, get_runtime_issues() was never called by the indicator system, causing custom runtime issues to be ignored.
Order-of-operations fix — calling super.get_runtime_issues() before appending custom issues ensures custom _runtime_issues are not lost when the base class returns early.
API documentation clarified — TileCheckRule class documentation now explains when validate_placement(), get_runtime_issues(), and get_failing_indicators() are vs aren’t called.

Fixed get_runtime_issues() not being called by indicator system — The indicator system was checking validate_placement() and get_failing_indicators() but never calling get_runtime_issues(). Custom rules that override get_failing_indicators() to append custom runtime issues now work correctly.
Fixed order-of-operations bug in custom rule overrides — When a custom rule overrides get_runtime_issues(), it must call super.get_runtime_issues() BEFORE appending custom issues. The base class returns early if _runtime_issues is empty, so appending AFTER the super call was correct, but the pattern was not clearly documented.
Fixed character encoding issue in CollisionGeometryUtils — Removed U+0019 (SYN) character that was embedded in source code comments during copy-paste. This character was propagating through API generation into HTML output.

TileCheckRule class documentation updated — Now clearly explains:
- validate_placement() is called for pre-placement validation
- get_runtime_issues() is called by the indicator system for runtime checks
- get_failing_indicators() is called for visual indicator display
- The correct override order: call super first, then append custom issues