AutoMarkAssist

# AutoMarkAssist ## [v3.4.15](https://github.com/Swatto86/AutoMarkAssist/tree/v3.4.15) (2026-05-30) [Full Changelog](https://github.com/Swatto86/AutoMarkAssist/compare/v3.4.14...v3.4.15) [Previous Releases](https://github.com/Swatto86/AutoMarkAssist/releases) - Version 3.4.15 - fix proximity and mouseover marking Bug-fix release for the automated marking engine. - Proximity marked nothing: CheckInteractDistance returns nil for hostile units on the 1.15 client and that nil was treated as out-of-range, filtering out every candidate. Range check now trusts positive results and falls back to nameplate presence so the nearest mobs are marked. - Mouseover applied the wrong mark or no mark when other unmarked mobs were nearby: the soft-reserve pass pre-claimed slots for mobs that were not actually marked. The hovered mob is now allocated directly via normal mark priority (DB preference -> Skull -> Cross -> CC). - Marks were dropped the instant a mob lost its unit token, freeing the icon and letting the next mob receive a duplicate. Added a last-seen grace window; deaths still free the icon immediately via the combat log. - CC-duration check in the death cascade read UnitDebuff return values from the wrong positions, so the guard against promoting a CC'd mob to a kill mark never fired. Corrected to the live layout. - Mouseover range limit could silently block marking for the same reason; it is now fail-open. - Mouseover skips the expensive pack scan for non-hostile/dead units. Update README (drop stale soft-reservation wording). Bump TOCs and AMA.VERSION to 3.4.15. Add 3.4.15 changelog entry.