Thoughts about updating the set editor

[mtgrares]

Maybe I'll try to incorporate the set editor into the main project. I think I understand things but let me get it straight. So now all of the cards are in /res/cardsfolder/ as separate files and common.txt, uncommon.txt, rare.txt in /res/draft/ are still being used to draft? It is nice that the rarity is in the individual card files, SVar:Rarity:Uncommon.

It would help me out if the individual card files included the set. I know that friarsol mentioned that he has a Python script ready to go, here.

I should be able to add mythic rares as long as I'm updating stuff. Correct me if I'm wrong but mythic rares appear in 1 out of every 8 packs and replaces the rare card.

[Chris H.]

Maybe I'll try to incorporate the set editor into the main project. I think I understand things but let me get it straight. So now all of the cards are in /res/cardsfolder/ as separate files and common.txt, uncommon.txt, rare.txt in /res/draft/ are still being used to draft? It is nice that the rarity is in the individual card files, SVar:Rarity:Uncommon.

It would help me out if the individual card files included the set. I know that friarsol mentioned that he has a Python script ready to go, here.

I should be able to add mythic rares as long as I'm updating stuff. Correct me if I'm wrong but mythic rares appear in 1 out of every 8 packs and replaces the rare card.

`
I am guessing, but if the set editor was merged into the Forge app then the set editor would also have access to getText and would display the correct info.

Sol mentioned a plan to add set info so I think that it is just a matter of time. He, Rob and Sloth have been busy creating a new system for the keywords and it may take a while before we see the results of the set info project.

[Rob Cashwalker]

Just check out the changes in ReadCard to support the individual files.

Set-rarity and pictures are on the drawing board, but actually using them effectively will require a number of changes. Producing set-specific boosters would be the only need for full Mythic support. I wrote some code to add mythics to the current boosters, but when you consider that our support of mythic cards is very small compared to regular rares, so interpreting them as regular rares is just as effective.

Last we were discussing revising the draft function, we were leaning to a single-file format, instead of common, uncommon and rare. This way the user can have more than one draft pool.

[mtgrares]

You are right, I'm not sure how many mythic rares Forge actually has. And more than likely the number of mythic rares would be way too small to be useful.

[timmermac]

AFAIK, Forge actually has a fairly considerable amount of mythics. I run into them on a pretty regular basis when I'm playing.

[Rob Cashwalker]

timmermac - by regular, do you think it's too often or about right - 1:8? If it's too often, does it make your experience un-fun? Because from my POV, if it's fun to have them as often as you do, then we shouldn't change that.

[juzamjedi]

I include a pretty good number of Mythics in my draft set. If you're referring to draft providing a bunch of mythics that is probably why. Because I like Jace the Mind Sculptor, Baneslayer Angel, etc.

[timmermac]

I usually get a mythic or 2 in every 10 rares that I get, which is just perfect for me. I actually modified the quest.preferences file so that in every booster I get 5 commons, 5 uncommons and 10 rares. Out of the probably 500-600 rares I have so far, less than 10% of them are mythics, so the balancing is working as intended as far as I can tell.