Multiverse Feedback

Multiverse Feedback by Alex

275 cards in Multiverse

168 with no rarity, 96 commons, 3 uncommons,
2 rares, 6 mythics

1 colourless green, 38 white, 59 blue, 2 black, 42 red,
88 green, 2 multicolour, 3 hybrid, 38 artifact, 2 land

960 comments total

Report bugs and discuss ideas for new features here

Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity
Mechanics | Upcoming releases | Skeleton

This is not a conventional set of cards. Instead this is where to track bugs and upcoming features in Multiverse.

If you want to report a bug or suggest a feature, click New card above!

You can use the colour/frame of the "card" to indicate what type of issue you're creating:

Please comment on suggestions if they matter to you. If you see a proposal that you like, add a comment saying you want it. Alex is far more likely to add a feature if lots of people want it!

Cardset comments (10) | Add a comment on this cardset

The set creator would like to draw your attention to these comments:

On Version Control (reply):

Mmm. Yeah, this is a sensible topic to raise. Back when I was on a free database, I was confident I wouldn't have space for previous revisions. However now that I'm paying for the database, we've got a good amount of space, so storing previous revisions is a fairly plausible enhancement.

It wouldn't be insanely difficult, but it would be a moderate amount of work; however it's a very sensible thing to ask for. No promises, but I'll look into it further.

On Bugs importing from CSV (reply):

In theory I could directly import MSE files rather than making people have to export. I'm getting a bit more time in the evenings now than I was a couple of months ago so I could have a go at that myself. I've got a good sample MSE set I can be using.

On Card history (reply):

Mmm. Yeah. For a long time this was a feature which I knew would be nice but I was imagining would never happen, because the database space required is at least an order of magnitude greater than for Multiverse's current implementation. In particular, this would make my database size expand past the limit of Heroku's free hosting plan.

But that was quite a number of months ago. And, erm, the database is already four times the size that Heroku supposedly limit their free hosting plan to, and I haven't been charged or run up against any database size limits. So perhaps I could give this a try.

It's possible it might precipitate the inevitable move to paid-for hosting, at which point I probably would stick up a Paypal Donate button somewhere on the site. And I quite like not being at that state yet.

Recently active cards: (all recent activity)

 
There's a notable rise in CPU usage when viewing a set's visual spoiler page that has a lot of links to images (as if they were gif animations or something).
1 comment
2017-03-25 16:31:52 by Tahazzar
 C 
Feature
Allow us to specify small symbols/icons to be included on cards. If we were creating our own mana symbols like snow {s} or Phyrexian mana {pw}, at the moment we couldn't have those images display on cards at all.
10 comments
last 2017-03-22 21:00:08 by Alex
Bug
Mana symbols do not work like word characters with regard to line breaks.

(read comments for details)
4 comments
last 2017-03-15 16:47:54 by Alex
 
I don't know where the conention comes from; MTGO or somewhere else – but people keep entering 'existing cardname*' to indicate a reprint. may as well do something with it – initial comment linking to original card maybe hide the star?
9 comments
last 2017-03-15 16:17:17 by Vitenka
 
Especially Purple
12 comments
last 2017-03-14 12:59:29 by Jack V

Recent comments: (all recent activity)
On Constant CPU usage on visual spoiler page:

Example: http://www.magicmultiverse.net/cardsets/2161/visualspoiler

A quick timeline recording seems to suggest the browser/scripts keep (re)painting something. Only happens if you have linked to card images (and you keep viewing the page) so it likely has something to do with them.

Btw, is this more of a {r} or {b} issue?

On Allow Custom Symbols:

Hmmm. I have a feeling I had a reason why I didn't allow Markdown in card texts, all those years ago when I first designed the site. But I've since added *italic* and **bold**, so the main difference would be hyperlinks in card text. Which seem odd, but on the other hand I'm happy to allow animated GIFs as card images. So... yes, there might be some sense in just allowing full Markdown parsing in card text. I'll have to give it some thought.

On Allow Custom Symbols:

A simple (temporary?) solution would be to allow markdown in card text - including images: gold

On Line Breaks around Mana Symbols:

Ah, I see. Linebreaks after "(" and before "{?}", or after "{b}" and before ".)". Mm, that's not very desirable.

The fix... isn't very easy, I fear. I'd need to detect clusters of word-characters-and-images and wrap them in <nobr> or similar. That part of the code is rather fiddly, and also fairly performance-critical because it gets evaluated every time the card is displayed. (There's an argument that I should store the formatted HTMLified text alongside the raw text in the database, updated at write time, so I don't need to calculate all the substitutions at read time. But that refactoring would itself be a bit of work.)

I'll see if I can find a sensible fix, or time to do it the proper way. No promises though.

On Support * cardnames:

That latter can be done by pasting in the appropriate URL for a full-card image. But yeah, automating it might be nice.

Or at least a skeleton checkbox "Yes, basic lands are wanted, kthx"

On Support * cardnames:

kauefr casts Reanimate Thread.

I'd really like for an official way to insert reprints in our sets, with some kind of checkbox. Maybe even diplaying the card image from gatherer instead of the usual custom render.

On Line Breaks around Mana Symbols:
  • Screenshot
  • Firefox (though the bug can be recreated in Chrome by changing the zoom level)
  • Windows 7
On Line Breaks around Mana Symbols:

Please post a screenshot when you're reporting a bug with how something's displayed, and also report your browser and OS. For me (Windows 7, Chrome) both the mouseover preview of Glacial Bat and the view of it on the card's page itself both appear correct: in the preview "({?}" starts the reminder text at the end of one line, with the next line start "can be paid", which seems legitimate typesetting. If you disagree, please tell me exactly what you'd want to see and why.

It's never going to be possibly to manipulate HTML into desktop publishing-worthy typesetting. Multiverse isn't trying to do perfect beautiful line formatting, though I'm happy to make tweaks if there's a sensible simple fix.

On Line Breaks around Mana Symbols:

Mana symbols do not work like characters with line breaks e. g. if your reminder text starts with a paranthesis (e. g. cycling) your "(" can be orphaned on a line with the symbol and the rest of the reminder text on the next line.

The same is true for mana symbols at the end of reminder text allowing line breaks right afterwards even if they are only followed by ".)"

Use of nonbreaking chracters does not fix that behavior (tested with non-breaking space (U+00A0) and zero-width non-breaking space (U+FEFF)).

~~~

BUG example: Glacial Bat (click link; occurs in version concurrent with this post - might change in the future)

On Alternate Colored Mana and Frame:

Ooh, I hadn't thought of using unicode symbols, that's a good idea. Although it would be a lot nicer if normal text displayed the same size as the mana cost (or if non-mana symbol text in the mana box made the whole thing display as text, not symbols).

I think I suggested it before, but it would be really nice to get just three or four more symbols like {?}, so you can use different ones if needed[1].

Having user-customisable ones would be a bonus, but harder to implement and more rarely really needed.

[1] And I think this is just me, but I happen to dislike {?} because to me it looks like {x}, an unspecified cost, not just a new symbol.

(All recent activity)
See other cardsets