Multiverse Feedback: Recent Activity
| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
Recent updates to Multiverse Feedback: (Generated at 2025-09-04 22:41:53)
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.
Heh. I could do that, yes. I think Circeus's approach is a lot simpler though :)
Since you already have flavoured markdown, could you interpret a comment on entry to see if it contains a cross-reference, then store the database ID of the referant, then re-interpret it to the current number of that comment on display?
Did that make sense?
Can't deleted comment simply be replaced by a "comment deleted/hidden" message that maintains numbering? (plus having the kind of notice is helpful if someone somehow answered to a deleted comment).
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.)
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?
Actually, that makes sense. If you've got the ability to make decklists somewhere further down the queue, then that should take priority. My quibbles have more to do with organizing how you're going to print things, and decklists kind of solve 98% of the problem.
Hmm. I did already implement a "printer view" for details pages, deliberately to use them for proxy printing. For example, if you go to something like this details page, there's a subtle link at the top-right saying "Printable". Clicking that ought to take you to a page that's pretty good for printing proxies.
You can create details pages for any cardset you have edit permissions on. Inside them, include the card name in ((double round parentheses)) to embed the coloured card mockup. For example, this Testy details page comes out looking like this. So for example, on Ifreann, you can add details pages with the "Add details page" link in the grey box at the top of each Ifreann page.
Given all of which, I'm not sure there's very much more to do for this feature. Perhaps to let you select cards to print proxies of without having to make a details page first. That will come when I add the "decklist" feature, although that's not going to be very soon.
That would be very cool, Alex. I don't know why I didn't think to use HTML characters myself for alternate symbols, but that makes a lot of sense.
You can, but I got to agree with Pierre... it's tricky. It's also tricky to print out an specific assortment of cards... say four of each common. Doable using the system we have? Definitely. Ideal? Not yet.
You kinda can - if you hit 'booster' or 'visual spoiler'; then choose to print from your browser.
There's some problems with getting them the right size; though.
Hmm. As long as you don't want all the extra versions for hybrid mixes between all of those and all the existing colours, that's plausible. I'm happy to choose 4 shades of orange (frame, pinline, type bar, textbox); I don't want to have to also choose land background and define hundreds of "Hybrid red-purple, Land green-orange, Hybrid yellow-white" kind of options.
For the "mana symbols", I could add just random symbols like ★ ☸ ♦ behind fairly random coloured circles.
(In the meantime, the colourless frame is slightly purply-tinged, because it's Eldrazi-inspired.)
That said, I would appreciate a purple, orange and yellow frame (and maybe gray, silver or brown, if there's a way to make it not look like artifact or lands) for non-Magic related projects I have in my head. I don't have anything in mind right yet... it just seems like a good idea to have the options at the bottom of the frame colour list... especially if it's an easy thing to code.
Having six or seven options for frame color and mana symbol is probably wise... especially for people who want to make a game that isn't quite Magic. I kind of wish there was an easy way to flip on a tab that had a pile of non-standard options... though, I know, practically, that would require a lot more work for such a tangental subject.
I assume the purple frame is easy enough. The purple mana symbol isn't so simple. Alex didn't make the symbols, right? They come from a database... probably belonging to Wizards. If that's the case, this very humble suggestion is tantamount to requesting someone to remake 50 mana symbols... or find a way to add symbols to someone else's database... or... you know, I don't code, but I assume that it's tricky.
But no purple :(
There's
and 
for 'odd' mana symbols.
has apparently gone away
I could provide some things like this. (There are already some very basic stats in the infobox at the top-right of a cardset's front page.)
I think really the details here would be easiest with the cardlist page supporting multiple sorting. Which it currently does, but only on Firefox, in bizarre fashion. So you can already sort a cardlist by "mana cost" (which sorts by CMC) then by "colour" to get all your white cards sorted by CMC, then your blue cards sorted by CMC, etc. (I guess I could provide a nicer interface to this.)
But that said, there's definitely a role for more statistics. "Average number of words" and "Average number of words on commons" are metrics that have been suggested before. I may as well provide these.
This! Please!
I have an idea about presentation - put text below the card, under where the edit button goes now. When you build the page, check the DB for if it is favorited by the user currently logged in. Then if it is, write a string "Favorited" to the page. When you click that string a dialog box pops up giving you the option to unfavorite it. Vice versa for if it's not favorited.
You can give users the access to all their favorites through their user page (even if it is spartan now, you gotta start somewhere). It can be text based with hyperlinks to the card page, or potentially a visual spoiler.
Backend-wise, it's certainly very simple, yes. Presentation-wise is where the effort would be: what does the favourite icon look like when it's checked, when it's not checked, writing the view to show all your currently favourited cards (and finding somewhere to link it from, especially as I don't really have a sensible user profile page at the moment).
But yeah, it's a good idea, and it wouldn't be too much effort.
As for helping out, many thanks for the offer; I am planning to put the source code up on Github so people can make their own changes and send them via pull requests. I've not had much time to work on Multiverse myself recently though.