| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
|
CardName: Missing (or badly documented) import features Cost: UW Type: Pow/Tgh: / Rules Text: The import is not so well documented, and maybe some features are missing. Such as, it is not so clear how to do (or if it can be done; some probably it cannot be done at all): - Color indicators - Frames (e.g. adventurer cards, split cards, etc) - Mechanics - Better information about how they should be formatted You should probably also mention that CSV quoting is required. Flavour Text: Set/Rarity: Multiverse Feedback None
Missing (or badly documented) import features
  The import is not so well documented, and maybe some features are missing. Such as, it is not so clear how to do (or if it can be done; some probably it cannot be done at all):
- Color indicators - Frames (e.g. adventurer cards, split cards, etc) - Mechanics - Better information about how they should be formatted You should probably also mention that CSV quoting is required. |
History: [-] Add your comments: |
Multipart cards (DFCs, split cards, adventures etc) indeed can't be imported. This is definitely a bug / long-standing enhancement that's needed doing. I don't really know quite how it should be represented though. The JSON Export does export things fairly sensibly, with
{"name":"Diffuse Essence",...,"layout":"double-faced","names":["Diffuse Essence","Concentrated Rage"]},{"name":"Concentrated Rage",...,"layout":"double-faced","names":["Diffuse Essence","Concentrated Rage"]}. I could allow something like that in the import screen.Mechanics I think you can specify in card text like "[myMechanicName
]", but can't import/export the actual mechanics.
Colour indicators... hm, I don't know OTTOMH, but yes, you may well be right that they can't be imported. That at least should be an easy add.
I've added
colour_indicator,activeandwatermarkto the importable fields.Still need a way to import/export mechanics and the multipart frames.
OK, good you have added colour indicator and active; thank you. (Later I might update my export template to support exporting them to Multiverse, but not at this time.)
The Magic: the Gathering template in TeXnicard uses columns in the database table: "Kind" (normal, split, double-face, melded, etc), "Secondary" (boolean, for back faces of double-face cards, etc), "Meld_ID" (only for meld cards), and "Other_ID". Each part of the card is a separate record in the database; the "Meld_ID" and "Other_ID" fields link the two parts together.
I don't know if you want to do similar in Multiverse or not.
All of that exists already, as I recall from writing a program that reads the JSON/XML, it's just not part of the import interface. I imagine there would need to be some sanity checks on the "Other_ID" (the fields are called "multipart", "link-id"/"parent-id" in XML export).