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-11 17:53:35)
Can you link a set and/or card for which the bug occurs?
I did not, no. Trying while logged in - I do indeed see a difference between visual spoiler and individual cards. e.g. Migrating Settler demonstrates the issue.
And this card now DOES show an artURL when I export as JSON; which it did not previously (on a machine I wasn't logged in from)
Lets move the cache image issues into here instead of the print format card.
https://drive.google.com/file/d/19EFZRal8oLuTnhvggsn7QOTELNMBJYWa/view?usp=drivesdk
This is a saved pdf of all my 'view by sections' pages. Vitenka, when you view the individual cards do you see art? It's confounding just how inconsistent the data is for my cardset.
I checked the export set and all the info seems to be there when I try exporting, consistent results for each export format. Could you be seeing something different because of the italicized '(unsigned)' after your name?
View by sections I also see no images. Individual cards, I see no images. Checking the database contents via export, I see no URLs. I'm pretty sure that the server believes there's no URL on most of your cards.
Why it thinks that, if you're sure they're there, I have no clue.
Print update! After a lot of headache with print drivers and scaling I figured it out (mostly).
From a printable visual spoiler page, right click and hit print, then Save as PDF. Use a landscape layout, and increase the scale to 104%(edit: I previously said 108% but somehow that's actually wrong and 104-105 is a better fit). Then print that pdf and the resulting cards will be the exact height of a standard magic card (3.5") however the width will be slightly smaller than a normal card.
I haven't figured out how I'll alter the aspect ratio of the cards without distortion, that may simply not be an option. (My roommate thinks she could mess with the html but thats above my paygrade)
I see the same thing HarrisonY says: Visual Spoiler page without images, but View by Sections page with the images.
I must restate and reiterate that nearly all the cards have art urls on them. If you click through any of the commons you'll see that they have arturls. /cardsets/2580/visualspoiler will occasionally be up to date, but then revert for no discernable reason to a very old server cached state.
You mean /cardsets/2580/visualspoiler ? I can see 138 cards; though only about 4 have images. Two white ones; and a couple others such as Tortudiphant and Loubus, World Grinder.
And looking at 'export' (json output)? Very few cards in your set have any artURL. So it looks like you may have created the art, but multiverse doesn't know about it. If you're sure you entered it in the card's edit fields, then I think you need to make this a red card to indicate it's a bug.
(Note: A couple of cards DO have an art URL but the image doesn't show up anyway - because the site it's linked from doesn't allow embedding. That usually means it only shows up if you visit that site, at which point your browser has it cached and will show it here too.)
HAH! New bug Alex: Multiverse picked up (full url of /cardsets/2580/visualspoiler ) as 'non-logged in users aren't allowed to post external links' when it's clearly an internal one.
ctrl-f5 is the same. anyone want to do me a favor and look at my tuvia set visual spoiler and see if you can see more than 2 arts? the art appears when i hit the "view by sections" buttons with a bit more consistency, but its a bit sad when I know I've created and uploaded over a hundred pieces of art and they dont show up.
Also I'll update when I do some test prints at work, my first go I'll try saving the page as a pdf, looks like it will fit 9 cards on a 8.5"11" page which comes very close to the 2.5"3.5" dimensions of magic cards. Wish me luck.
Heres a quick and dirty look at the difference on my end: https://i.imgur.com/RZ1fr8m.jpeg https://i.imgur.com/m7XgOdV.jpeg
Might be browser-dependent. I usually use ctrl+f5.
Do you have a link to the caching issue? If it's server-side caching, then that's obviously not going to help.
How does the print preview look for you? It prints fine for me, when I set it to "Fit to page width", but I can also manually scale it before printing and it shows the layout relative to the size of the page correctly.
Tested on a computer, ctrl shift R does nothing on visual spoiler page
For whatever it's worth, I've also not had the cache problem; but I think the visual spoiler IS one of the pages that has extra server side caching; which has been known to go wrong.
But the main point - how to get the output size right - I'd also love to know. The one time I printed out I also ended up with dinky-size cards.
I'm on mobile and even after clearing my cache and switching browsers I still see my visual spoiler page revert back to a much older iteration all the time. It will update just fine for a while and then boom it's back to when I had 3 arts only lol.
Still this does bring up the fact that I should be trying to use a computer to format print pages in general
Edit: I've asked friends in other cities to look and they see the old version when it reverts.
Ctrl+shift+r refreshes the cache, so pressing that when you visit the site will ensure it's updated
Multiverse doesn't generate images. You could try Shena'Fu's Card Creator's importer to generate card images en masse. The URLs to these images are simple: https://www.ieants.cc/magic/ccimg//.png , where would be the set's name.
As for Cockatrice, it would be trivial to write a client-side converter in HTML + JS. Since JS can handle XML or JSON as JS objects, the conversion should be straight-forward. Personally I would start with JSON, then convert to whatever final format.
Is there yet an easy way to draft and playtest the cards made here in Cockatrice (or another software, I don't know any others)?
Have you tried pressing the 'Mark all cards as active" button on the skeleton page? My skeleton cells don't update until you do that.
Visual spoiler page is tough, I use the "view by sections" button to see more up to date visuals.
I find in general the caching doesn't trigger as much for edits as it does for new cards.
Edit: it's something similar with the missing page. I created an info page on my set and the link took a while to appear even though I could directly navigate to the page through my history.
TBH I think it's mainly my fault. I implemented a bunch of caching, several years back, to try to alleviate server load. That basically works; the site is faster now, especially on high-traffic cardsets (hah), than before I did that. But it caches too much and exceeds its memory quota. Eventually that builds up and the server uses so much memory that Heroku kills it and it has to restart.
Huh. I'm a LOT less sympathetic to them about the "Heroku has fallen down and can't get up" outages, if you're actually paying them for this.
Panic over, I suppose. Turns out as of a couple of years ago I'm paying $16 per month, which is $9/m for the database and $7/m for the "hobby dynos" that run the server.
I suspect I could get rather better performance for quite a lot less money if I were to move to something like AWS. (The URL would stay the same, as would the immediate hosting technology, Ruby on Rails; but the provider would change.) I'd need to take care of things like Ruby updates myself and be more vulnerable to security issues and suchlike, but it might still be worth it. But, well, as people are sadly rather aware, I'm not taking much time to maintain this site any more :/
Still, outdated and crusty and creaking as Multiverse is, seems like it's not going anywhere in the short term.
ha! turns out I'm already paying them for both halves. Phew, I guess?
😟
:'(
What is the cost to maintain this site, and what do you expect it to go to? There don't seem to be that many active users, so I don't imagine a paid tier here would have a big impact, but I'm curious
Their blog post announcing this: https://blog.heroku.com/next-chapter