Multiverse Feedback

Multiverse Feedback by Alex

278 cards in Multiverse

170 with no rarity, 96 commons, 3 uncommons,
2 rares, 6 mythics, 1 basic

1 colourless green, 37 white, 58 blue, 2 black, 37 red,
97 green, 2 multicolour, 3 hybrid, 39 artifact, 2 land

993 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 (11) | 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)

 C 
 
A way to temporarily turn off symbol expansion to allow OPENBRACKET 1 CLOSEBRACKET as text in comments without it appearing as a mana symbol
13 comments
last 2017-04-19 18:21:14 by Alex
Bug – Software-Degradation
I just get "We're sorry, but something went wrong." message page in every set.

Or is it just me?
3 comments
last 2017-04-19 16:44:09 by Alex
00come
 
Whenever I try to make a comment on a card, it covers the comments.

Can you remove the fixedinner class from cardfixedwrapperinner? That seems to solve the issue.
Illus. aka mproud
4 comments
last 2017-04-19 16:43:48 by Alex
 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.
14 comments
last 2017-04-19 11:55:39 by Jack V
 
It would be nice if entering Flying (This creature can't be blocked except by creatures with flying or reach.), Battle cry (Whenever this creature attacks, each other attacking creature gets +1/+0 until end of turn.), or any other Wizards-designed keywords automatically inserted reminder text.
10 comments
last 2017-04-11 02:34:43 by jmgariepy

Recent comments: (all recent activity)
On Allow (1) in text in comments:

Nope, just removed the () option for mana symbols everywhere; everyone should use {} now. I'll do a database edit to fix up the cards that were using them for mana symbols.

On Allow (1) in text in comments:

(1) (a) (b) awesome!

(Did you leave it an option somehow for people who used it, or just, everyone should use {} not () now? )

On Allow (1) in text in comments:

(1) Is this fixed now?
(2) I hope so.
(3) Yes, it is!

On "Visual spoiler" pages no longer work?:

Should be OK now.

On Card covers comments:

This is fixed for desktop browsers, I think. Mobile fix is still to come.

On "Visual spoiler" pages no longer work?:

Okay, don't sweat it :)

Crap like that is not entirely unexpected when large updates are applied, which btw, are pretty cool so thumbs up.

On "Visual spoiler" pages no longer work?:

Argh. Yep, confirmed. I'm trying to fix this urgently.

On Allow Custom Symbols:

ETA: Yes, that seems to be it. It turns the images into blank images, but doesn't include their title text (which is still there, eg. if i copy it and paste elsewhere). That's a problem with the plugin not this website.

On Allow Custom Symbols:

I'm using a plugin which may not do the right thing; if you like I can check if it works correctly with normal way of disabling images.

On Allow (1) in text in comments:
(All recent activity)
See other cardsets