Great news everyone – the Lemmy CardFetcherBot is now live across all MTGZone communities. We’re still updating it and working on getting running with supervisor on the server, but in the meantime it should be handling all comments and posts on our instance here.
To use it, type card names in this format: [[Card Name]]
, and Cardbot will reply with links to the cards.
If you’d like to help out in anyway, feel free to join in at Github here: https://github.com/mikegioia/lemmy-cardfetcher-bot
Adding issues, sending PRs, anything at all will be helpful!
[[Venture Forth]]
[[Our Market Research Shows That Players Like Really Long Card Names So We Made this Card to Have the Absolute Longest Card Name Ever Elemental]]
[[Verdant Force|TMP]]
- Unable to retrieve information for “Verdant Force|TMP”
[[card name]] to call
We dont support the
|SET
syntax yet[[Verdant Force]]
[[Silvos, Rogue Elemental]]
There’s my boy
[[Fire // Ice]]
[[Start // Finish]]Everything looks good there.
Could you update the sidebar with the github link and maybe a quick usage instruction?
Just updated now, great idea
[[Sarkhan’s Unsealing]]
[[Palantir of Orthanc]]
[[Loopy Lobster]]
still working out some kinks 😅 [[Loopy Lobster]]
- Unable to retrieve information for “Loopy Lobster”
[[card name]] to call
Hmm, let’s try something Standard-legal: [[Chrome Cat]]
That seems good! Is the card list limited to things that are tournament-legal? Loopy Lobster was one of the Mystery Booster playtest cards.
It’s using the Scryfall API, and this is the query we’re making for that card: https://api.scryfall.com/cards/search?q=Loopy+Lobster
I’m not sure why Scryfall can’t find it since they serve the page for it.
All of those playtest cards are excluded, it looks like. I think I found the answer here. This URL will find Loopy Lobster:
https://api.scryfall.com/cards/search?include_extras=1&q=Loopy+Lobster
But the
include_extras
parameter also covers things like tokens and planes which you might reasonably decide you don’t want. Maybe have it re-run the search withinclude_extras
if the initial search without it comes back empty? Or maybe not, since that could significantly increase the number of API calls. I don’t know.