Failing to correctly scan Trailblazer will crash the character scanner

[kel-z]

I can't reproduce it myself (probably some combination of graphic settings and game resolution), but it is possible for the scanner to not recognize the Trailblazer character and try to read the character name instead (which will most likely produce a KeyError and crash the parser since Trailblazer's name is the account name).

Either fine-tune the Trailblazer recognition logic, or wrap everything in a try-catch to skip a character if it fails to parse. Whichever comes first.

[kel-z]

If HSR is running slowly, when clicking between different characters, the character name might not update fast enough before the scanner screenshots the name, resulting in duplicate character entries.

One solution is to keep a record of all seen characters so far, then if a duplicate is detected, wait and retry the name parse again, with a max of 5 attempts.

[kel-z]

This might explain why Trailblazer's name sometimes gets parsed, because after clicking off of Trailblazer and onto the next character, Trailblazer's name will get screenshotted and fail the Trailblazer check, thus causing the scanner to think the parsed name is an in-game character name.