Dungeons and Dragons Wiki talk:Rating Articles
User Sandbox, But No User
Ambidexterity, DaTedinator Variant (3.5e Feat) has met the criteria for being sandboxed, but there's no user attached to it! Where do we put the sandbox? Do we just delete the page, since the author is not a community member and therefore not terribly likely to show up and fix it? --DanielDraco 07:40, 15 August 2012 (UTC)
- Havvy moved it over, you could send it back to him and let him decide if he wanted to try to get it updated or just removed. Otherwise, deletion would be the only option I think. - Tarkisflux Talk 15:57, 15 August 2012 (UTC)
- I'm fine with deletion. Surgo 16:03, 15 August 2012 (UTC)
Mobile device problems
Clicking the "rate" button doesn't work properly when viewing the site on an iPad or Blackberry, and may not work for other mobile devices as well. Is there any way to fix this? —Preceding unsigned comment added by Luigifan18 (talk • contribs) at
Community Favored/Opposed Averages
I think the goalposts for CommFav and CommOpposed are too tight. If we loosened the rating average by 0.25 in each direction, more articles which should fit in each category actually fit in there. --Havvy (talk) 18:23, 1 March 2013 (UTC)
- I agree with this and wholeheartedly support it. It feels too easy for a single outlier to change things at the moment. --Ghostwheel (talk) 18:24, 1 March 2013 (UTC)
- I disagree, particularly since the reason for changing it seems to be that some people think that some articles should fall into those categories and aren't because other people disagree with them in their own ratings. The point was to keep them tight and force a strong consensus for an article to land in one of those groups and allow outliers to push them out of them. That is working as intended and discussed, and I continue to support it.
- So while I don't really care if we opened up the favorites a bit, I am not really for it either and would vote against it because I want a degree of exclusivity among those articles since they're competing for main page advertising space. But I am pretty opposed to opening up the bottom end as proposed, particularly given the current trend of people opposing things before offering constructive advice or opposing on fluff grounds (instead of simply disliking). The articles already show a low score (which we can show on nav now if people want to), and moving them out as a result of the current rating trends + easier kicking seems dickish and exclusionary. Neither of which are conducive to the sort of community building that people say they want to counter the complained about slowness.
- So if a display change isn't enough for people who want more stuff removed or highlighted, I'd like to see a better constructed argument in favor of changes. The downsides outweigh the upsides IMO.
- I agree with Tark. The limits are where they should be. For the amount of rating that we get, we get about as many CommX articles as we probably should. I, for one, have not seen any articles which are generally favored by the community which have not become CommFaves, except by virtue of just nobody bothering to rate them. The ones that fail to fall into a category are the ones where no consensus exists, or where the consensus is decidedly unenthused in whichever direction it points. That's exactly the way it should be. --DanielDraco (talk) 20:22, 1 March 2013 (UTC)
- I feel like it would be a good idea to broaden it if CommFave and CommOpp were marks of "good article" and "bad article". But they're not. There are and should be good articles which are not CommFaves. That category is not for favorites of 25% of the community which everyone else kind of likes. It's for the best of the best as seen through the eyes of the majority. They are the articles that we can all come together and say, "Yes, this is a damn good example of what we want to see on this wiki." As is, we can already get CommFaves with only 50% of voters actually wanting it to become a CommFave. It should not drop below that. --DanielDraco (talk) 20:34, 1 March 2013 (UTC)
Additional Rating Pictures
Alright, that didn't work so well. Let's try something else. Right now we have three images: opposed, rated, and favored. Let's change that up. We have names for our ratings, so add pictures for being +/- 0.5 from the value shown. For example, opposed would still be 0-0.5, but we'd show a dislike pic for 0.5-1.5 and neutral for 1.5 to 2.5. --Havvy (talk) 20:43, 1 March 2013 (UTC)
- Completely fine with that. It's a recode, but not a particularly hard one. - Tarkisflux Talk 21:33, 1 March 2013 (UTC)
- Re-code done, new art added (thanks Gan!), and the additional visuals are now live. Please let me know if there are any bugs.
So the issue has come up of whether we want anonymous ratings to be allowed. We chatted about it a bit in IRC and TF asked me to post some of the points raised against it so other people can agree or refute as they see fit. I'm just going to do it in bulletpoint for sake of ease.
- The lack of a singular, unified identity tied to them
- The fact that they are the easiest (though not the only) way to sneak multiple ratings from the same user onto an article
- The brief registration process would be a good deterrent against troll ratings and hasty ratings from much-too-casual users
- A registered user is one more likely to stick around and discuss their rating.
It has also been noted that ratings from unregistered users under a dummy name might very slightly mitigate one or two of these issues, but not to any satisfactory degree. --DanielDraco (talk) 00:27, 24 July 2013 (UTC)
- Here are some points for it:
- Lower barrier to ratings means more ratings and more casual user friendly in general.
- Unregistered ratings allow people another way to dip into the site (in addition to talk page discussions and anonymous article contribution) and convert to registered user later. This assumes that conversion is a more effective population building tool than feature gating though, and I'm not sure that's actually true.
- In response to DD's security points, we don't actually have ballot stuffing, troll ratings, or poor ratings from passersby to worry about at the moment, so the need to defend against them isn't well supported. I get the worry, but solving a potential future problem that may never even happen doesn't seem particularly compelling to me since it comes at an accessibility and openness cost.
- I think this is likely to come down on community building decisions, and on those I have a preference for the continuity of a registered user name. It also makes it much easier to direct attention to responses with user talk pages instead of article talk pages, which is something that I see a lot more often than we have IPs rate. Which kind of sucks in this specific case because the IP who started this discussion would be excluded as a result :-( - Tarkisflux Talk 18:36, 24 July 2013 (UTC)
- I'm of the opinion that people should register before rating for the reasons DD stated, and also for the reason that if they invest more into the system (even if it's a few more minutes), they're more likely to be an active part of the community, rather than just saying something and leaving after a single rating. Furthermore, it's not like IP ratings are a major part of the rating system, so it wouldn't be a big downside either. --Ghostwheel (talk) 22:23, 25 July 2013 (UTC)
- I don't see problems with allowing IP users to rate. Sure, the odds of having a dialog with them might be a bit low, but the whole point of a rating system is to get opinions. Some of those opinions might seem stupid to the author of the article and the author might want to discuss it, but even if that never happens, at least the author will get some feedback so they can either solidify their own opinion ("yes, I made this the right way") or see something they need to change. And if the author is upset about an IP rating throwing off their article's "score", they can just ask some of the regulars to go rate it to perhaps put the score where the general community thinks it ought to be. I don't think censoring opinions that go against the general consensus or that seem dumb is a good idea.
- Also, I agree that security concerns aren't really an issue and probably won't be. It's not like sockpuppeting is impossible anyways, so I don't see IPs offering any threat that registering can't already do (if maybe a little less convenient).
- As for it creating more active members... Well, I think that's not necessarily a great assumption. My initial experiences with the old D&D wiki was as an IP user for a while. I wanted to get used to how to comment on a wiki and such before I made an identity for myself. I wouldn't have joined just to rate if there had been a rating system. So, there's at least one counterexample to what you are suggesting, Ghostwheel. Whether it's more likely either way: I don't know. --Aarnott (talk) 22:29, 25 July 2013 (UTC)
- Surgo and Aarnott are for IP rating while DD and Ghost are against, and I don't really want to block out the only IP we have who is currently rating. So in the absence of more people wanting to restrict ratings and the lack of problems with the current open system, I think we might as well leave it as is for now. Tying down later is easy enough after all. - Tarkisflux Talk 20:08, 26 July 2013 (UTC)
- Just a bump before I tweak DD's policy writeup in a few days. As things stand IPs will be allowed to rate. They probably don't have the same expectation of permanency as registered users (because IPs can change, but that seems extremely unlikely) and should convert their ratings if they ever do register, but that's minor policy writeup stuff. - Tarkisflux Talk 22:42, 1 August 2013 (UTC)
Removing and Blocking Ratings
Okay, let's talk about more of this policy stuff.
I have been told that there are users who feel that a negative rating with insufficient detail is unfair in that it offers the author no ability for the author to adjust the page to address the criticism and request a re-rate or apply the OldVersion tag. That doesn't seem like an unfair complaint (if one with a few other logical extensions that I'll get to shortly). I'm wondering how people feel about allowing an admin (and only an admin, because edit wars) to remove a rating upon request from the author if they agree that it is insufficiently specific and the rater has failed to respond to requests to clarification. Yes, I said remove and not block because the OldVersion tag is specifically there to delineate one that the author is blocking for the stated reasons no longer applying, not one that failed to specify actual reasons and was dealt with by an admin. It seems like the sort of case where we'd want an admin to step in and agree that it was a crap or inappropriate rating per policy, instead of just a user dispute. We could do a new tag instead, but I don't really want multiple blocked ratings tags floating around confusing people looking at the ratings.
Other things that seem unfair for similar reasons: continuing to include non-updated ratings two years after the migration. The RC system didn't include a negative rating and doesn't actually hurt articles (but may be blocking some actually negative ratings), but the anyone registered like/neutral/dislike system does actually hold articles back when they aren't updated. I'd like to remove all of them for consistency sake, and to retire the tag associated with them. It's been 2 years, people really should have dealt with them by now to be fair to the articles that they're attached to. Unless there's really strenuous objections from a lot of people, I'm just going to pull them all. - Tarkisflux Talk 05:01, 27 July 2013 (UTC)
- Fine, fiiiiiiiiiiiiiiiine... how does one find their old ratings in order to update them? :-P --Ghostwheel (talk) 05:49, 27 July 2013 (UTC)
- My post prompted this, but just for the sake of unity I'll note here too that I agree that this is a good procedure to put in place. I would suggest that it include a request on the rater's talk page for clarification, followed by some amount of time (3 days maybe, to be shorter than the CommX grace period) for the rater to respond and clarify. And holy crap, we still have legacy ratings? Yeah, let's get rid of those. --DanielDraco (talk) 07:47, 27 July 2013 (UTC)
- I actually like people waiting longer than FOREVER to make these sorts of changes and would prefer 7 days to match with the CommOpp policy, but I can live with 3 days.
- How do people feel about removing non-updated OldVersioned ratings? If we went forward with it at all, I'd want to wait 7+ days from user talk notification of the OldVersioning. I'm not sure how I feel about it, but if we're opening the door to removal for these other reasons it seemed like the sort of thing we may as well discuss. - Tarkisflux Talk 17:15, 27 July 2013 (UTC)
- My main reasoning for 3 days is preicsely that the CommOpp grace period is 7 days. If a user gives a 0/4 rating that pushes the average down to 0.5, then the next day the author sees it and contests it because there is no explanation given, giving the rater 7 days or more to respond will mean that the article will be pushed into CommOpp before the rating can be removed. I guess we could just not allow an article to be pushed in or out of CommX by a rating with an unresolved contest against it, but that would A) provide a stalling tactic for butthurt authors and B) be more or less tantamount to just letting the author nullify it before allowing time to respond. I stand by 3 days as a good timeframe.
- I am generally against removing anything from talk pages ever without archiving it. So I'm going to support Fox's idea here and say that OldVersioned ratings should be grayed out to be more visibly not applicable, but not removed.
→Reverted indentation to one colon
- Graying out is easy (well, it's another re-code, but whatever), and a better idea anyway. So let's do that. Your position suggests that you would prefer blocking insufficiently descriptive ratings on articles rather than removing them via admin. Is that the case and you would prefer a new blocking tag, or are the situations sufficiently different as to allow removal? - Tarkisflux Talk 04:07, 28 July 2013 (UTC)
- It seems to be just us in here, and non-removal was already suggested by Fox. So it's at least 50% popular. I don't mind supporting that over straight removal, which I'm also generally against. It's another tag, but those bother me much less in the grayed out scenario so I'm not worried about it. - Tarkisflux Talk 06:20, 30 July 2013 (UTC)
- And a bump here before I update more policies and rewrite the rating template again. Current position is for a new rating block reason that the author can apply after 3 days if they do not receive clarification after requesting such on the rater's talk page. And for the template to do a better job of showing which ratings are being blocked by changing the color scheme instead of just adding a disclaimer. It's live in a few days if we don't see some objections. - Tarkisflux Talk 22:47, 1 August 2013 (UTC)
Rating: "For Reasons Given Above"
Alone this should not be a valid reason to rate an article one way or the other. Referencing and agreeing to points below are relevant. But a rating should always add something to why it was rated in the manner chosen - and be given a personal touch that shows the article was looked into. --Franken Kesey (talk) 20:24, 5 August 2013 (UTC)
- No. If someone has expressed my feelings clearly and fully and I have nothing to add, then I have nothing to add apart from agreeing with them. --Ghostwheel (talk) 20:56, 5 August 2013 (UTC)
- And if someone's reason was: "Because its stupid." then three others: "For reasons given above." It should not be community opposed. No one took the time to work with the page. A rating is just as much a contribution to this wiki as an article is, there is no use in ten people making ten of the same versions. —Preceding unsigned comment added by Franken Kesey (talk • contribs) at
- As per policy, ratings must be validated with reasoning of some kind. It doesn't matter if its in the rating or the rater points to material elsewhere on the talk page (like from an earlier post discussing the article or the talk page of a similar article in a series for that matter). This is acceptable if less convenient in some cases of long discussions because people are lazy and reading ratings should be clear. Some raters don't like to express the same thoughts over again and waste people's time with redundancy on what's already been said (which itself reduces clarity, and again, people are lazy). Now, if the reasoning wasn't given or was for some reason invalid, then yeah, those ratings get struck. We already do that. Did you just hear a bell? 'Cause I just chimed in. --Ganteka Future (talk) 22:52, 5 August 2013 (UTC)
- A rating is not as much a contribution to the wiki as the article is, and if someone writes an exhaustive rating (or commentary) of an article I see no reason to tell someone they are not allowed to second that opinion. I've rated articles with lots of positive or thorough negative reviews , and trying to find something new to add is non-trivial. While I prefer to write my reasons down, requiring that is a barrier to new ratings that I'm not interested in raising.
- To your specific concern, vacuous ratings will be blockable based on being insufficiently clear (see above discussion) if the rater fails to provide additional details. And so would any ratings based on them. The case you are concerned about will be a non-issue shortly (and opposing for being 'stupid' instead of merely disliking might even run afoul of our merits requirement). - Tarkisflux Talk 23:04, 5 August 2013 (UTC)
- Grayed out ratings are now live. Parameter was changed from |OldVersion to |block to reflect different mission. Currently will accept |block=NewVersion and |block=InsufficientExplanation, can add more if we determine that these are insufficient. Editing article now. - Tarkisflux Talk 07:43, 17 August 2013 (UTC)
Merit Guideline Expansion
It's been complained about a couple of times, and I wanted to discuss it without cluttering a talk page. People do not get to rate based on whatever they want, and any indication otherwise should be corrected. Part of that is on me and not writing a clear merit guideline, which is why I have just updated it.
They were always intended to work as a "rate according to what's there, and if you're wrong we'll delete it" standard, but it wasn't as clear as it should have been. I have deleted ratings (not blocked, deleted) for merit violations when they didn't seem to be addressing what was on the page, and I will do so again if I see any that I think aren't addressing the article fairly. They were also intended to work to make sure people rated based on how well what they made fit into the framework they were inserting into (how well made a flaw was, for example) and not a commentary on the framework itself. If someone writes up why they think a flaw is a terrible fit for the flaw system and then opposes it, then so be it. That part was pretty much there I think, but should be more clear after edits.
There is a problem with applying that to the variant rules though, because they're trying to alter the framework rather than insert into it. And since I'm not willing to condemn a playstyle and won't let the wiki get into the business of doing it either, the only way to really judge a playstyle altering variant rule is by how well it meets its own goals and does what it says it's going to. Anything else is tacit approval of some variant concepts over others. Since variants aren't going to be adopted by people who don't already want to meet the goals they specify, the ratings will help them understand how well the article does the thing that they're interested in and not argue that they shouldn't be interested in. If you still want to argue that it's a bad thing to want in the first place, you can do that in regular comments. - Tarkisflux Talk 00:18, 5 March 2015 (UTC)
- This is a bump, because I don't want anyone complaining about not seeing these changes when I start informing people of violations and deleting ratings in a few days. If this isn't ok and needs to be adjusted, tell me now (or soon, you know what I mean). - Tarkisflux Talk 02:05, 6 March 2015 (UTC)
- Variant rules should also be judged on how smoothly they fit in the existing system (or at least the parts that are not replaced) and how overall usable they are, not only on their stated goal. If I make a combat system whose goal is to redo initiative to be like 2e and succeed, however the system triple the length of combat because of how it work, it is perfectly justifiable to dislike such system because of it unplayability. --Leziad (talk) 02:56, 6 March 2015 (UTC)
- Explain how to do that without letting the whole thing devolve into playstyle complaints, and I'm on board.
- Your example doesn't really do it. There could be people who would prefer the chance to interrupt a spell between the period when casting began (char init) and the time when it was successfully cast (char init - spell speed). There could be people who want small weapons to go slightly faster, on average, than large weapons. And there may be people who like randomized turn order. I am unwilling to tell any of those people that they're doing it wrong and their rule is bad and should be removed from the wiki, even if it does slow the game down substantially. Those are necessary consequences of the setup, and as long as they're discussed and acknowledged I don't see a reason why it should be rated badly because of them. People who want that other stuff might be willing to make that trade, and that's a playstyle decision. It's not one that I'm going to make, but that's not relevant to how well the variant achieves its goals.
- If there are other things that it does that don't work well or aren't intended, then it can and should be downrated for those reasons. But downrating because people want different things out of the game and are willing to pay different prices to make it work (when that price is done as reasonably as possible and indicated clearly) seems a lot like playstyle preferencing, and I'm not down with those cases. - Tarkisflux Talk 05:03, 6 March 2015 (UTC)
- Dunno if it helps, but I have an unspoken rule that I limit to dislike if it functions, but I think it's a terrible playstyle that hurts the game (and typically try not to rate those period, I'm not the target audience and it's a bit rude otherwise). Of course if it's broken AND a bad playstyle it's free game. The key point here is that dislike shows my disapproval, but oppose is straight up "remove this", and I think it requires a measure above and beyond the transition between neutral and dislike.
- One big thing I will say though is in your description, especially if it's an oppose, you need to justify it. That's why I harped on MS when he was like "I don't like dragons, oppose", and why I harp on others when they do the same thing. That is, at most, a dislike and really "you probably shouldn't bother rating this". Show why it is broken, regardless why you like dragons or not. -- Eiji-kun (talk) 05:07, 6 March 2015 (UTC)
- It not about playstyle, I wasn't complaining about 2e initiative in 3.5e by itself. It could work, I am referring to if it was done in a way that considerably slowed down combat. Perhaps not the best example so let try another. Short of designing such a rule myself we will need to go abstract and hypothetical here:
- Someone make a rule that change ability score, compressing them into 4. The system itself is consistent with itself and work well, however the changes have a great effect on the framework of the game. We need to take in account how the variant will rule will impact what it does not change: Monsters, spells, items. Now let say the rulemaker added fractional ability scores to add some variety to his 4 ability score system. This fractional ability score system work well with itself and is well written. There is a problem however, no monsters in the game use fractional ability score and using the variant rule would require the DM to convert any monster he want to use to the system. While the rule is well written and achieved everything it own goal it clashes with other part of them system and since using it require mass conversion it is not really seamless.
- Now if charisma was completely taken out from the ability scores, requiring major change in a lot of classes and skills. Assuming the rule is well written still there is alternative but it still require conversion. So while it is possible to use the system, and it excellent at what it does, doing so is an extreme hassle I believe it would be justified to rate this system negatively based on how it seam with part of the game it does not touch. Now if the rulemaker expanded the system and did the conversion himself the complaint would fall off obviously.
- It is true that variant rule create their won framework, but we must also consider how they interact with the framework they do not inherently affect. They still after all work within the framework of the game as a whole. Also we must consider how clunky and annoying some rules are, which I assume count toward attempting to reach it intended purpose and what if the author want to make the game as clunky as possible with 300 words paragraphs of rules? We also need to pay attention to the overall quality of the rules, it mathematics, it grammar, how clear it is. I think it would be fair to dislike a rule if you need a cipher to be able to read it no matter how well it meet it intent. What if the rule is inherently offensive? Adding racist and sexist or other distasteful elements to the game? I agree we should be more lax with rating variant rule, but basing it solely on how well it meet it intent seem unwise to me. --Leziad (talk) 05:24, 6 March 2015 (UTC)
(RESET INDENT) Hmmm, Leziad has a point. Variant rules either add, or change, something in the overall framework of D&D. Not all rules fit, regardless what intention of the rule is. After all if you augmented it enough it's not a variant rule, it's a new system. -- Eiji-kun (talk) 05:50, 6 March 2015 (UTC)
- Eiji, that whole idea of "I'm not the target audience for this, and so I'm going to hold my rating a bit" is pretty much what I was trying to go for. I may well steal some of the 'you probably shouldn't be rating this' bits when I work up whatever next form this is likely to take.
- Leziad, for the 2e case my point was that I don't think such a thing could be done without slowing down combat. Downrating because of the slow down would be problematic as a result, because it's part and parcel of the whole thing. But if the slow down wasn't discussed, or it was instead praised as a speeding up, or if it was terribly worded and unclear then sure, downrate. Oppose even if it's bad or misleading enough. I don't want to remove the quality considerations, and if that needs to be made more clear I'll do that. There's a line between 'this is a bad rule because it promotes something I don't like' and 'this is a bad rule because it is poorly written / works poorly with all of these other unchanged subsystems that aren't mentioned at all' that I'm trying to stop people from crossing over. If you have wording suggestions, I'm happy to steal them.
- And I support straight up deletion for inappropriate articles, so I'm not sure that they should really be discussed in ratings... but sure, oppose those too if it's a borderline case. - Tarkisflux Talk 08:30, 6 March 2015 (UTC)
- Honestly, if you're going to be giving something a bad rating, you should hold off until you actually discuss it and make an effort to iron out its faults. If someone makes a rule that's only broken by an overly-literal RAW reading or as a result of obscure/mostly ignored rules and you say "Feat is mechanically broken and does not function, 0/4" instead of "It's impossible to qualify for this feat because of this rule: blahblahblah", then you're just being a jerk. You might as well bite a cow's arse and say "This is the worst steak ever!". When it comes to variant rules, you need to get it through your head that not everyone needs them. If you think full attack as a standard action is OP because you play a dwarvern rogue with a +5 flaming holy composite longbow, then you're obviously not someone who needs it to be useful. I mean, I consider the injury variant to be inherently broken because it turns Marshal into an invincibility button, Paladins become unstoppable, and other such nonsense, but I don't rate that poorly because it's obviously incompatible with certain games. LenKagetsu (talk) 19:25, 7 March 2015 (UTC)
- Len - While I prefer discussion before downrating (because courtesy), it's not actual policy and I don't think it should be. It has been repeatedly demonstrated that people don't stick around for as long as their work does, and asking raters to wait a bit for them to respond is just yet another hoop to jump through for page ratings that new users are likely to get tripped up on. If you disagree and want to start a separate topic about it, feel free. Policy reflects consensus in this case, and consensus can change.
- As for the variant bits, I suspect we're mostly on the same page. If the injury variant didn't call out its potential problems with some game sets or purported itself to be a replacement suitable for all games, I'd consider that a failure of the article and downrate appropriately. I suspect Leziad would too based on his framework comments.
- I'm basically saying that someone should make a significant effort to improve on an article before giving it a low rating. If you can see faults, you can take time to point them out and let them fix them. If they've been AWOL for months though, then slap them all you want. LenKagetsu (talk) 23:14, 7 March 2015 (UTC)