Hey there,
If you're tired of having the 20 minutes leading up to Round 1 of your RCQ be nothing but panicking players looking for pen and paper, asking if you can print their decklist or if they can just send it to your on discord, then look no further!
I've put together this website: https://decklist.lol/
Create a tournament, and it'll provide you with a link and QR code your players can use to submit their decklist for your next constructed competitive event. It's like deck checking with Melee, only better because it actually works properly on your phone.
It's free and the only personal information stored is whatever name the player choose to provide on the decklist they submit. No emails or passwords are stored on the server.
The domain name might be silly, but it's very easy to remember, which is why I picked it.
Edited Jonas Swiatek (May 20, 2025 06:55:19 PM)
Very cool idea! I spend some time playing around, and it is quite intuitive. Great work!
Some notes:
Originally posted by Joaquin Azcarate:
Very cool idea! I spend some time playing around, and it is quite intuitive. Great work!
Some notes:
- Verification emails are flagged as Spam (in Gmail at least. Likely due to no DMARC Record, and your DKIM signature being for amazonses)
- Let the users submit unknown cards. Otherwise you will be playing an updating game when new collections drop.
- "Commander" being the format default makes me unreasonably angry 😅
- When submitting a decklist, the name is optional, but in "my decks" the name is required. This is annoying when I try to import. Consider having a default name like using the event name
- You are missing a 1rem spacing between the Add Judge and the table
- Change the Vite favicon logo 😒
Thanks for the feedback!
About feedback point 4, it does work as intended. The player must provide their own name for the purpose of the decklist. Adding the "Deck Name" (like Boros Energy, Mono Red Aggro), is really just there in case people wanna voluntarily provide it for TOs that wanna run some sort of meta game rundown after the tournament.
Edit: I think I just realised that you mean when importing FROM an existing event into "My Decks", instead of the other way around. Yes, sure! I can default the name to the event the deck was imported from.
Edited Jonas Swiatek (May 21, 2025 07:59:30 PM)
Originally posted by Jonas Swiatek:
Hey there,
If you're tired of having the 20 minutes leading up to Round 1 of your RCQ be nothing but panicking players looking for pen and paper, asking if you can print their decklist or if they can just send it to your on discord, then look no further!
I've put together this website: https://decklist.lol/
Create a tournament, and it'll provide you with a link and QR code your players can use to submit their decklist for your next constructed competitive event. It's like deck checking with Melee, only better because it actually works properly on your phone.
It's free and the only personal information stored is whatever name the player choose to provide on the decklist they submit. No emails or passwords are stored on the server.
The domain name might be silly, but it's very easy to remember, which is why I picked it.
Hi!
Amazing tool! I just have a piece of feedback that came across while testing.
Since after lists are locked, and only the TO has permission to edit, would it be possible to display the changes done or a "log" of some sort?
Thank you!
Hi!
Amazing tool! I just have a piece of feedback that came across while testing.
Since after lists are locked, and only the TO has permission to edit, would it be possible to display the changes done or a "log" of some sort?
Thank you!
Thank you! Yeah it's on my list of stuff I wanna get in there. It's going to take a bit of data remodelling so it's kinda pending me getting that done, and I've been busy doing the Tournament Timers feature that's available in the Tools menu.
But I plan on there simply being a drop down where both the judge and the players can see revisions of the decklist, so if the player or a judge modifies it, there will be a paper trail of it.
Jonas, well done and thank you for providing this tool. It is genuinely fantastic.
You may want to adjust the data validation or field parameters for the date field when creating events. I was able to input years with up to 6 digits, however I got a validation error for anything over 4 digits. With than slight bit of clunk as well as being prevented from going more than 30 days into the future this feels a bit wonky. I was very disappointed to not be able to schedule an event for the year 69420.
I'd humbly suggest two options
1- Allow events to be created arbitrarily far into the future but limit the field to 5 digits. This would allow for funny number. 5 is half way between the current limit and standard date notation so it could be considered a good compromise. Lastly, we all must agree that in the year 99,999 deck list will still be a vital part of in person card gaming. But by the year 100,000 psychic registration will have fully supplanted them.
2 - Keep the 30 day future restriction but limit the year field to the standard 4 digits to smooth the process slightly.
The smallest of detail but I couldn't let it go unreported. Thank you again and I wish you the best for maintaining the tool.
Edited Caleb Bright (May 22, 2025 05:27:13 AM)
Originally posted by Caleb Bright:
Jonas, well done and thank you for providing this tool. It is genuinely fantastic.
You may want to adjust the data validation or field parameters for the date field when creating events. I was able to input years with up to 6 digits, however I got a validation error for anything over 4 digits. With than slight bit of clunk as well as being prevented from going more than 30 days into the future this feels a bit wonky. I was very disappointed to not be able to schedule an event for the year 69420.
I'd humbly suggest two options
1- Allow events to be created arbitrarily far into the future but limit the field to 5 digits. This would allow for funny number. 5 is half way between the current limit and standard date notation so it could be considered a good compromise. Lastly, we all must agree that in the year 99,999 deck list will still be a vital part of in person card gaming. But by the year 100,000 psychic registration will have fully supplanted them.
2 - Keep the 30 day future restriction but limit the year field to the standard 4 digits to smooth the process slightly.
The smallest of detail but I couldn't let it go unreported. Thank you again and I wish you the best for maintaining the tool.
Hi Caleb, and thank you!
I've simply just added the needed attributes to the input field to limit it to 30 days ;) I think the demand for scheduling deck registration for an RCQ in 14500 AD is going to be fairly limited.
The reason for the 30 day limit is that I delete everything related to an event 7 days after the date picked. Less data storage to potentially pay for.
Edited Jonas Swiatek (May 22, 2025 05:46:12 AM)
Originally posted by Andre Santos:
Hi!
Amazing tool! I just have a piece of feedback that came across while testing.
Since after lists are locked, and only the TO has permission to edit, would it be possible to display the changes done or a "log" of some sort?
Thank you!
Hi Andre,
I've added this feature now. Both players and judges can now view revisions made to a decklist. It'll also show if the change is made by the player or by an admin.
Originally posted by Jonas Swiatek:
Originally posted by Andre Santos:
Hi!
Amazing tool! I just have a piece of feedback that came across while testing.
Since after lists are locked, and only the TO has permission to edit, would it be possible to display the changes done or a "log" of some sort?
Thank you!
Hi Andre,
I've added this feature now. Both players and judges can now view revisions made to a decklist. It'll also show if the change is made by the player or by an admin.
Hi!
Amazing! I will check it during this week.
Thank you so much once again for such a great tool.
Hi!
Amazing! I will check it during this week.
Thank you so much once again for such a great tool.
My pleasure. It started out as something I figured we'd just use for our local tournaments here, but it turned out really well. The last two RCQs I've used it with has had zero issues - except players who just can't spell or remember the actual names of magic cards. Such as Damping Sphere vs Dampening Sphere or Visions of Beyond vs. Visions from Beyond.
Unfortunately running a proper Elastic Search instance to offer looser card name matching is going to cost more than I'm willing to pay, so we're currently stuck with exact card name matching, except for some stuff where it'll accept cards without commas and apostrophes. For instance writing "sheoldreds edict" will be accepted as "Sheoldred's Edict".
If someone more skilled at HTML/CSS than me is interested in implementing some sort of UI for card name suggestions, please check out the "Contribute" link at the bottom of the page. I've got everything wired up backend-wise for actually querying it and making suggestions for card names while typing - but it's beyond my skills to make it look remotely useful.
Unfortunately running a proper Elastic Search instance to offer looser card name matching is going to cost more than I'm willing to pay, so we're currently stuck with exact card name matching, except for some stuff where it'll accept cards without commas and apostrophes. For instance writing "sheoldreds edict" will be accepted as "Sheoldred's Edict".
One incidental feature of Deckbox.org that I like is that, when entering card names, it performs substring matching on any part of the card name; it doesn't just match from the start of the card name. Deckbox.org considers punctuation, including spaces, to be significant for this searching. Thus e.g. "ping sph" unqiuely matches "Damping Sphere", and "ed's ed" uniquely matches "Sheoldred's Edict". I use this when cataloguing cards for my inventory, as 99% of the time, just using the few characters around each side of a space in a card name narrows down the results to just one card or a few to select from.
Not sure how useful this would be for players in general, but I thought I'd mention it here.
If someone more skilled at HTML/CSS than me is interested in implementing some sort of UI for card name suggestions, please check out the "Contribute" link at the bottom of the page. I've got everything wired up backend-wise for actually querying it and making suggestions for card names while typing - but it's beyond my skills to make it look remotely useful.
For UI components, I'd recommend taking a look at Material UI. It provides many useful React components, such as for text fields with autocompletion support: https://mui.com/material-ui/react-autocomplete/
You must be registered in order to post to this forum.