Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mark equippable quest rewards #21

Open
kennumen opened this issue Jul 21, 2012 · 1 comment
Open

mark equippable quest rewards #21

kennumen opened this issue Jul 21, 2012 · 1 comment

Comments

@kennumen
Copy link
Collaborator

Can your warrior equip a 2handed axe? Can your hunter hold a staff? ... Wait, do druids ever support 2H maces and did I remember to weapon train him?

Obviously the biggest gain here is for weapons (and perhaps the occasional brainfart). List out in some way which rewards can be equipped by the bot.

Personally I'd lean towards 2 lists (in the same party chat line). E.g.:
"[QuestCompletedName] rewards: I could equip [X] [Y] [Z] or sell [A] [B]"
"[QuestCompletedName] rewards: I could sell [A] [B]"
"[QuestCompletedName] rewards: I could equip [X] [Z]"

Feel free to be creative. Listing sellables by value and/or equippables by 'score' (most likely to be an upgrade first).

@kennumen
Copy link
Collaborator Author

Better idea. Integrate 'IsBetterEquip()' [not actual function name] from Equip Auto and mark quest rewards something as following:
[QuestRewardItemLink] [eq+) - [ItemLink] [eq-) - [ItemLink] [ne) - [ItemLink] [other)

Legend:
(eq+) - (in green color) - Equippable, improvement
(eq-) - yellow/orange text - Equippable, you have better equipped already
(ne) - red text - cannot equip
(other) - blue text - is not an equippable item (could be water, bullets, ...)

@edit as a bonus it would also increase interest to tinker with equip comparison code.
@edit [eq+) == (eq+) but (text) following [text] makes a link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant