{"ops":[{"insert":"Howdy. I made a "},{"insert":{"card-link":"Faceless One"}},{"insert":" and "},{"insert":{"card-link":"Viconia, Drow Apostate"}},{"insert":" deck with "},{"insert":{"card-link":"Umori, the Collector"}},{"insert":" as a companion. Umori is displayed as an error that states \"You have a card outside of your commander's color identity - Umori, the Collector\" and I'm guessing its because Archidekt c"},{"attributes":{"color":"oklab(0.321044 -0.000249296 -0.00927344)","background":"oklab(0.0846607 0.00000385568 0.00000169128 / 0.03)"},"insert":"hecks the legality of your sideboard before applying Faceless One's color identity. This combination of cards should be legal. Adding an option of setting a color of \"chose a color\" cards or changing the order of checking card legality should be enough to fix it."},{"insert":"\n"}]}
0
{"ops":[{"insert":"You're likely correct in the reasoning, but your solution would be too complex to implement. Providing users a way to choose a color would be extremely annoying since we'd need to store that data somewhere. For a one off like this it wouldn't be the end of the world, but the way wotc plays fast and loose with the rules of MTG, hard coding a database column for a one off interaction wouldn't be wise. \n\nI'll see what I can do to fix the issue you're seeing client side. \n\nIf you can, could you link the deck you're talking about (not required, but it'll make my life easier since I'll have something to test with).\n"}]}
1
{"ops":[{"insert":"Thanks for the quick response.\nlink to my deck: https://archidekt.com/decks/10904538/viconia_faceless_one_umori_value_machine\nI also checked if the same error comes up with different companions and it does.\n"}]}
0