Search options

I know what you mean. I played in a small tourney one weekend so I built a UB tendrils deck by pulling around 5 cards from 12 other decks. It took forever to rebuild my decks because I couldn't remember what came from where

For that very reason though, the idea of marking a deck built or unbuilt seems wrong to me. In this case, the tendrils deck is the one that is Built, and until I put the cards back the other 12 are really Unbuilt. In a perfect world, the state of the deck is not based on an arbitrary flag, but rather the inclusion (or not) of cards from inventory. Just because you have cards in your inventory does not mean those cards are in a deck, that could be another step. Then a built deck is any deck with all 60 cards allocated from inventory, and an unbuilt deck would have a list of 60 cards but not all are allocated for whatever reason (not available from inventory, or pulled to another deck?). Then you are no longer flipping deck statuses - you are tracking your cards through the decklists.

In my opinion this is three separate requests and map to three phases of development.

Phase 1: Allow cards in inventory to be queried for (your) decks that contain them

Phase 2: Add to the inventory a "Total Used" (in your decks)

Phase 3: Track currently Built/Unbuilt decks, in inventory calculate running total (number that are "Available for Use")

I think the majority of deckbuilders would find 1st to be convenient, a smaller but still large subset would intuitively use the 2nd, and the smallest subset might take full advantage of the 3rd. That being the case, it makes sense to incrementally add the three features. Granted, the 3rd sorta supersedes 2nd, in that you probably would not carry both Total Used and Number Available fields, since it's simple math to determine one from the other...

However even the first phase solves many problems because its hard to click on every one of our decks looking for a certain card until all four (or more) are located.

Me and my shiny new "Deckbox 2 CSV" converter disagree with you.

http://killobyte.com/magic/

I couldn't access your database so I had to write a parser, not just and exporter. Of course I've never seen your codebase, maybe your tools take longer to use. Do you use PHP? In PHP the applicable part for you would be:

public function printCsv() {
        header('Content-Type: text/csv');
        header('Content-Disposition: attachment; filename="Deck.csv"');

        echo 'quantity,name,sideboard'."\r\n";

        foreach ($this->getCardList() as $card) {
            echo '"'.$card['quantity'].'","'.$card['name'].'",""'."\r\n";
        }

        foreach ($this->getSideBoard() as $card) {
            echo '"'.$card['quantity'].'","'.$card['name'].'","YES"'."\r\n";
        }
}

where $this->getCardList() and $this->getSideBoard() return an array of cards.

Anyway, looking forward to seeing what you come up with.

like google docs share feature.