I’ve bashed the LFD Call to Arms as not going far enough, and not being an effective solution; and as a blogger with no leverage or responsibility in the game that is easy to do. So instead of a blog post which grumbles, here is a blog post with a suggestion.
Item stat based rules for Need vs Greed, for group roles.
The random dungeon finder tool now filters on armour type, but no further. I’m proposing that there is an algorithm which can filter the Need vs Greed option even further, so that gear is far less likely to be awarded to the wrong role. Using this the players would be getting gear with a far higher (but not imperfect) degree of focus on the role they joined to execute.
We have four roles and a range of special cases for gear within the class combinations created by those roles (Range DPS, Melee DPS, Tank, and Heal). It’s a bad thing to see a Need roll on an item which will never be used, such as a Death Knight rolling need on a Plate item which has Int on it, or a Hunter rolling on a staff with Spirit.
Here is a suggested solution to improve the algorithm which filters Need vs Greed selection:
Use role based filters for all Need role which restrict based upon:
- Apply a primary stat filter, where the item must have that stat present.
- Apply a secondary stat filter, where any one of the listed stats must be present.
- Apply a secondary stat filter, where if any of the listed stats are present then the character is excluded from the Need roll.
This allows for the armor type restriction to hold as currently implemented, and the armor type restriction would still act as a restriction. It allows trinkets, rings, necks and other non-armor type items to be classified using the stats assigned to the item. This mean that it is not an arbitrary assignment of priority, but one based on the stats which the item has and how they are valued as recognised by item weightings.
The rules allow for an item within a armour type that a role might current role on to be corrected, like Int plate vs Dodge plate, or a trinket with only one stat, and allows for ignoring the Stamina values on gear. While this might disadvantage Tanks slightly, I am not sure of many items which would otherwise be selectable which would not also be valid choices for DPS characters – so the degree of impact is less.
All that we need to do is decide on the primary stat for each class & role combination, set a valid list of secondary stats, and also set some stats to exclude. It is worth noting that the inclusion of a stat in the included or excluded list is not mean to dictate a priority amongst them, it just means that this is a potentially valid stat for the class-role.
For example: It would be a shame for a range Tank to miss a role for an upgrade with Dodge on it just because a DPS in the same group rolls need.
The syntax is = Class Role: Prime-Stat / Stats Included / Stats Excluded
DK mdps: str / mast, crit, hit, expertise, haste / !int, !spirit, !dodge, !parry, !block
Pally mdps: as above
War mdps: as above
Druid mdps: agi / mast, crit, hit, expertise, haste / !int, !spirit, !dodge, !parry, !block
Rogue mdps: as above
Shaman mdps: as above
DK tank: str / dod, parr, mast, exp, hit / !block, !int, !spirit
Druid tank: agi / dod, mast, exp, hit / !block, !parry, !int, !spirit
Pally tank: str / dod, parr, block, mast, exp, hit / !int, !spirit
War tank: as above
Druid rdps: int / spell power, hit, crit, haste, mastery /
Hunter rdps: agi / hit, crit, haste, mastery / !int, !spi
Mage rdps: as per Druid
Priest rdps: int / spell power, hit, crit, haste, mastery, spirit /
Shaman rdps: as per Druid
Warlock rdps: as per Druid
Druid heal: spi/ int, mastery, crit, hate, spellpower / !hit
Pally heal: as above
Priest heal: as above
Shaman heal: as above
As a basic this does it. It could be expanded to understand the ratio of Spirit to Int in comparison of caster items, where one is valued to dps higher than healers.
It could be expanded to ignore the rules if the person who could roll Need already has an item in that location which exceeds the item weight by ~20%. Meaning a player could not roll Need on a ilevel: 333 item if they already have a ilevel 356 in that location. For them it becomes a forced Greed. That might mean that another player is the only one who can greed, or that nobody can roll need. You could also open the rolling so that if nobody is normally allowed to roll Need due to this rule, then the system lets them role Need if it is in their armour type. This way a offset item goes to somebody who might actually use it, not to disenchant or vendor.
And I’m sure there is a huge range of exceptions that might apply for funny items. No way in hell I was going to try and parse all of the WoWHead data to validate this.
On plan I think this is a solid idea. What do you think?