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-04 22:46:46)
I want to do this, and in fact I've been trying to implement that. Last time I tried I hit problems with the regex of all card names being too long. But yes, I want to do this.
sorry for this unusefull report, was in a hurry to get to work. Now it works just fine again, but for about an hour (till i left) when i loaded ANY skeletonpage it just displayed the optionsbox, the header and the bottomline. I tried several reloads which didn't help.
neuromancer told me they are working now.
As an example: http://multiverse.heroku.com/cardsets/224/skeleton My skeleton page is working very well right now.
I do think, Alex, that there needs to be more explanation on how to set up the dratted thing though. I remember it being non-obvious at the time.
This report is really, really unhelpful. I could answer flatly "Yes it is." You don't tell me what's wrong, what you'd expect to happen, which cardset the problem is with... Please take a look at How to Report Bugs Effectively and come and provide some more details.
Seems to be working fine for me. If you can reproduce it, I can take a look in the logs: Please let me know the precise time/date of a failed preview instance. Alternatively, the cardset and full contents of a card that you tried to preview but got erroneously created might help.
Can you give more clarificaiton on the circumstances of this error; because I was using preview heavily on Saturday and it was working for me, then.
I'm always up for making it easier for people to get data in/out of Multiverse. Could you email me your txt file so I can see the format it follows? (alex.churchill@cantab.net)
Hmm. Yes, this has definitely been suggested, but possibly long enough ago that this was only on the ToothyWiki page, not in the Feedback repository here. It is a very sensible suggestion, anyway; I just never got around to speccing it out because there were always shinier or more urgent things to fix.
I looked to see if this was already suggested, or already implemented -- I felt I must be missing something. But if it's not been explicitly suggested, it seems like it would be easy, but quite helpful, eg. to have a discussion of a mechanic on a page explaining it, rather than on whichever card happens to use it first, or needing to make extra cards specifically for the discussion.
Good idea. I think I had this on a list of desired features some time back, but it slipped off. Don't know how easy it'd be.
Mm. Yeah, I had problems the last time I tried import data. I wasn't able to get it fixed last time I looked into it: it seemed that the CSV library had got confused. I should have another go at fixing it. Thanks for the prod.
Heh... I know this is a weird place to mention it, but Avatar of Bodach doesn't tell you what to do if multiple people have the same number of cards in their hand, which also happens to be the most amount of cards in any players hand...
For example, I set the formatting line to "image%name", click "Replace with new", and try to import "http://img259.imageshack.us/img259/7337/avatarofbodach.jpg%Avatar of Bodach" (without quotes anywhere). I get the error "Line 1 of data had 1 fields when expecting 2".
EDIT: That's interesting. The link is supposed to go to http://img259.imageshack.us/img259/7337/avatarofbodach.jpg but the auto-link code thinks the link is http://img259.imageshack.us/img259/7337/avatarofbodach.jpg%Avatar
Haha. Now I feel silly. I was able to reproduce the problem on Jon's computer, since mine is having issues right now. This is just the kind of thing that happens to me and technology. Thanks for helping, Alex.
Screenshots received - thanks. I think that's finally helped me track down the problem, which is...
...that you're slightly zoomed in.
That's pretty awful that my Javascript resizing code goes so horribly wrong if you're zoomed in. But I can finally reproduce it. If I go to, say, Gale Dancer and repeatedly zoom one step (ctrl+mouse scroll wheel) then reload, at anything above a certain zoom level Multiverse gets confused and makes the text as tiny as it can before hitting the hard limit I gave it. Yikes.
Well, okay. There's a short-term workaround, which is to zoom out one step. It seems that your zoom level is just one step away from what Multiverse is happy with, so for the short term you can just hit ctrl+scrollwheel down, and that ought to avoid the issue for the moment.
But I should definitely try to fix this, because that's an absurd way for my site to behave.
My guess is that Chrome recently rolled out a change which makes the Javascript widths/heights of zoomed pages report the actual number of pixels displayed on the screen, rather than the "pre-zoomed" size, and that broke my code. But it's just exposing a pretty bad way for my code to behave at all, so I'll definitely get this fixed.
Many thanks for working through the debug steps with me to help me find the problem.
It might also be worth noting that text displays normally on tokens.
Sorry for all the trouble. :(
Okay, I'm sending you a couple of screenshots.
The first time I hit "Expand text," it grows to what looks like "normal" size on a card that doesn't need smaller text. The second time it gets a bit bigger. That function seems to behave normally. Is it worth noting that when I first load a card or a page of cards, the text is normal size for a few seconds before shrinking?
How very odd and irritating. Um. This is rather vexing. I'd really like to get to the bottom of this, but it's a bit hard when I can't reproduce it locally. Can you send me a screenshot?
Another thing that'd be somewhat helpful is if you could go to a card whose rules text should fit without shrinking (like this one), right-click the textbox and select "Inspect Element"; select the div with class "cardtext" (it'll probably be two above the one that gets selected), and tell me the contents of the "style" attribute on that div.
Or in fact, does the "Expand text" link below every card do anything? Can you describe to me precisely what sequence of behaviour you see clicking several times successively on the "Expand text" link?