Skip to content

Fix AOB scan bounds and expose main-image ambiguity detection - #16

Draft
Krarilotus wants to merge 3 commits into
gynt:mainfrom
Krarilotus:fix/aob-scan-bounds
Draft

Krarilotus wants to merge 3 commits into
gynt:mainfrom
Krarilotus:fix/aob-scan-bounds

Conversation

@Krarilotus

@Krarilotus Krarilotus commented Sep 12, 2026

Copy link
Copy Markdown

TL;DR: On hold as a combined proposal: fix scan-range bugs and add an optional unique-match search API.

The existing scan can exceed bounds and skip final-position matches. Those are concrete bugs. Searching executable pages for two matches is an additional capability whose consumer requirement was withdrawn.

Changes: Clip readable ranges and fix short/end cases in the existing scanner. The draft also adds scanForAOBInMainModule and a package-version update.

Review / testing: Separate the range correction from the API expansion for review. The old scanner fails the native upper-bound regression; Debug/Release and boundary checks passed for the draft. Hotkeys/Recorder no longer require the added API. The author’s hold on new framework APIs still applies.

Fixes #15. Native regression run.

@gynt

gynt commented Sep 14, 2026

Copy link
Copy Markdown
Owner

When did you encounter said bugs? Do you have some reproducible code that causes the bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AOB scans exceed supplied bounds and miss boundary matches

2 participants