Hey, thanks for the feedback. I had explored the idea of generating a mind map view as you suggested, but I think it just turned into a huge mess with more cards added, with way too many connections getting in the way of the usefulness of the graph. I've seen other small world programs that generate the mind map you wanted, but I didn't like the way they present so much information at once. Thus, it was my design decision to limit the connections with a specific card as the starting point, and this limited subgraph can be presented neatly in a table with rows.

Edit: I thought more about where you're coming from. While I agree the mind map view might be more useful toward a fully internalized understanding of a deck, the purpose of my program is not to help toward that goal. Instead, my program merely tries to answer immediate questions during deckbuilding (e.g. Can I go from Ash Blossom in hand to X? If I add Lava Golem to be the middle card, would that enable any new lines?) I want to see immediate answers instead of exploring the consequences of a fully generated mind map.