LEGAL

Deckmeister is unofficial Fan Content permitted under the Fan Content Policy. Not approved/endorsed by Wizards. Portions of the materials used are property of Wizards of the Coast.
©Wizards of the Coast LLC

ABOUT

Deckmeister v0.5, made by Drentel.

Made with HTML, CSS, pure JS and spite for the current state of the web.

This is an early version - expect bugs and save often.

HOW TO USE

Deckmeister can be used as a normal full-featured deck editor, but it also has support for custom proxies (vanilla cards with changed visuals, e.g. art, frame) and entirely custom cards.

To add vanilla cards, click on "Scryfall" in the left panel, search for a card, then click the one you want from the search results. The card will be added to your deck's maybeboard. Form there, click on the card to move it to different areas of the deck, change its printing, or remove it entirely.

If you have multiple copies of a single card, the "Set all to printing" button will set all copies of the clicked card to its printing. This is mostly useful for basic lands.

Use this importer to get your deck into tabletop simulator.

To add custom cards and proxies to your deck, you must first add a repository that contains data about them.

Example repositories:

• Drentel's custom cards (entirely customs):

  https://filedn.eu/lPUcGy7L5V0Bkha5QyKGbLf/repo.json

• Drentel's alters (entirely proxies):

  https://filedn.eu/lPUcGy7L5V0Bkha5QyKGbLf/alter_repo.json

To add a repository copy the address, click on "Custom", input the repository address into the top field (above the "Add Repository" button), then click the "Add Repository" button. Cards from it should appear in the card list below. Add them the same way you add vanilla ones.

Do note that proxies from repositories will show up when you'll try to change printings of vanilla cards. You do not need to add them separately.

HOW TO MAKE YOUR OWN REPOSITORIES

Repositories are JSON (specially formatted text) files that contain data about cards contained in them (names, oracle text, links to images, etc.)

To make your own repository you need to:

• Create the actual JSON file with correct data about all your cards
• Host it (and all images linked in it) on a publicly available endpoint.

The first step is relatively easy, but might be time-consuming depending on how many cards you're planning to add:

• Download one of the example repositories (just input the address into your browser address bar and copy the data to a text file with a .json extension)
• Look at it. The repositories contain all supported card types as examples. Some tips:
  • Everything is case-sensitive. Make sure to avoid mistyping card names and such.
  • Mana is written as big letters in curly brackets. {W}{U}{B}{R}{G} and so on. Hybrid mana is written as {UB}{RW}, NOT {U/B}{W/R}. Also, make sure that your hybrid mana is correctly ordered. {UB} is blue-black {BU} is invalid. Phyrexian mana has a P at the end {BP}{RWP}...
  • If your card is double-faced (this also applies to split cards and cards with adventures) and has two mana costs, split them with "{-}", with the first face's cost coming first.
  • Look at "Sinkou the Vengeant" in the custom repository for an example of adventures/split cards. If your card is double sided, move the "image_uris" field inside each of the "card_faces" entries and put images for each face separately there
  • The "id" field for each card should be different within the repository. Different repositories can have cards with identical id fields, that will not cause issues.
  • If you have multiple copies of the card with the same exact name, only the first one will display in the general list, and all others will be counted as alters for it. Access them via "change printing".
  • When you're finished, make sure to verify your syntax using one of the million online tools. Personally recommend the beautifier that appears when you search "beautify json" in DuckDuckGo.

For the second step, all you need to do is to host the repository file on a publicly available direct access endpoint. Essentially, people should be able to type the URL to your repository in their address bar and see it the same way you see the example repositories.

Take note: any changes you make to your repository might take up to 24 hours to show up when importing it. To sidestep this, install a "CORS Unblocker" browser extension and remove all text from the "CORS Proxy" super secret setting below before trying to import the repository.

If your import doesn't work, open the F12 console and check for following:

• If it shows a 404 message when trying to import the repository, your link is likely wrong.
• If it shows a "TypeError" or a "SyntaxError", your json is likely not correctly formatted. Recheck it with a json beautifier and compare it to the example again.
• If the console is spamming messages, it's most likely that one or more of your image links don't actually point to an image file. An image link will embed as an image (not as a site preview) when sent as a discord message.

Google drive does not work. I personally use pCloud. GitHub also works, and is free. The image files of the cards need to be hosted the same way.

SUPER SECRET SETTINGS

Don't touch these unless you know what you're doing

CORS Proxy