Multiverse Feedback
Multiverse Feedback by Alex
336 cards in Multiverse
226 with no rarity, 96 commons, 3 uncommons,
3 rares, 6 mythics, 2 basics
1 colourless green, 3 colourless, 43 white, 69 blue, 2 black, 44 red,
117 green, 5 multicolour, 4 hybrid, 46 artifact, 2 land
1185 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:
BLACK for security or privacy issues or other "evilness"
RED for bugs of any other kind
WHITE for user interface suggestions, making it easier to do things you already can do
BLUE for feature suggestions, allowing you to do things you can't already do- When an issue is completed, it'll become
GREEN. - If an issue is not a bug, is unreproducible, or a duplicate of another record, it will be marked as ARTIFACT.
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 (12) | Add a comment on this cardset
The set creator would like to draw your attention to these comments:
|
On Version Control (reply):
on 19 Feb 2016
by
Alex:
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):
on 18 Jun 2015
by
Alex:
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):
on 25 Feb 2012
by
Alex:
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)
It can be hard sometimes to have user-to-user conversations on Multiverse, which is more oriented towards user-to-card or user-to-cardset communication. Are there any plans to enable messaging users directly, friend systems, etc.? It's not a huge issues now given the size of the site but it's a nice-to-have.
Ensure also that any new features of cards that are added can work with import and export too, please.
I think that allowing you to write on your user page can be helpful, in case you want to mention different communications, e.g. email (for private messages), NNTP (for public messages), etc. This is possible in a card set page already, but not in the user page.
It is possible to render it server side, perhaps by using the same part of the software that renders it on the web browser (I have seen things containing automated screenshots of HTML documents before, so I would think that it is probably possible).
Rendering on the client side is also possible. This seems to be the element(s) with the ".cardborder" CSS selector. If a browser extension can make screenshots based on CSS selectors, whether or not they are in view, then this can help, I suppose. (I don't know if there is any.)
An alternative is to use external programs to render the cards However, MSE doesn't import (unless they changed that recently and I am unaware), and TeXnicard doesn't currently include any rendering templates for Magic: the Gathering.
Argh. Wow. I guess my Markdown library has got tweaked? That's really weird.
Should be indented:
> Indented text intended here.
Related: when I hit the site via HTTPS, everything mostly works except the on-hover card previews from the skeleton. I get "Blocked loading mixed active content" in the console. I suspect all that's needed to fix this is to make sure that XHR requests use the same protocol as the page was loaded under. In HTML you can usually write links in the form "://www.magicmultiverse.net/path/to/page" (omitting the leading "http" or "https") and the browser will do the right thing both ways. I'm not sure about JavaScript.
The "Special Details Pages" ComboBox also doesn't work properly: It fails to insert the special title into the appropriate text field (the title is left blank).
I came across this trying to create a new Front Page.
Marking a post as adressed/unadressed or highlighting them doesn't show the change in status immediately, a manual refresh of the page is needed.
(You tell us if yu prefer filing separate bug reports, right?)
The totals for rarity and color/s item are now shown on the page where one generates a set skeleton.
Yikes! No, I wasn't aware of that - though I was aware of intermittent caching problems on the individual cardset recent changes pages. Thanks for the heads up: I'll look into it.