Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Warnings while building deck data
See original GitHub issueMTGJSON Version: 4.X.X
4.4.0
Description of Bug:
While buildeing the decks I get blocks of warnings like this.
[INFO] 2019-04-30 00:04:41,484: Finished deck Replicator
[WARNING] 2019-04-30 00:04:41,489: No match for {'name': 'Mountain', 'set_code': 's00', 'number': '30', 'foil': False, 'count': 2, 'multiverseid': 25480}
[WARNING] 2019-04-30 00:04:41,489: No match for {'name': 'Forest', 'set_code': 's00', 'number': '13', 'foil': False, 'count': 2, 'multiverseid': 25482}
[WARNING] 2019-04-30 00:04:41,489: No match for {'name': 'Swamp', 'set_code': 's00', 'number': '49', 'foil': False, 'count': 2, 'multiverseid': 25478}
[WARNING] 2019-04-30 00:04:41,490: No match for {'name': 'Giant Growth', 'set_code': 's00', 'number': '15', 'foil': False, 'count': 1, 'multiverseid': 25502}
[WARNING] 2019-04-30 00:04:41,490: No match for {'name': 'Orcish Oriflamme', 'set_code': 's00', 'number': '34', 'foil': False, 'count': 1, 'multiverseid': 25540}
[WARNING] 2019-04-30 00:04:41,490: No match for {'name': 'Rod of Ruin', 'set_code': 's00', 'number': '40', 'foil': False, 'count': 1, 'multiverseid': 25529}
[WARNING] 2019-04-30 00:04:41,491: No match for {'name': 'Soul Net', 'set_code': 's00', 'number': '46', 'foil': False, 'count': 1, 'multiverseid': 25543}
[WARNING] 2019-04-30 00:04:41,492: No match for {'name': 'Terror', 'set_code': 's00', 'number': '51', 'foil': False, 'count': 1, 'multiverseid': 25504}
[INFO] 2019-04-30 00:04:41,498: Finished deck Player A's advanced pack
What do they mean? Are the mentioned cards not added to the deck or are there some data missing for the cards?
If the affected deck gets incomplete maybe some more info should be added to the warning.
Either way I think the affected deck should be mentioned in the warning.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
5 Warning Signs of an Unsafe Deck - Gary Smith
People often get injured due to weak or wobbly railings on a deck. The railing must be properly attached to the perimeter of...
Read more >Deck Safety: 5 Warning Signs of an Unsafe Deck
5 Warning Signs of an Unsafe Deck ; 2. Loose Connections ; 3. Corrosion of Connectors and Fasteners ; 4. Rotting Wood ;...
Read more >Coastal decks: Red rust on decks is a safety warning - ICC
Simply stated, visible red rust and rust stains are a warning that critical structural elements of a deck may be unsafe and at...
Read more >Common Warning Signs Your Deck Is Deteriorating
One of the more obvious signs that your deck needs a repair is when you start to notice the wood rotting. Rot will...
Read more >6 Warning Signs of an Unsafe Deck - YouTube
Did you know that deck collapses have increased by 20% since 2007? The good news is that deck failures are preventable.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hmm, I thought everything except S00 was fixed already. I’ll fix them for reals on next update I guess.
Yep, look into that when you can? Closing as this isn’t an issue on my side now.