453 - Search/filter zone for all recipes in that zone
ARL Version (ie: 1.0 Beta 9):
ARL Revision (ie: r1100):
What is the enhancement you currently have in mind?
The ability to search/filter a zone for all recipes available in that zone not just the recipes that the current toon with its current profession/s can learn. The idea is that I can enter into a zone on any toon and regardless of that toons profession be able to search for every recipe that is buy able/mob dropped in that zone regardless of which profession it belongs to.
Do you have a method of how this would be implemented?
ARL should scan all toons like normal and save the list of what recipes the toons know and what they don't know (filtering such a rep level and specialisation should probably be removed so a complete list can be generated). This then should be exported to a master list in which you can refine how you want to display unknown recipes of all your toons such as by zone, skill level, mob drop, vendor buy etc.
How critical is this enhancement?
Not critical at all, take your time.
| User | When | Change |
|---|---|---|
| Ackis | Tue, 24 Mar 2009 18:29:12 | Changed milestone from None to Future Release Changed component from None to Filtering |
| Ackis | Tue, 24 Mar 2009 18:28:30 | Changed status from New to Accepted |
| BWMerlin | Mon, 23 Mar 2009 17:09:17 | Create |
- 1 comment
- 1 comment
Facts
- Last updated on
- 27 Mar 2009
- Reported on
- 23 Mar 2009
- Status
- Accepted - Problem reproduced / Need acknowledged.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Medium - Normal priority.
- Component
- Filtering
- Milestone
- Future Release
Reported by
Possible assignees
-
- Manager
- Author
-
- Author
-
- Author
-
- Author
-
- Former author
Votes (Total: +1, Average: +1.0)
-
Votes +1
- #1
AesirRising Fri, 27 Mar 2009 14:23:28This is going to be a lot of data. Output into chat will be a problem. On screen display would be unwieldy, but perhaps a filter option for the ARL main frame that filters by zone would be a valid solution.
If the enhancement request is accepted as proposed, as a first step/pass on the implementation, I'd like to see it generated as a delimited text dump that includes source data (e.g., zone, vendor/mob name, waypoint) for import into a spreadsheet or desktop database. This bypasses UI usability considerations while still supplying the data to the user. [edit: for that matter, I've not tried this, but perhaps the existing data dump to text feature provides a multi-step solution already...hmm.]