Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
Mechanics | Upcoming releases | Skeleton |
CardName: Find cards I created Cost: {W} Type: Pow/Tgh: / Rules Text: If you're pushing people into making cards inside 'cards with no home' - there needs to be an obvious way for them to find those cards again; and to get comments on them collected in one place etc. If there's a way to do "All my cards in this set" I don't know what it is, and it should be made more obvious. Flavour Text: Set/Rarity: Multiverse Feedback None If you're pushing people into making cards inside 'cards with no home' – there needs to be an obvious way for them to find those cards again; and to get comments on them collected in one place etc. If there's a way to do "All my cards in this set" I don't know what it is, and it should be made more obvious.
|
History: [-] Add your comments: |
Actually; what I think I want to suggest is sub-folders inside a cardset; and for those to have some prominence in recent changes.
Which then makes me wonder what the difference is between that and a cardset (though it'd let you support blocks and other linked sets) - and also what the actual cost is of a cardset, compared to the cards in it?
fixed by My Cards
My idea to support SQL would make this and many other things possible easily. Then, if I want to find all cards I created in all card sets, I could write:
Or, if I only wanted to find all cards I wrote in the "Cards With No Home" card set, then I could write:
Or, if I wanted to find all cards that have any comments that I wrote, among all card sets:
Due to the difficulty, I could not find my other suggestion at this time, although I can mention that it involves a SQLite virtual table, so this server does not need to parse any SQL code itself (therefore avoiding the security issues that would go with that), nor does it need to implement all possible queries (the server would implement all constraints it understands; the rest would be implemented on the client).