Bug when artifact created by Sanctifying Elixir

[Shanksu7]

Current Behavior

The box displaying the substats of an artifact created with Sanctifying Elixir is slightly different, as it includes a small purple banner on the card, which shifts the substats slightly downward.

Expected Behavior

The scanner stops scanning

Reproducing a Behavior

Scanning an artifact created by Elixir

Device OS

Windows 11

Genshin Impact Version

5.7

Inventory Kamera Version

1.3.17

Screen resolution, screen mode, and UI scale

1920x1080

Additional notes and remarks

No response

Evidence

No response

Preflight Checklist

• I have checked for similar issues in the issue page, and I have not found any similar to mine.
• I am using the latest version of the scanner.
• I tried setting the scanning delay to maximum, and it still doesn't work.
• I have attached the video recording to the bug report.
• I have attached the error log to the bug report.
• I am available to later explains the issue.
• I have disabled (or documented) all screen filtering software, plugins, and enhancements while scanning.
• I use default in-game keybindings or have configured keybindings for the scanner.

[wuppiwuppi]

confirmed. same platform + resolution

[Karrai]

Quick fix could be to have the program click "locked artifacts only" and have players unlock artifacts until a proper fix is finalized.

[mosu-e]

Quick fix could be to have the program click "locked artifacts only" and have players unlock artifacts until a proper fix is finalized.

Tried this but it'd keep removing filters on his own

[perezsam150]

As of 5.8 this bug is still present. Using the filters to selectively scan artifacts is also useless because the scanner removes all applied filters.

EDIT: From their Discord, there is a Github Fork that fixes the issue where it stops scanning artifacts that are defined by Sanctifying Elixir.

[escalonn]

this issue presents differently for me. instead of stopping, the scanner silently skips these artifacts without giving any indication about why and without writing anything to the logs. that behavior was very frustrating to debug.