| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
|
CardName: Temporary set, before allowing set creation Cost: Type: Pow/Tgh: / Rules Text: Might be more toruble than it's worth - but since you often are saying "Hey; don't create a new set!" - why not have no 2Create a set" link until you've created several cards (but a "Create a card" link instead, which takes you to a 'holding' set) - and then once you've created, say, five, offer up a "Create a set (and move your cards into it)" link. Flavour Text: Set/Rarity: Multiverse Feedback None Might be more toruble than it's worth – but since you often are saying "Hey; don't create a new set!" – why not have no 2Create a set" link until you've created several cards (but a "Create a card" link instead, which takes you to a 'holding' set) – and then once you've created, say, five, offer up a "Create a set (and move your cards into it)" link.
|
History: [-] Add your comments: |
I might have suggested this before, but maybe a more explicit landing page with sections for:
It's also the case that what people often want to do is create a bunch of cards which are related somehow. I don't suggest it urgently, but I wonder if it would helpful to have some way of defining subsets (of complete cardsets or cards with no home), eg. "cards related to such-and-such a mechanical theme", "cards designed by X", "cards from shard Y", "cards inspired by Batman characters", etc, etc. Obviously you could do that with details pages, but if the interface urged people towards it, it might allow what they want without creating a separate cardset.
Alternatively, just add a "cardset type" for "cardset" and "staging area", and have only cardsets show up on the front page?
My hope is that "Special" cardsets on front page ought to alleviate a lot of this, yeah. (Which is actually implemented at home already, just pending me getting my connection to Heroku sorted out.)
Maybe I'm crazy but a way to have set files that have both "locked cards" (i.e. cards "in" the set) and cards "in design" that are not "officially" part of the set would do something similar and avoid designers needing to have multiple card sets for every set. Skeletons already provide a simple way to assign cards to a set, too.
That's what the "active" status is meant to be used for. Although I agree giving a card a code from a skeleton is rather similar to setting its active status to true, not everybody wants to use skeletons.
"not everybody wants to use skeletons." I noticed. I was making sets where I needed codes, but a skeleton was out of the question because card code represented chronological events, and the skeleton generates "wrong" card codes for that.
You could always generate just one or two lines of the skeleton, and then just edit it to link to whatever codes you wanted. Or equivalently generate a large skeleton, then delete most of it. After you generate it, a skeleton is just a details page with a little bit of extra shiny formatting.
implemented something similar a while ago for new users