You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: