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-05-12 22:23:39)
Fortunately it's not as bad as you think (and it's not really a bug).
The thing is, you've got the card's type set to "Planeswalker". Multiverse is respecting that.
If you edit that type to remove the word "Planeswalker" (just removing the final "r" is enough) then it reverts to the normal creature frame and you can edit the power (to remove it). Then you can restore the "Planeswalker" type if you want.
When trying to edit the card Torben the Crusader, I noticed that trying to change the frame from "planeswalker" back to "normal" is not possible - in fact any frame you choose afterwards will have now a face that's a planeswalker card.
Due to this the field "power" cannot be edited after creation of the card if you make the card a planeswalker.
Cardlist is known to not work. But Visual Spoiler should work, as that's paginated. I've used Visual Spoiler on the Multiverse Design Challenge set in the past... yes, that works fine, and that set has 3000 cards.
I agree that VS doesn't seem to be working for CWNH though. That's frustrating. I'll look into it.
Edit: Wow, it seems to be that anyone attempting to view the CWNH visual spoiler generals a "Memory quota vastly exceeded" error. Yikes.
While checking some sets for the behavior of Visual Bug in Visual Spoiler if stumbled upon another:
This visual spoiler page clearly shows frames of multiple colors, but for me the line "Show frames:" contines only a button for filtering black frames (the set prviously contained only a large number of black cards, so maybe the buttons just don't update correctly with new cards added?).
Force refresh does not resolve the issue.
link to image
Left: before applying filter Right: after applying filter
It seems the filter currently just hides card art.
Aye. The Cards With No Home set with 1600+ cards is a good example. It probably has a bunch of interesting cards, but currently it's impossible to view them properly. You are limited to scouring through the "Recent Activity" or whatever.
Maybe some kind of "partial view" with couple of hundred of cards per page could alleviate this issue?
I should get back in the habit, really.
Woah. That is one funky page.
The reason I implemented it at all was for mashups, actually :)
There's a (not very) secret page http://www.magicmultiverse.net/mashup which Vitenka asked for, which is a frameset containing a random Gatherer card (when Gatherer isn't down), 2 random Multiverse cards (as often the first one is blank or otherwise unsuitable), and a Create new card window in the community mashup set :o) Anyone can feel welcome to use it... in fact, perhaps we should link it from the mashup set's front page.
One card would also make make sense for things like mashups, where you also want to choose one card and not get distracted. But OTOH, I always just made up my mind in advance to use the first card listed and that worked fine.
@Jack: Oh, hey, thanks!
@Jack & Alex: Excellent work! I wasn't expecting the problem to be hashed out when I woke up. :)
Hm... I guess I should bookmark the single random card address. I'm not sure if it has a use to other users, since a sample booster and/or 15 random cards seems to be a better way to get a glimpse into what's in Multiverse... and that might be the best way for people to experience random cards from this set. But with my article series, it's best that I get a single random card. Otherwise, I could be distracted by the other cards that populate, tempting me to choose a different card, and tainting the results.
Oh cool, nicely done! I'm glad I was going in the right direction.
I've mixed feelings about the "here's a thing that's like a lazily-loaded array". I like the idea a lot, and when it works, it lets you do a lot of stuff very clearly and efficiently. But there always seems to be a point where it's secretly converted to an array when you don't quite realise.
fixed!
I believe "Cards.nonsecondary" is what's called a "scope" in Rails terms. It's not actually accessed anything from the database yet. ".sample" operates on a ...oh. Oh. The sample method operates on an array, not on a scope... so it is pulling in every card from the database, because it's converting the scope into an array of every card!
Right, that's a moderately simple fix then.
Hm. Yeah, I'm a bit confused. You thought it was slow because of what you did to the mechanics? But it looks like it's choosing even one random card that's slow, not so much displaying it.
Is the github code up to date? My l33t google-fu says, it is basically just doing "Cards.nonsecondary" and then calling "sample" on that. Is there something about that that means the entire array needs to get loaded when it looks like it shouldn't? Or is something else the problem.
I really don't know why the /random function is so slow. It shouldn't actually be pulling every card out of the database. It will be pulling up the cardset permissions and the mechanic text for every cardset represented in the randomly selected cards, but that shouldn't affect the case where there's just one or two cards, especially given that popup previews of an arbitrary card are so quick.
Oh cool. OK, I'm wrong twice over, because I didn't realise that existed, and I assumed that, if it did, the overhead wouldn't make it timeout :)
In retrospect, maybe jmg's workaround is "go to random.org and get a random number between 36 and 81862" and "go to http://www.magicmultiverse.net/cards/[that number]"
PS: jmg, I'm enjoying reading that series.
As it happens, there is :) http://www.magicmultiverse.net/random?count=1
Would it be worth making "show a random card from multiverse" as a workaround (maybe add a secret "/random?n=1" parameter or something?).
Ah, yes. That's going to be particularly resource intensive with the tweaks I made to mechanics, and Heroku is still killing any request that takes longer than 30 seconds.
I have some performance enhancements in my sandbox which I should really deploy in the next few days, which I hope should remove a lot of the extra delay and perhaps even improve performance relative to before the mechanic tweaks.
The option on the front page to "See a Random Selection of all the cards on multiverse" tends to result in getting an Application Error screen, no matter what web browser I use. It works sometimes... but lately it only seems to do its job one out of every four days I try it.
Which kind of stinks. Because I was hoping to add some random cards from Multiverse into my According to Gatherer Cube. It isn't a real problem, since I can just take random cards from 'Cards with no home'... which in retrospect is probably more appropriate anyway. But multiverse.net/random still needs help.
Without typing them from hand.
See here
Mechanic expansion in comments is intentional, but not as useful as I'd expected it would be. I might switch it off.
Deathtouch was an unintentional omission. No idea how that happened. It's in now. (Might take a few hours to propagate across all server processes.)
There's no easy way to import Wizards mechanics into your cardset, but that's a good idea. Create an enhancement and I'll try to get that done.
Update: Flying (This creature can't be blocked except by creatures with flying or reach.), Lifelink (Damage dealt by this creature also causes you to gain that much life.) ... work
Deathtouch (Any amount of damage this deals to a creature is enough to destroy it.) ... doesn't work
Is the replacement in comments intentional? I never noticed it before.
Is there a quick way to import the existing keywords into a set so I can also see them on the mechanics page? Seeing the number of times you have used a keyword is an invaluable tool and one of the reasons I wanted this.
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.
(1) (a) (b) awesome!
(Did you leave it an option somehow for people who used it, or just, everyone should use {} not () now? )
fixed, piggybacking on the urgent fix to visual spoiler