Multiverse Feedback

Multiverse Feedback by Alex

268 cards in Multiverse

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

1 colourless green, 38 white, 61 blue, 2 black, 37 red,
88 green, 1 multicolour, 3 hybrid, 35 artifact, 2 land

932 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)

 
Would be nice if it were a set option to stop other people putting images, either off-site or on-site, in the comments on a card. They can be very flow-disrupting.

Optionally allow set admins to do it, but not other people.

In no way vital, just an idea that I'm not even sure I'd actually toggle on.
1 comment
2017-01-18 10:50:09 by Jack V
3 comments
last 2017-01-16 00:58:26 by Alex
 
The card frame doesn't stay in a fixed place, and continues to float down screen.
10 comments
last 2017-01-08 10:09:49 by Alex
 
Can an "edit this card" link be added next to "Link to this card"? Currently you can only edit starting from the cardlist page or the card's individual page. This would make working from the Skeleton/visual spoiler a lo easier.
2 comments
last 2016-12-06 15:39:34 by Circeus
 
Make reorganizing the skeleton easier
2 comments
last 2016-12-06 10:55:58 by Alex

Recent comments: (all recent activity)
On Disallow images in comments:

Or maybe just double-bracket card names? I do always find this a little annoying, and it seems like most of the time it's not for an actual image (which would be ok) it's that someone used double instead of triple bracket by accident.

On Granting Admin Status to Specific Users:

Yeah, this isn't new. See Grant Admin to Individuals, Multiple cardset admins, Admin list, Selective cardset administrator...

I mean, yes, it's something I'd definitely like to allow. I just haven't had time.

On Granting Admin Status to Specific Users:

Plenty of times proper access rights have been asked for.

It's not been a problem for the open sets so far. (Though better "What it as previously" on 'a card has been edited') would be nice, just in case.

On Granting Admin Status to Specific Users:

Copied from the card Dispersal Coup.

"@Alex, but isn't everyone admins? The only way I could find that allowed my friends to work on the set is if I opened the set wide open, making everyone admins and allowing anyone to do everything. If I could assign certain usernames as admins then I might be able to work some proper permissions. As it stands now, you can only set admins to be: Myself (useless if I want others to help), Everyone (Scary because anyone could mess up our designs) or signed in users (so... pretty much everyone?). Why can't I select specific people to be admins?"

On Frame Won't Stay Put:

"the bottom part of the card is often out of view"? Uh... just how small is your screen size?

But yes, I agree I could redesign the card view to use something like flex-box or multiple columns.

On Frame Won't Stay Put:

Fixed elements are bad idea in general and 90% of the time poorly executed and disrupts the flow of the document, including this site. The only things you would fix are backgrounds.

Moreover the bottom part of the card is often out of view and theres no way to see it because fixed position means scrolling has no effect to see the rest.

The other problem with your current setup is why isnt the comment section resized so that the card doesnt overlap the comments. The comments still take the entire width of the screen, but obviously the fixed card obstructs them.

The better solution is to set the card section and comments section as 2 columns next to each other, with certain heights relative to the screen size. Each section can be set in CSS to overflow:auto that adds scrollbars when necessary. This layout works without javascript and any screen size, and insures the card never overlaps the comments. Both sections can be scrolled individually so the whole of it can be read.

On Frame Won't Stay Put:

Huh; note that for me - the card doesn't stay in a fixed position; it's nailed to the canvas like any other element. On desktop, I mean. It never occured to me it would be any other way. Why would it be any other way?

But; um, if you really want it to not scroll; it's fairly plainly a case for frames; not CSS.

On Frame Won't Stay Put:

The fixed card position (on desktop) is most noticeably useful on long discussion threads, especially for cards that have been edited several times or that have complex wording people are discussing. It's a pain to have to keep scrolling up to see what people are referring to.

On mobile, something has to give, and condensing horizontal elements to be concatenated vertically is standard practice.

The problem is that there isn't a good way to detect "on mobile", or even really to define what it means. New mobile devices with bigger screens keep coming out all the time - or even ones with more pixels but not bigger screens, which are even more of a pain. Responsive web design is hard; almost everyone agrees with that. And it's the kind of thing some web developers spend their entire day job trying to keep up with industry trends. For a hobbyist like me, it's just not practical. (My day job does touch on HTML/JS/CSS sometimes, but it's not a major focus.) I've tried to code the site so make things degrade gracefully, but it looks like that's not quite working right in this case... so yes, I'm going to tweak my hard-coded sizes, because nobody has a more sensible way of making CSS detect what counts as mobile than that.

On Frame Won't Stay Put:

I know that Link and I think Vitenka sometimes respond by phone. And those two are, like, 10% of the total audience right there. I presume that paying attention to mobile is just good business.

That said, I got to admit that if the card didn't scroll down with the comments, it wouldn't occur to me that there was something 'wrong' with that. The card image in Gatherer doesn't do that, for example, and that never bothered me. It's a nice feature. I hope the occasions where it causes a problem are minimal, but I wouldn't know.

On Frame Won't Stay Put:

Fixing the card in place is a pain in general. Your solution is using more guesswork and hard coded sizes? Moreover the other elements are not resized, so the fixed card still blocks them when scrolling down the page.

Hardly bother to visit on mobile devices.

(All recent activity)
See other cardsets