Digital

260 readers

8 users here now

MTG Arena and Magic Online discussion

Discussion related to Magic's digital games, including MTG Arena and Magic Online (or MODO).

Learn more about MTG Arena and Magic Online!

founded 1 year ago

MODERATORS

[email protected]

Looking for Decklists with Original Set Information for Preconstructed Decks (mtgzone.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

I've been wanting to get started using XMage and thought it would be fun to play a few matches against the AI with the GRN Guild Kit decks (GK1) using the original printings. I found decklists on sites like mtg.wtf that list the card names and quantities, but they don't specify the original set name and card number for each card.

For example, this GitHub repo has decklists for various preconstructed decks, but also lacks the specific set information and card numbers.

What I'm really looking for are decklists that include the card name, quantity, set name, and card number in the set for each card, ideally formatted like this:

quantity [SETCODE:collector number] cardname

This .dck file format used by XMage would allow me to easily import the exact preconstructed deck I want to play with the original printings, without having to rebuild it.

It made me think how nice it would be to have all the preconstructed decks available as .dck files with the original printings specified, nicely organized into folders by product. That way I could easily grab the exact deck I want to play with in XMage without having to build it manually.

Does anyone know if prebuilt decklists with detailed set data like this already exist somewhere for preconstructed products like the Guild Kits? Or if not, I may try writing a script to generate them before manually creating the files myself.

Please let me know if you know of any resources where I could find complete decklists for preconstructed decks specifying the card names, quantities, set names, and card numbers! This would save me a lot of time in recreating the decks accurately in XMage.

top 8 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

https://github.com/taw/magic-preconstructed-decks-data

This repository contains machine readable decklist data generated from:

https://github.com/taw/magic-preconstructed-decks

https://github.com/taw/magic-search-engine

Files

decks.json has traditional cards + sideboard structure, with commanders reusing sideboard.

decks_v2.json has cards + sideboard + commander structure. You should use this one.

Data format

Data file i a JSON array, with every element representing one deck.

Fields for each deck:

name - deck name

type - deck type

set_code - mtgjson set code

set_name - set name

release_date - deck release date (many decks are released much after their set)

cards - list of cards in the deck's mainboard

sideboard - list of cards in the deck's sideboard

commander - any commanders deck has (can be multiple for partners)

Each card is:

name - card name

set_code - mtgjson set card is from (decks often have cards from multiple sets)

number - card collector number

foil - is this a foil version

count - how many of given card

mtgjson_uuid - mtgjson uuid

multiverseid - Gatherer multiverseid of card if cards is on Gatherer (optional field)

Data Limitations

All precons ever released by Wizards of the Coast should be present, and decklists should always contain right cards, with correct number and foiling, and mainboard/sideboard/commander status.

Source decklists generally do not say which printing (set and card number) each card is from, so we need to use heuristics to figure that out.

We use a script to infer most likely set for each card based on some heuristics, and as far as I know, it always matches perfectly.

That just leaves situation where there are multiple printings of same card in same set.

If some of the printings are special (full art basics, Jumpstart basics, showcase frames etc.), these have been manually chosen to match every product.

If you see any errors for anything mentioned above, please report them, so they can be fixed.

That just leaves the case of multiple non-special printings of same card in same set - most commonly basic lands. In such case one of them is chosen arbitrarily, even though in reality a core set deck with 16 Forests would likely have 4 of each Forest in that core set, not 16 of one of them.

Feel free to create issue with data on exact priting if you want, but realistically we'll never get them all, and it's not something most people care about much.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Here are step-by-step instructions to migrate decks_v2.json to .dck files with the desired structure, assuming no prior knowledge of the command line:

Open a web browser and go to the following link: https://github.com/taw/magic-preconstructed-decks
Click the green "Code" button and select "Download ZIP" to download the repository as a ZIP file.
Extract the ZIP file to a folder on your computer.
Open the folder and create a new file migrate_decks.py.
Right-click on the file and select "Open With" and then choose a text editor such as Notepad or Sublime Text.
Copy the following Python script and paste it into the text editor:

import json
import os
import re

from typing import List, Dict

DECKS_FOLDER = 'Preconstructed Decks'

def load_decks(file_path: str) -> List[Dict]:
    with open(file_path, 'r') as f:
        return json.load(f)

def format_deck_name(name: str) -> str:
    name = name.lower().replace(' ', '_').replace('-', '_')
    return re.sub(r'[^a-z0-9_]', '', name)

def get_deck_info(deck: Dict) -> Dict:
    return {
        'name': format_deck_name(deck['name']),
        'type': deck['type'],
        'set_code': deck['set_code'].upper(),
        'set_name': deck['set_name'],
        'release_date': deck['release_date'],
        'deck_folder': DECKS_FOLDER,
        'cards': deck['cards'],
        'sideboard': deck['sideboard']
    }

def build_deck_text(deck_info: Dict) -> str:
    lines = [
        f'// {deck_info["name"]}',
        f'// Set: {deck_info["set_name"]} ({deck_info["set_code"]})',
        f'// Release Date: {deck_info["release_date"]}',
        '',
    ]

    for card in deck_info['cards']:
        lines.append(f'{card["count"]} [{card["set_code"]}:{card["number"]}] {card["name"]}')

    lines.append('')
    lines.append('SB:')

    for card in deck_info['sideboard']:
        lines.append(f'{card["count"]} [{card["set_code"]}:{card["number"]}] {card["name"]}')

    return '\n'.join(lines)

def build_deck_path(deck_info: Dict) -> str:
    return os.path.join(deck_info['deck_folder'],
                        deck_info['type'],
                        deck_info['set_code'])

def write_deck_file(deck_info: Dict, deck_text: str) -> None:
    deck_path = build_deck_path(deck_info)
    os.makedirs(deck_path, exist_ok=True)

    filename = f"{deck_info['name']}.dck"
    file_path = os.path.join(deck_path, filename)

    with open(file_path, 'w') as f:
        f.write(deck_text)

def migrate_decks(input_file: str, error_file: str) -> None:
    decks = load_decks(input_file)

    error_decks: List[Dict] = []
    for deck in decks:
        try:
            deck_info = get_deck_info(deck)
            deck_text = build_deck_text(deck_info)
            write_deck_file(deck_info, deck_text)
        except KeyError:
            error_decks.append(deck)

    if error_decks:
        with open(error_file, 'w') as f:
            json.dump(error_decks, f)

if __name__ == '__main__':
    migrate_decks('decks_v2.json', 'error_decks.json')

Open a terminal or command prompt on your computer. On Windows, you can do this by pressing the Windows key and typing "cmd" and then pressing Enter.
Navigate to the folder where the decks_v2.json file and the migrate_decks.py file are located. You can do this by typing cd followed by the path to the folder, such as cd C:\Users\YourName\Downloads\magic-preconstructed-decks-master.
Type python migrate_decks.py and press Enter to run the Python script.
Wait for the script to finish running. It will create a .dck file for each deck in the decks_v2.json file, with the desired structure.

Note: If you don't have Python installed on your computer, you can download it from the official website: https://www.python.org/downloads/. Choose the latest version for your operating system and follow the installation instructions.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

tappedout exports as csv with set information:

.csv
Board,Qty,Name,Printing,Foil,Alter,Signed,Condition,Language
main,1,Beacon Bolt,GRN,,,,,

.dck
1 [GRN:?] Beacon Bolt

Here is a Python script that reads the .csv file and writes the required format to a .dck file. This script uses the csv module to read the .csv file and write to the .dck file.

import csv

def read_csv_file(file_path):
    with open(file_path, 'r') as file:
        return list(csv.reader(file))

def write_to_dck_file(file_path, data):
    with open(file_path, 'w') as file:
        file.writelines(data)

def convert_csv_to_dck_format(csv_data):
    csv_header, *csv_rows = csv_data
    return [format_dck_line(row) for row in csv_rows]

def format_dck_line(row):
    quantity, name, printing = row[1], row[2], row[3]
    return f"{quantity} [{printing}:?] {name}\n"

csv_data = read_csv_file('input.csv')
dck_data = convert_csv_to_dck_format(csv_data)
write_to_dck_file('output.dck', dck_data)

This script works as follows:

It opens the .csv file in read mode.
It creates a csv reader object to read the .csv file.
It skips the header row using the next() function.
It opens the .dck file in write mode.
For each row in the .csv file, it formats the line as per the .dck file format. The format is "Quantity [Printing:?] Name". Here, Quantity is the second column in the .csv file, Printing is the fourth column, and Name is the third column.
It writes the formatted line to the .dck file.

Please replace 'input.csv' with the path to your .csv file and 'output.dck' with the path where you want to create the .dck file. Run this script in a Python environment, and it will create the .dck file with the required format.

[–] [email protected] 1 points 1 year ago

You can either go here https://mtg.wtf/deck Or the same data is also exported to mtgjson if you want it in JSON format https://mtgjson.com/ The same data is also available in a few other export formats.

Source data for it is in https://github.com/taw/magic-preconstructed-decks with source URLs for every deck (some of these expired by now and you'd need to go to the Web Archive - WotC redesigns its website every few years, killing old URLs).

Inferring exact set and collector number based on all available information is done algorithmically.

Everything should have correct names, quantities, and set codes.

A few cards won't have correct collector numbers. The list of cards which are generally expected to not have exact collector number: "Plains", "Island", "Swamp", "Mountain", "Forest", "Wastes", "Azorius Guildgate", "Boros Guildgate", "Dimir Guildgate", "Golgari Guildgate", "Gruul Guildgate", "Izzet Guildgate", "Orzhov Guildgate", "Rakdos Guildgate", "Selesnya Guildgate", "Simic Guildgate"

For everything else, the algorithm is exact as far as we know. Anything the algorithm can't detect automatically it flags, and we resolve it manually.

— Tomasz Wegrzanowski

I noticed that the default deck download format on the website doesn't include set code and collector number information.

If you're fine with JSON, you can use mtgjson, or this file: https://raw.githubusercontent.com/taw/magic-preconstructed-decks-data/master/decks_v2.json (which is exported to mtgjson).

In case it matters, collector numbers are Gatherer-style not Scryfall-style (so DFCs are 123a / 123b, not 123 etc.). This only really affects cards with multiple parts.

Do you have any more questions?

— Tomasz Wegrzanowski

[–] [email protected] 1 points 1 year ago

Manabox has a list of all precon lists and exports in "n cardname (set)set#" format

[–] [email protected] 1 points 1 week ago

Forge not only has all the decks with their original printings but also has the capability to play against the AI.

[–] [email protected] 1 points 1 year ago

https://github.com/taw/mtg

mtg

Magic the Gathering scripts.

scripts

analyze_deck_colors - reports colors of the deck according to correct algorithm [ http://t-a-w.blogspot.com/2013/03/simple-and-correct-algorithm-for.html ]

clean_up_decklist - clean up manually created decklist

cod2dck - convert Cockatrice's .cod to XMage's .dck

cod2txt - convert Cockatrice's .cod to .txt format

txt2cod - convert plaintext deck formats to Cockatrice's cod

txt2dck - convert plaintext deck format to XMage

txt2txt - convert plaintext deck format to plaintext deck format (i.e. normalize the decklist)

url2cod - download decklists from URL and convert to .cod (a few popular websites supported)

url2dck - download decklists from URL and convert to XMage .dck format

url2txt - download decklists from URL and convert to .txt format

data management

These are used to generate data in data/, you probably won't need to run them yourself

generate_colors_tsv_mtgjson - generate data/colors.tsv from mtgjson's AllSets-x.json (recommended)

generate_colors_tsv_cockatrice - generate data/colors.tsv from cockatrice's cards.xml (use mtgjson instead)

mage_card_map_generator - generate data/mage_cards.txt

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

You can download the .txt file for each decklist from MTGGoldfish by clicking on the "Download > Exact Card Versions (Tabletop)" button. However, please note that these files may not be compatible with Xmage due to differences in formatting. Nonetheless, creating a conversion script should not be too difficult.