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-07-01 07:41:56)
I have been so beiwdlered in the past but now it all makes sense!
It was dark when I woke. This is a ray of sunishne.
Ah, yes, that makes sense. I could certainly add a "Move" link to the edit page... except that won't save any other edits you've made in the form from the edit page. Hmm.
Probably he looked on the "Edit" page, since that's sort of a form of editing a card.
See devise and OAuth (in particular devise :oauthable)
E.g. Civilized Scholar.
Yes, I think it's one of the most needed functions in Multiverse at the moment. It's definitely a high priority for the next release.
This would make me very happy.
Oh. Hmmm. Interesting. This is why I could do with conducting some usability studies, I guess. Where would you have looked for such a link, and where would you like to see it?
Aaah, I see. It shows up on the "comments" page, but nowhere else. Would explain why I missed it.
Go to any card you can edit. Look just below the card. Below the "Expand text" and "Edit" links there are "Move" and (if you have permission) "Delete" links.
There's a "move" button? Where? I could probably use that!
Hmm. You want something beyond the "Move" ability? Clearly "Copy" is a different operation from "Move", and it makes sense to permit both, but your stated use cases sound like "Move" would meet their needs. I think some people are already using "Move" to store cards that aren't quite ready to go into a set yet.
Your #1 does make some sense. I wonder though if it's too specific. There could be other things users might want to indicate before people comment, such as "This set is deliberately breaking the colour pie so there's no need to point out colour pie violations", "This set isn't using rarity so there's no need to point out inappropriate rarities", and so on. As Jack says, this seems mainly to be on a per-cardset basis.
I don't know how much of a problem it is at the moment with people being offered undesired templating advice. It seems similar to the way that most of the feedback authors of fiction and fanfiction get will be "You made a typo here and your grammar is wrong there", where what they'd prefer is more along the lines of "This character is underdeveloped and this scene breaks suspension of disbelief". There are certain types of error that it's just easier to spot (for certain kinds of commenter). I don't know if most cardset authors would prefer to have templating comments or no comments; it's often the case that one person making a templating comment prompts others to make more useful comments by drawing their attention to the card.
What I think I might consider is allowing a user to specify, on a per-cardset or also perhaps per-user basis, one short sentence to be shown to everyone who's about to comment, perhaps alongside the "Post comment" button. A few present options would be things like "Note: I'm not trying to use modern templating in my rules text", but it could also be free text input for any other points authors wish to make.
Eeenteresting suggestion.
In reverse order: your #2 is something I've considered. I've actually considered it more for cardsets: in a view like Recent Changes, I often want to navigate to some particular cardset and create a card in it, or search that cardset's cards, or whatever. So I've considered adding mouseover panes for cardset navigation. For users also makes some sense, although I'd want to know it'd be some use before I put the time in to deal with it.
Mm. Makes sense. I'd need a set of probably 16 images (one for each colour and two-colour pair, and a five-colour one for Transguild Courier and Statue of Eternity).
Heh. Yep. The problem is that your images are too large :P
Well, no, the problem actually is my tooltip library doesn't let me adjust the size of the tooltip once the AJAX request returns. I have to guess how big will be big enough; if it's too small we get this problem, but if it's too big the tooltip moves to the left of the cursor unnecessarily.
There are a couple of other problems with the tooltip library I'm using, so this may be indicating I need to ditch it and write my own that's better suited to my needs.
Or it may make more sense per cardset. You might have a shortlist of "This should be in modern templating", "I prefer to use modern templating, but these cards haven't been templated yet", "I prefer to use modern templating but with British spelling and singular 'they'", etc, etc. Obviously people should be able to do that by putting a comment in the cardset, but it might make it easier to have that option explicit, and possibly cut down on superfluous corrections??
It seems fixing Mockups favoured over images brought its own problems. :)
Now that I have the Front Page capability, there's not much need for the original use of highlighted comments, actually. I could remove the up-front display of highlighted comments and let them be just used on a card history to let the cardset creator draw attention to a particular comment, and potentially later on let them be displayed somewhere else as well.
I was thinking it could use the highlighted comments - but you can highlight more than one (and since they show up at the top of your set you also usually want to highlight very few cards)
I think the comments log for the card is the best place for that. It's intentional that people can only post a comment on a card from the page where the existing comments are shown, so if they're going to make some misunderstanding then the creator has a chance to correct them first. You can draw attention to a particular comment using
**bold text**if you want.I'm inclined to leave this suggestion open, but not planning to implement it particularly soon.