| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
|
CardName: Tags for easily searching themes Cost: Type: Pow/Tgh: / Rules Text: Imagine I have a minitheme without a keyword (because the text isn't consistent, like AVR's "loner" theme). It's awfully hard to keep track of them normally. If you could put tags, like "Loner Monoblack Sacrifice" to indicate it fits the loner theme, that it supports monoblack strategies, and that it supports a sacrifice theme, for example, it would be a lot easier to keep track of the different themes you have. Flavour Text: Of course, this kinda implies the cardlist should have filters already. :P Set/Rarity: Multiverse Feedback Common Imagine I have a minitheme without a keyword (because the text isn't consistent, like AVR's "loner" theme). It's awfully hard to keep track of them normally.
If you could put tags, like "Loner Monoblack Sacrifice" to indicate it fits the loner theme, that it supports monoblack strategies, and that it supports a sacrifice theme, for example, it would be a lot easier to keep track of the different themes you have. Of course, this kinda implies the cardlist should have filters already. :P
|
History: [-] Add your comments: |
Skeleton? Comments?
Yeah, I think the skeleton is probably a reasonable place for this; or there's nothing to stop you inventing a tag ("AVRLonerTheme") that you mention in comments and look for with the advanced search page. When I rework skeleton/cardlist to combine them I'll see if I can find a way to allow this, but I don't think it's really sensible to add some specific field to cards for "tags".
But isn't information on the skeleton indepent of the cards themselves? Or am I using it wrong?
You're right, the skeleton rows are indeed not directly bound to cards. If you change a card's code, that will move the card from one skeleton slot to another. So in that sense it's independent of cards.
Sure. Tags in comments is a little messier (and a bit confusing if you add tags at different times), and you have to wait until you make the card to comment.
If tags aren't sensible, a field for card comments (a single field that can be changed and always appears under the card, for example) should do it. Might also fix the problem people have with trying to make card rulings?
Hmm. There is somewhat of a fuzzy spectrum between tags, rulings, design notes and comments. But yes, I could do something along these lines.
Cool. :)