Multiverse Feedback

Multiverse Feedback by Alex

261 cards in Multiverse

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

1 colourless green, 36 white, 59 blue, 2 black, 38 red,
85 green, 1 multicolour, 3 hybrid, 34 artifact, 2 land

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

 C 
Feature
Let us have a nice frame for creatures with level up.
15 comments
last 2016-07-31 21:38:49 by WOM Devign Team
 C 
 
When someone edits a card, they have the ability to comment on their change. I think it would be nice if there was some way to view older editions of a card as well, like on Wikipedia.
That way, you could know what I used to have as flavor text here. ;)
5 comments
last 2016-07-31 21:22:59 by WOM Devign Team
 
It would be nice if entering [Flying], [Battle Cry], or any other Wizards-designed keywords automatically inserted reminder text.
2 comments
last 2016-07-31 21:16:21 by WOM Devign Team
 C 
Feature
It'd be nice if multiple cardsets could share a mechanic. Particularly obvious for several sets in the same block.
4 comments
last 2016-07-31 21:11:41 by WOM Devign Team
 C 
Wishlist
There should be a link where logged-in users can view history of their own recent actions, such as which cards they added or commented on. This would make it simpler for them to find those cards even when the overall recent changes page might not give any indication of where they are.
14 comments
last 2016-07-31 21:04:01 by WOM Devign Team

Recent comments: (all recent activity)
On Level-Up Cards:

Upvote, although your most recent comment is a good workaround.

On Card history:

I think this may be redundant with another comment I made recently, but I can't remember for sure, so I'm posting this one as well.

On Premade Official Keywords:
On Copy mechanics between cardsets:

Upvote.

Right now it looks like there is a sort of set-mechanic pair structure. Maybe you could also have mechanics that were associated with users? So if Bob was making a card for beebleworld, he would have access to beebleworld mechanics and Bob mechanics.

On View Own Action History:
On Accessing Safiria acts like I'm logged out:
On forbidden card move has unhelpful error:

Well, just showing the skeleton row which prevents the move would be very helpful. It wouldn't be half as annoying if edit and move was a possibility. As is, you have to go check for an available card code/delete the code, save the card, then repeat the move, which is frustrating when it happens repeatedly.

I think you should be able to have multiple cards with the same code if there is no skeleton. I'm not sure what is best to do once the skeleton happens. Maybe put an error message in the skeleton instead of a card link?

On forbidden card move has unhelpful error:

Mmm. Interesting. I wonder whether I should go back to allowing duplicate card codes in any given set, in fact.

On Hide mechanic parameters:

No, the feature suggestion is right. At the moment if you specified "join \1 together" as the expansion of the keyword "combine" or anything, and then wrote a card saying "Target player may [combine three target creatures]", you'd like that to expand to "Target player may join three target creatures together", but at the moment it wouldn't - it'd go wrong and expand to say "Target player may join three target creatures together three target creatures".

On Hide mechanic parameters:

Sorry if i'm not understanding this right, but couldn't you just not use the same name for both names?

(All recent activity)
See other cardsets