Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
Mechanics | Upcoming releases | Skeleton |
CardName: More options in Export Cost: Type: Feature Pow/Tgh: / Rules Text: The export page should offer more options and a way to export a subset of cards. There's somewhat of a continuum between the skeleton, the cardlist, the visual spoiler, a hypothetical printer-friendly playtest slips page, and the plain-text and CSV export. Flavour Text: Set/Rarity: Multiverse Feedback Common |
History: [-] Add your comments: |
Oooh! Oooh! Can we get an export format for MSE?
If anyone can point me at any doc for MSE's format, I'd be happy to try. I've not found any explanation of what their format is so far.
This seemed fairly complete: http://magicseteditor.sourceforge.net/doc/file
My request is very very non urgent though. Do useful stuff first ;)
Wow. Yeah, that's awesome. I ought to be able to do something with that.
As you say, though, not particularly soon. Perhaps in the next-but-two release, so sometime around spring-summer.
i want a JSON format that could work with a hypothetical custom-set playtesting webapp. we would have to work out the formating, although i do have a working one from a previous project. however XML may do for now to test the app. (ideally the webapp should accept other popular formats as well. main thing i'm concerned is how comprehensive those formats are and how they handle complex cards, like split cards.)
benefits of JSON are
1. can contain any and all data about a set, cards, and other data in a single file.
2. can handle cards, sets, and pack data, etc. of any complexity
3. easily parsed by javascript and other languages
4. application-neutral. any software can read and write the format easily
I'm certainly up for that in theory. I should mention that Chowlett is working (theoretically with some help from me) on a web-based draft server, Multidraft, designed to integrate with Multiverse. But I think a nice standardised export format such as JSON ought to be compatible with both of those.
draft server is cool. but according to wotc, sealed is a better format to test new sets. so i hope multidraft can do sealed.
edit: it seems there is already a MTG JSON project. (http://mtgjson.com/) . it's a good starting point, however, i would try to normalize the data.