Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors loading JR cards in deck editor #4311

Closed
Zzooouhh opened this issue Dec 31, 2017 · 3 comments
Closed

Errors loading JR cards in deck editor #4311

Zzooouhh opened this issue Dec 31, 2017 · 3 comments
Assignees
Labels
bug Bugs and errors

Comments

@Zzooouhh
Copy link
Contributor

Zzooouhh commented Dec 31, 2017

When you load up a deck that contains cards from the Masterpiece Series Amonkhet edition in V10, you'll be greeted with an error message - "Errors while loading deck - founded problems with deck: Layout mismatch: Expected 4 cards, but got 1 in layout 'MAIN'". This was with a test dck file containing three MPS-AKH cards and one Kaladesh Masterpiece; the numbers in other deckfiles always correspond to the number of MPS-AKH cards (i.e. "99 cards, but got 98" in an EDH deck with one masterpiece).

The deck file after the error will load, but will present various graphical and possibly card database glitches - after sorting by card type, I've once had a card disappear, another time I've had a Land Tax swap for a Wall of Wood, and once the infringing masterpiece cards were sorted 3 columns away from everything else.

EDIT: Land Tax swapping for Wall of Wood is related to the numbering changes for 4th edition, not this bug.

@JayDi85 JayDi85 added the bug Bugs and errors label Dec 31, 2017
@JayDi85 JayDi85 closed this as completed in 1a252e6 Jan 3, 2018
@Zzooouhh
Copy link
Contributor Author

Zzooouhh commented Jan 9, 2018

This same issue happens for JR cards (Judge Rewards) as of version V11c.

@Zzooouhh Zzooouhh reopened this Jan 9, 2018
@Zzooouhh Zzooouhh changed the title Errors loading MPS-AKH cards in deck editor Errors loading JR cards in deck editor Jan 9, 2018
@JayDi85
Copy link
Member

JayDi85 commented Jan 9, 2018

Yeah, i will check.

@JayDi85
Copy link
Member

JayDi85 commented Feb 4, 2018

Fixed via 5722b51

@JayDi85 JayDi85 closed this as completed Feb 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs and errors
Projects
None yet
Development

No branches or pull requests

2 participants