How to alter CMC on cards?
TappedOut forum
Posted on Dec. 13, 2017, 5:27 p.m. by mustekala
hey, a possibly frequently asked question, but I could not find an answer.
when adding my deck to tappedout, I really appreciate the statistics and diagrams, but is there a way to correct the cmc on various cards?like, for example, in my deck I have several really expensive green creatures that cycles for one or two colorless mana, and in my deck , I never cast these cards, always only cycle them.
the average cmc and colour allocation is not accurate for my deck, since those green big expensive cards gives the deck way too much green, and way too high cmc, than what the deck actually requires.
is there a way to alter this in tappedout.net? so that these green big creatures instead just cost "1" or "2", not 4GGG, for example...
I too have this problem with my monoblack Reanimator deck. I have off color big creatures that I physically cannot cast but rather get cycled and reanimated. I appreciate you bringing it up
December 13, 2017 8:34 p.m.
landofMordor says... #4
If it's a deckbuilding issue, it's not too hard to calculate an adjusted CMC. Simply add the "effective CMC" of all your spells (1 or 2 in your example), then divide by total number of spells. Just don't account for your lands.
On the other hand, if it's an aesthetics issue...math can't help you with that :/
December 13, 2017 10:43 p.m.
yup, the issue is not about not being able to calculate average cmc myself, the issue is about handy stats and graphs at tappedout not being "accurate" according to how certain spells are cast (ie, not using their cmc, but their cycling cost), which of course is no big deal in the scope of world problems.
I see that this funcion is not yet available. thanks for the replies!
December 14, 2017 2:07 p.m.
Do you mind telling me how? :D I can't find that information.
May 26, 2021 4:36 p.m.
Ah I found it. Add *CMC:20* after the card name.
Sorry for double post, I post this in case someone else searches for this info. :)
yeaGO says... #2
this is on the feature roadmap, but we haven't got to it yet.
December 13, 2017 8:20 p.m.