"This card's name is always treated as" in banlist files

YGO Omega Bugs
, ,
1

  1. Bug description
    Adding a card to a banlist that has different cards that are always treated as that cards name results in all cards that are always treated as that card to handled as the same card. For example: adding “Umi” to a banlist will result in all cards that are treated as “Umi”, like “A Legendary Ocean”, to fall under the same status (forbidden/limited/semi/unlimited).

  2. Bug reproduction steps
    Add cards like “Umi” to a YGOPRODECK collection and export it as a banlist (lflist.conf). Instead of doing that though you can also use a *.conf file with the following content:

    !Umi Test
$whitelist 
22702055 1

    I’m unsure whether this applies to banlists directly written in an sqlite database or only to the format that an lflist.conf is in.

  3. Screenshot OR error code

    image
    image1876×1036 511 KB

    This image uses the banlist in the code block above and a filter to “limited 1”.

  4. Expected behavior
    Only exactly “Umi” should be available given the banlist above filtered by the stated filter. Cards like “A Legendary Ocean” or “Pacifis, the Phantasm City” should not be legal.

  5. What OS are you using
    Linux; this is reproducible on windows as well though