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 2024-05-14 05:29:13)
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.
I'm thinking mainly about recent changes. On the right it has a description of the card set, and I'd really like to sometimes at least be able to override that with a description of the card in question. It's mainly for my huge stable of "This card idea is halfbaked at best" cards where I want someplace to describe what I'm trying to do.
It's not a hugely important request.
Hmmm. Interesting proposal.
I think it's generally best for a card to stand alone. If there's some rules that need adding for a set of cards or a mechanic, those would be best explained on a details page for the set.
When you say "the various grid views"... I can think of skeleton, visual spoiler, and cardlist. It makes sense to include a description in the cardlist. I don't think it makes sense to include anything like that in the skeleton automatically; perhaps a card could have a very small text field to be automatically included in the skeleton, but individual skeleton rows want to be very slim to keep the whole page manageable. On the visual spoiler I don't think it's sensible to autoinclude text - or at least, I can't see a use case for it at the moment.
Could you elaborate what kind of description you're thinking of, and what set of pages you'd want it to be included on?
If it is a card they're deliberately choosing to reprint then it's friendly to provide a link to the Oracle text. If it's not then it's nice to let people choose a new name.
qqzm has provided me with a script that would be very helpful for this.
Ha! The first thing I thought when I saw the new mechanic was "Alex is gonna love this one." ;)
I'm glad they finally broke this taboo. It will be interesting to see if it becomes a major mechanic in the future, after everyone gets a chance to play with it and see how much fun/annoyance it can be.
"artifact" means "duplicate", I think