Multiverse Feedback: Recent Activity
| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
Recent updates to Multiverse Feedback: (Generated at 2025-09-14 06:38:38)
I don't know how much control you need. I have seen a document about random pack generation in Lore Seeker, which lists the following possibilities:
Simulated collation: Make a list of cards (possibly with duplicates), and then cut it at a random point and select cards starting from that point.
Naive algorithm: Pick ten common cards (with no duplicates), three uncommon cards (with no duplicates), and one rare or mythic card (in the list of cards to select from, put rares twice so they are more likely than mythics).
taw's algorithm: Like the naive algorithm but replace five of the ten common slots with color-locked slots; only common monocolored cards of a specific color appear in each slot. This way it is guaranteed to have at least one common card of each color.
Reuben's algorithm: Use the naive algorithm, and then check for the criteria; if they are not met, then try again. The criteria are: at least one and at most four commons of each color, at least one common creature, and at most two uncommons of a color.
Nonbasic land slots: Some sets use a nonbasic land slot instead of a basic slot; there are different weighted probabilities for different rarities.
See MSE documentation about pack types to see what capabilities MSE has.
TeXnicard has a flexible system that supports all of the Lore Seeker possibilities, and more; it also has the possibility to associate a 8-bit "auxiliary value" with each card in the pack (which can be used for whatever purpose you want, such as to indicate shiny cards).
I would expect probably Multiverse would never be flexible enough, although some of the possibilities listed might be implemented, maybe.
I haven't seen Isochron before; I looked and it seems that there is unfortunately no protocol documentation, so would have to be figured out from the source code instead. A reimplementation of both the server side and client side might be made to support use with other software and other operating systems, including more flexible random pack definition. But for using the existing Isochron implementation with programs other than MSE (if you do not need the more flexible random pack definition), the file format that lists the cards seems to be easily enough to do.
In response to comment 59923: It may be helpful, although note that not everyone uses MSE. I use TeXnicard, and I have also heard of Geckos and PrincessEdit, although I do not know much about them (I don't know if they support import/export at all). All four of these programs can render the cards themself, although I think they may have different capabilities and restrictions for doing so. (I actually also don't know if Geckos and PrincessEdit support Magic: the Gathering at all.)
Did you look at the Wikipedia article for CSV? It might help. I also had a problem, but after I read the Wikipedia article about CSV, then I figured out what to do to get it to work. Examine the code of the multiverse-export template in the TeXnicard source repository for an example code.
I wrote a TeXnicard export template for exporting to Multiverse. I intend to make the card set in TeXnicard, and only add a mirror to Multiverse (for the convenience of users who use Multiverse). If there are improvements to that template which could be made, then I hope that it can be done. If you see a bug in my program, you can report that, too.
It is my intention that the output from this export template can then be piped to curl (instead of xclip) in order to do this import.
Also I would hope for better documentation, for how to make adventurer cards, split cards, etc in the import. Maybe it might also be helpful to have a import format that can import other things too, all in one file, so that you can import mechanics and so on as well.
Ugh. I kind of figured that was the case. But Weird Al once told me that it never hurts to ask, and of all the Boomers, I trust Weird Al.
For what it's worth, redirecting off-page seems to be doing rather well. So I'm kind of asking for a solution to a problem that doesn't really exist.
Embedded ugh is even more ugh than off-page ugh.
Ugh.
Hi Alex! This card was more just a general question. Since there wasn't a proper border for that, I figured I'd just make the frame gold.
We've been using polls on Name That Card, and it's been going along great. This has involved sending people to a page where the poll appears. But it would be nicer to embed the poll into the comments section.
There is a script for this. Unfortunately, my knowledge of HTML is limited to what a writer would know, not what a web designer would know. Here, I'm going to copy and paste the script right in this dialogue box:
Obviously, not counting the since that's just there to show the script without it trying to do something else. Is there an easy fix to make this script work inside these dialogue boxes? Or is this a 'bad idea', I shouldn't think too hard about it, and instead keep redirecting people to the poll page?
I'll add that it's messed up on my screen too, in case it's possible it was just a client-side thing.
e.g. Avacyn the Protector
Currently that page don't show which cards have, for example Cycling, or Multikicker. I don't know if anyone would want evergreen keywords to appear there, though.
Maybe it could be a cardset option? Apologize if this is a big ask, I'm a bit tired to think about the logistics of coding this, not that I know much about web languages
A MSE export template that exports to the CSV format needed by Multiverse may be helpful to write; that is independent of Multiverse. Unfortunately, MSE doesn't support import templates, although TeXnicard does. I also started writing a export template for TeXnicard to export Magic: the Gathering sets to the Multiverse import format, but the documentation for the Multiverse import format isn't so clear. (Templates (whether major or minor (import or export or rendering)) in TeXnicard are written in a combination of PostScript and SQL, although PCRE functions are also provided. I am writing TeXnicard due to many things I dislike about MSE, including the GUI and WYSIWYG; I like the batch interface and command-line interface instead.) Some features of the Magic: the Gathering template in both MSE and TeXnicard may be unavailable in Multiverse, and when transfer in other direction, also some things might not be specified, so will be missed.
If you hover your mouse over the letters "CI", a little tooltip should appear with the longer description "Show colour indicator?" The checkbox has been there since the beginning; it's just that I decided it was taking up too much space for how little it's used so I condensed "Colour indicator" to "CI".
yeah that's it thank you :)
Do you mean the color indicator? It shows a little circle with the cards color left of the supertype/card type and is used in place of e. g. "~ is red." on cards without mana cost or cards that cost
.
Canon Examples: Crimson Kobolds, Ancestral Vision, Crashing Footfalls.
MMV Example: Azar's Kobolds.
Well, when flicking through multiple different cards it's disruptive to have things move around. But yes, as long as things aren't actually covered up by it, it would be functional.
Um. Hm. Well. OK, amuseum could get the tooltip previews to look nicer if they made those cards use a card frame that Multiverse knows is landscape, such as Plane cards.
And the flow issue is a separate thing. Yes, I should definitely refactor individual card pages to use flexbox or some such so that you can definitely scroll to all the content.
Card image size specifically, though... I'm not sure that's my call to make. How big should they go? If the set designer supplies huge high-res images for their cards, aren't they wanting me to display them in full res?
If I put CSS on Icy Moon of
then the text is unreadable - again, because amuseum has told Multiverse that the card frame is portrait but supplied a landscape card image.
I think the main thing to fix here is the flow issue on individual card pages. If I addressed that, while letting the image still be as big as it wants to, would that meet everyone's needs?
Icy Moon is another one.
When you have a full-card image on the left; where this has a mockup. And yeah; that'sa very good example of it going very wrong.
I can come up with at least one example: The default view for Nexus of the Multiverse is one that comes to mind. The image is much wider than the mockup and its height is so much that the textbox is off-screen (in the sense that vertical scrolling doesn't even register that anything of the image is off-screen - there would need to be more comments before the scrolling feels the need to catch up).
In which view?
The site is somewhat inconsistent. Hover links like Skullcruncher Disciple have the tooltip image scaled down. In the Visual Spoiler the image is at its supplied original size.
And bizarrely, inline embeds using double-parens like this use the Multiverse render even when a full image is available:
The bottom text box of a flip card doesn't show what you've typed in it while you're editing the card, although it's there when you save changes. If you preview changes, it actually clears the enter bottom half. You also can't set the frame color for the top half separately from the mana cost, although that works for the bottom half, even though I'd expect the bottom to use the same frame as the top by default.
I'm on a very out-of-date version of Firefox, if that matters.