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

Using "Type" as a Card Property Causes Strange Errors #1914

Open
zz1000zz opened this issue Dec 9, 2019 · 0 comments
Open

Using "Type" as a Card Property Causes Strange Errors #1914

zz1000zz opened this issue Dec 9, 2019 · 0 comments
Labels

Comments

@zz1000zz
Copy link

zz1000zz commented Dec 9, 2019

It appears "type" ought to be a reserved word as defining a card property with it as the name causes strange errors. o8build doesn't catch this, meaning a game package will build successfully but not work when a game is made/the deck editor is opened.

It's worth mentioning the problem happens if the property is defined in definition.xml and any card exists in a set.xml file, regardless of whether or not any card sets a value to that property. Interestingly, if no card exists in any set.xml file, the deck editor will not throw any errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants