Closed JBCastr closed 9 months ago
@JBCastr Hey there, this bug should of been fixed a few updates ago. https://github.com/ssjshields/archetype-counter/commit/b963eab4f8d72e7d8d71c33681a496df2ab45119 Could you ensure you're on the latest main build and try encountering Farfetch'd again? https://github.com/ssjshields/archetype-counter/archive/refs/heads/main.zip
@JBCastr Hey there, this bug should of been fixed a few updates ago. Could you ensure you're on the latest main build and try encountering Farfetch'd again?
That screenshot was actually from the update I downloaded today. I DID just directly copy the counter config files folder from the previous version and pasted it into the newer version. Maybe that caused issues? I'll go ahead and download a completely fresh version without tampering with it to see if it works.
That screenshot was actually from the update I downloaded today. I DID just directly copy the counter config files folder from the previous version and pasted it into the newer version. Maybe that caused issues? I'll go ahead and download a completely fresh version without tampering with it to see if it works.
If the CounterConfig_PokemonNameFix file was overwrote, that could be why this is occuring. Ensure you have the latest copy of that file, you can still use your old hunt profile files.
@AnonymousPoke added additional logic when processing monster that have special glyphs or spaces in their names, as well as added Farfetch'd to the name fix list. As of recent updates this list is now available for the user to modify or add-on to, if there is a consistent failed to scan issue (occurs more often with less supported languages.) you can add the monsters name to the file to correct the scan.
That screenshot was actually from the update I downloaded today. I DID just directly copy the counter config files folder from the previous version and pasted it into the newer version. Maybe that caused issues? I'll go ahead and download a completely fresh version without tampering with it to see if it works.
If the CounterConfig_PokemonNameFix file was overwrote, that could be why this is occuring. Ensure you have the latest copy of that file, you can still use your old hunt profile files.
This is exactly what happened. My bad, it was a user error. Thanks for the help though!
@JBCastr, please download the latest main build to see if the Pokémon name still incorrectly scans. If it does, you can still resolve as pointed above in "CounterConfig_PokemonNameFix" file.
DEBUG_OCR_OUTPUT.txt