You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the Import Feature, the importer interprets the "Rex" in "Tyrannax Rex" as a set, instead of part of its name. Adding the card via Card Catalog works normally.
To Reproduce
Steps to reproduce the behavior:
Go to Deck Editor
Click on Import
Input "1 Tyrannax Rex" as a card to import
The importer displays "Tyrannax [Rex]" and of course doesn't fetch the card.
Expected behavior
The importer should recognize Tyrannax Rex as the name of the card, not interpret "Rex" as a set.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows
Version 1.6.64
Additional context
I'm only a amateur programmer myself and a bit of a novice, but I suspect the fact that "Rex" has three letters might be what's causing the parser to trip and think it's a set code?
The text was updated successfully, but these errors were encountered:
Looking at the order the DeckRecognizer does things in, a fallback might be simpler than changing the order the patterns are checked in. Maybe something similar to the one for double faced cards?
So if the name isn't a real card but there's a set code, see if tacking the set code onto the name makes it a real card, and if so, proceed from there?
Describe the bug
When using the Import Feature, the importer interprets the "Rex" in "Tyrannax Rex" as a set, instead of part of its name. Adding the card via Card Catalog works normally.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The importer should recognize Tyrannax Rex as the name of the card, not interpret "Rex" as a set.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
I'm only a amateur programmer myself and a bit of a novice, but I suspect the fact that "Rex" has three letters might be what's causing the parser to trip and think it's a set code?
The text was updated successfully, but these errors were encountered: