I just had a couple of ideas that I think would be useful.
First, an option to automatically fetch/update the Set Codes when a new set comes out.
Every time a new set comes out, users need to look up the set info and manually update the Set Code data.
With this, maybe an option to only update Set Codes with missing data, and also an option to update/overwrite all Set Codes, in case someone entered the wrong information for an existing Set Code.
Second, an option to save by Set ID. I have one massive .csv with almost every set, which I like for creating/updating a massive amount of data from multiple sets.
It's easier than creating/updating the data for one set, saving it, selecting a different set, saving it, etc. It would be helpful if it could parse out all of the data into separate .csv files.
Also, loading in the huge .csv takes a few minutes to load, but if I already have to data for a set, and just want to download the scans, I'd rather just open the .csv for a specific Set Code.
Lastly, maybe an option to select sets by format - Standard, Modern, Commander, etc. Then users could have a file for each format, so they know which sets have rotated out, or so 'Unglued' cards don't show up if the user only wants Commander cards - things like that.
Let me know what you think, or if you have any questions about these suggestions.
Regardless, love the software.
You're right, it does seem to be fixed. If I uncheck 'Booster Packaging' in Options > Export, I only get Nname, Ncode, Ndate, and Nis_promo.
With that optioned checked, I get all of those other fields.
I'll give the new script a spin and see how it goes.
If I run into any problems, or if I think of any other ideas, I'll be sure to let you know.
I've found a number of posts about Changeling/Shapeshifter creature types, but I haven't been able to find anything that states whether a Changeling/Shapeshifter spell is all types.
Here's the scenario...
If I've got 'The First Sliver' on the battlefield, and then I cast 'Irregular Cohort', would that Cascade?
I don't think it would, since it's a 'Shapeshifter', not a 'Sliver' when I cast the spell.
Is that correct?
Using card tags is mandatory in the Magic Rulings forum. Please check your private messages to learn how to use them. I've added them for this post.
-MadMage
Love the application. I've been looking for something like this for ages, so thank you!
However, when I export the data to SQL scripts, the syntax within those scripts isn't quite right.
For example, the 'Nsets' table is created with five fields, but the insert script contains 20 fields, so they fail.
Also, there are a number of cards that contain an apostrophe, which affects the syntax, which also causes the script to fail.
I would love to see these changes implemented in the next release.
I work with SQL on a daily basis, so if there's anything I can do to help with these improvements, please let me know.
I just had a couple of ideas that I think would be useful.
First, an option to automatically fetch/update the Set Codes when a new set comes out.
Every time a new set comes out, users need to look up the set info and manually update the Set Code data.
With this, maybe an option to only update Set Codes with missing data, and also an option to update/overwrite all Set Codes, in case someone entered the wrong information for an existing Set Code.
Second, an option to save by Set ID. I have one massive .csv with almost every set, which I like for creating/updating a massive amount of data from multiple sets.
It's easier than creating/updating the data for one set, saving it, selecting a different set, saving it, etc. It would be helpful if it could parse out all of the data into separate .csv files.
Also, loading in the huge .csv takes a few minutes to load, but if I already have to data for a set, and just want to download the scans, I'd rather just open the .csv for a specific Set Code.
Lastly, maybe an option to select sets by format - Standard, Modern, Commander, etc. Then users could have a file for each format, so they know which sets have rotated out, or so 'Unglued' cards don't show up if the user only wants Commander cards - things like that.
Let me know what you think, or if you have any questions about these suggestions.
Regardless, love the software.
-KD
With that optioned checked, I get all of those other fields.
I'll give the new script a spin and see how it goes.
If I run into any problems, or if I think of any other ideas, I'll be sure to let you know.
Thanks
-KD
Here's the scenario...
If I've got 'The First Sliver' on the battlefield, and then I cast 'Irregular Cohort', would that Cascade?
I don't think it would, since it's a 'Shapeshifter', not a 'Sliver' when I cast the spell.
Is that correct?
Using card tags is mandatory in the Magic Rulings forum. Please check your private messages to learn how to use them. I've added them for this post.
-MadMage
However, when I export the data to SQL scripts, the syntax within those scripts isn't quite right.
For example, the 'Nsets' table is created with five fields, but the insert script contains 20 fields, so they fail.
Also, there are a number of cards that contain an apostrophe, which affects the syntax, which also causes the script to fail.
I would love to see these changes implemented in the next release.
I work with SQL on a daily basis, so if there's anything I can do to help with these improvements, please let me know.