No edit summary |
Lord Xivor (talk | contribs) No edit summary |
||
| Line 15: | Line 15: | ||
I vote in favor. Builds should be voted on their effectiveness within their class. Comparing between classes is impractical and illogical. Many people are not going to create a brand new character and spend weeks leveling it up and spend maybe what? 10-20k on skills and armor and weapons just to farm one area? Just because a build is relatively slow or has less damage output doesn't make it a bad build. If you can safely farm an area without too much hassle with the build it should be approved. [[User:Matthew Edmund|Matthew Edmund]] 01:41, 16 September 2007 (CEST) |
I vote in favor. Builds should be voted on their effectiveness within their class. Comparing between classes is impractical and illogical. Many people are not going to create a brand new character and spend weeks leveling it up and spend maybe what? 10-20k on skills and armor and weapons just to farm one area? Just because a build is relatively slow or has less damage output doesn't make it a bad build. If you can safely farm an area without too much hassle with the build it should be approved. [[User:Matthew Edmund|Matthew Edmund]] 01:41, 16 September 2007 (CEST) |
||
| + | :I agree. The way the voting goes on here, builds are rated as inferior if they do not meet the effectiveness of a similar build using a different profession. I disagree with this, as I feel that if someone is looking for a Warrior farming build, they are not going to look in the Assassin category for the build. In the case that upset me, I had a Dervish build that was similar in most ways to a Monk build. But no one that wishes to find a Dervish farming build is going to search for their Dervish builds in the Monk category, and no one that wants to farm an area that has their Dervish there are going create a Monk and level him and get him to that area for farming. They will want to farm on their Dervish. Therefore, whether the job can be done similarly or even better on a Monk is mute; the person is searching for a Dervish build, not a Monk build. I think profession bias needs to be done away with. - [[User:Lord Xivor|Lord Xivor]] 02:00, 16 September 2007 (CEST) |
||
Revision as of 00:00, 16 September 2007
k, let's make this final. —The preceding awesome-sauce comment was added by Skakid9090. 03:23, 12 August 2007 (CEST)
K. —ǥȓɩηɔɧ〚₮/ḉ〛 03:43, 12 August 2007 (CEST)
K. -- Armond Warblade
{{sysop}} 04:05, 12 August 2007 (CEST)
- Still doesn't really say anything specific about profession bias. I've seen a 0-0-0 rating on a warrior farming build because a 55 could do it faster. That shouldn't happen. Bluemilkman 04:12, 12 August 2007 (CEST)
- IMO that's a case of unreasonable voting and should be brought up with an admin. -- Armond Warblade{{sysop}} 04:48, 12 August 2007 (CEST)
- /agree with Armond here. If people want a great farming build, they use the best regardless of profession. If they want a good one, they use the best of the professions they have made available to themselves. Votes such as BMM's example should be brought to administrative attention, rather than creating a new policy and set of guidelines to deal with them. Some builds will farm better than others and deserve a higher rating than them. A Para might farm ok, but it should not be given a higher (or equal) score than a tested and true farmer simply because it is a Para. -
Krowman {{sysop}} 09:40, 12 August 2007 (CEST)
- /Agree with Krowman. While I agree that BMM's example probably constitutes an unfair vote, "Profession Bias," as defined by this policy isn't altogether unfair. Some professions are uniquely suited to specific roles, while others may not be suited to that role at all, and we have to acknowledge that. I think that this is probably the kind of problem that inevitably has to be dealt with on a case by case basis.
*Defiant Elements* +talk 09:12, 16 August 2007 (CEST)
- /Agree with Krowman. While I agree that BMM's example probably constitutes an unfair vote, "Profession Bias," as defined by this policy isn't altogether unfair. Some professions are uniquely suited to specific roles, while others may not be suited to that role at all, and we have to acknowledge that. I think that this is probably the kind of problem that inevitably has to be dealt with on a case by case basis.
- /agree with Armond here. If people want a great farming build, they use the best regardless of profession. If they want a good one, they use the best of the professions they have made available to themselves. Votes such as BMM's example should be brought to administrative attention, rather than creating a new policy and set of guidelines to deal with them. Some builds will farm better than others and deserve a higher rating than them. A Para might farm ok, but it should not be given a higher (or equal) score than a tested and true farmer simply because it is a Para. -
- IMO that's a case of unreasonable voting and should be brought up with an admin. -- Armond Warblade
- As impractical as it may seem, common sense should dictate over this type of subject. A build that uses a different profession but accomplishes the task as best as a build of that profession could with minimal downside may deserve a good rating, but a build that does that with a larger expense may not deserve the same rating. "It's the only build that can do that" doesn't really cut it in some cases, but in other cases it can, depending on the build's overall performance. — Rapta (talk|contribs) 18:23, 20 August 2007 (CEST)
- Agreed, builds should receive fair voting, and bad votes can be struck, but this policy is unneeded. I could make the downright BEST warrior healer, and by this policy, since it's the best healer a warrior could be, you'd have to vote it well. In Bmm's case, the vote itself seemed unfair, and should have been removed. Bob fregman 06:38, 21 August 2007 (CEST)
- As impractical as it may seem, common sense should dictate over this type of subject. A build that uses a different profession but accomplishes the task as best as a build of that profession could with minimal downside may deserve a good rating, but a build that does that with a larger expense may not deserve the same rating. "It's the only build that can do that" doesn't really cut it in some cases, but in other cases it can, depending on the build's overall performance. — Rapta
I vote in favor. Builds should be voted on their effectiveness within their class. Comparing between classes is impractical and illogical. Many people are not going to create a brand new character and spend weeks leveling it up and spend maybe what? 10-20k on skills and armor and weapons just to farm one area? Just because a build is relatively slow or has less damage output doesn't make it a bad build. If you can safely farm an area without too much hassle with the build it should be approved. Matthew Edmund 01:41, 16 September 2007 (CEST)
- I agree. The way the voting goes on here, builds are rated as inferior if they do not meet the effectiveness of a similar build using a different profession. I disagree with this, as I feel that if someone is looking for a Warrior farming build, they are not going to look in the Assassin category for the build. In the case that upset me, I had a Dervish build that was similar in most ways to a Monk build. But no one that wishes to find a Dervish farming build is going to search for their Dervish builds in the Monk category, and no one that wants to farm an area that has their Dervish there are going create a Monk and level him and get him to that area for farming. They will want to farm on their Dervish. Therefore, whether the job can be done similarly or even better on a Monk is mute; the person is searching for a Dervish build, not a Monk build. I think profession bias needs to be done away with. - Lord Xivor 02:00, 16 September 2007 (CEST)