You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of people are looking for an Axe because it was recommended on some wowhead guide, however this is not true and e.g. paladin can use sword instead as stats wise it will be exactly the same because buyer determines stats with missive.
Can you add an ability to scan for recipe that is not learned? I am constantly writing to people explaining that they can use sword instead.
The text was updated successfully, but these errors were encountered:
local function canShowScanButton()
return cur.recipe and cur.recipe.learned and not cur.recipe.isRecraft
end
to this:
local function canShowScanButton()
return cur.recipe and not cur.recipe.isRecraft
end
Don't have time to change something like this properly. Would want it piped through a bit more so the default response doesn't say "I can craft it". It won't work with the 'Scan all recipes' button, but I assume you aren't using that at this point in the expansion anyway. The above change should make the checkbox show up so you can check it, and I think that's enough for orders to start showing up. You can then middle click to open chat with the person.
I'm currently adding a 'Custom Explanations' button that will let you configure messages and send them from the right click context menu in the chat frame, so once that's released, probably tomorrow, you can save a message there. Middle click to start a chat/say hi, then right click their name in chat to send your saved explanation.
A lot of people are looking for an Axe because it was recommended on some wowhead guide, however this is not true and e.g. paladin can use sword instead as stats wise it will be exactly the same because buyer determines stats with missive.
Can you add an ability to scan for recipe that is not learned? I am constantly writing to people explaining that they can use sword instead.
The text was updated successfully, but these errors were encountered: