Get an Epic Experience with Premium


Boss Encounters Login to Add Favorites
  • World of Warcraft
  • 7,374 Monthly Downloads
  • Supports: 4.1
  • 590,609 Total Downloads
  • Updated 04/29/2011
  • Created 07/20/2010
  • 240 Favorites
  • Project Site
  • Comments
  • Release Type: Inactive
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: v1.3
Support development! **

About AtlasLoot_AdvancedSearch

AtlasLoot Advanced Search is a plug-in for the AtlasLoot Enhanced addon. AtlasLoot Advanced Search enhances AtlasLoot by providing additional search modes, enhancing existing search functionality, and more control over some of the common tasks in the loot browser - all via seamless integration.


  • Seamless integration: very small, light-weight, non-intrusive. The look-and-feel of AtlasLoot is not affected in any way.
  • More Search Options: Allows you to search for loot based on additional criteria, such as equipment slot or instance/zone where it can be found.
  • More Intelligent Search: Supports multiple ways of combining search terms, to further narrow down your search. Want to search for a chest piece that drops in Icecrown Citadel? Or perhaps search for all items which go into the hands, feet, or neck slots....AtlasLoot Advanced Search will make it easy.
  • Easily Extendable: Easy to add new search modules if you need a search mechanism that isn't available. AtlasLoot Advanced Search was designed and written from the ground up with extensibility in mind. Adding additional functionality or changing the behavior of any of its default search modules is easily accomplished without modifying any files in AtlasLoot or AtlasLoot Advanced Search. (Basic knowledge of Lua programming recommended.)

Bug reports:

Forum thread:

Latest News


Searching with AtlasLoot Advanced Search isn't complicated, but there are a few things to know in order to get the most out of your searches.

  • To narrow down your search results, combine search terms using and or +. (e.g. Sanctified and waist, Trial of the crusader and off-hand, etc.)
  • To broaden your search results, combine search terms using or or | (that's the pipe character). e.g. Hands or wrist, Icecrown Citadel or Ruby Sanctum
  • To combine multiple searches into one, use parenthesis to tell the searcher which parts should be grouped together. For example, let's say you want to search for items that drop in Trial of the Crusader or Icecrown Citadel, but you only want to see items that go into your head slot. This would be considered a combination search, because you are combining multiple criteria into one search.

    Because of this, entering Trial of the Crusader or Icecrown Citadel and Head into the search box isn't going to return the expected results - the searcher is now confused because you might have meant Search for all items from trial of the crusader, and also search for all head-slot items from icecrown citadel.

    The correct way to type this search into the box would be: Head and (Icecrown Citadel or Trial of the Crusader). Now the searcher knows that it should look only at head items, then only show the item if it comes from Icecrown Citadel or Trial of the Crusader.

  • If you ever experience a problem with AtlasLoot advanced search, such as an error message when you attempt to perform a search, you can easily disable Advanced Search without needing to log out or reload your UI. Click the arrow button next to the search box in AtlasLoot, and check or uncheck the "Enable Advanced Search" item.

There are currently four different search modes supported by AtlasLoot Advanced Search - searching by name, searching by item slot, searching by zone name, and searching by weapon type. Each mode can be turned on or off by clicking the arrow button next to the search box in the AtlasLoot window, and checking or unchecking the search mode entry. Because these searches must check a lot more data than a normal search, they will often take much longer than a normal search would. This is expected, and does not mean your game has frozen up. Some searches can take as long as 10 to 15 seconds

  • Searching by name works much the same as the default AtlasLoot search. You type all or part of the name of an item into the search box, and you are shown the items that match the value you entered.
  • Searching by zone name works much like searching by item name, except that it will match your input against the name of the zone where the item can be found. For dungeons, only the name of the dungeon is recognized (boss names and subzones are not supported).
  • Searching by item slot works by checking the value you enter against the name of the item slot that the item is used in. If the item isn't wearable (for example, a mount), it will be ignored by the search completely. Here is a list of the item slot names that AtlasLoot Advanced Search will recognize:
    • Head
    • Neck
    • Shoulder
    • Back
    • Chest
    • Shirt
    • Tabard
    • Wrist
    • Hands
    • Waist
    • Legs
    • Feet
    • Ring
    • Trinket
    • Off-hand (or Held in Off-hand)
    • Relic
  • Searching by weapon type works by matching the text you enter against the text that is displayed as the "type" for anything that goes into your hands (this includes shields, ranged-slot items, and projectiles). Here is the list of weapons types that AtlasLoot Advanced Search will recognize:
    • Axe
    • Bow
    • Crossbow
    • Dagger
    • Gun
    • Mace
    • Polearm
    • Shield
    • Staff
    • Sword
    • Thrown
    • Wand
    • Fist Weapon

r142 | orgevo | 2011-04-29 08:46:25 +0000 (Fri, 29 Apr 2011) | 1 line
Changed paths:
   A /tags/v1.3a (from /trunk:141)

** tagging for beta release; wanna see if anyone else still sees any lua errors before doing the final release for 4.1
r141 | orgevo | 2011-04-29 08:44:39 +0000 (Fri, 29 Apr 2011) | 6 lines
Changed paths:
   M /trunk/AdvancedFilter.lua
   M /trunk/AtlasLootFixers.lua
   M /trunk/Core.lua
   M /trunk/ItemQualityModule.lua
   M /trunk/NameSearchModule.lua
   M /trunk/SearchParser.lua
   M /trunk/SearchResults.lua
   M /trunk/SlotSearchModule.lua
   M /trunk/WeaponTypeSearchModule.lua
   M /trunk/ZoneSearchModule.lua

- fixed most of the remaining compatibility issues with the rewrite of AtlasLoot
** items are no longer appearing in the search results multiple times under the same header
** fixed a couple of lua errors that were introduced by some more recent changes to AtlasLoot's API

- all debugging log messages which are in time-sensitive areas (thus impact performance during development) are now controlled by a single variable that allows them to be turned on/off on a per-file basis, or all at once

r139 | orgevo | 2011-04-28 16:19:50 +0000 (Thu, 28 Apr 2011) | 1 line
Changed paths:
   M /trunk/Core.lua

- fixed another typo causing packaged versions of the addon to trigger lua errors that didn't show up during testing
r138 | orgevo | 2011-04-28 16:12:43 +0000 (Thu, 28 Apr 2011) | 1 line
Changed paths:
   M /trunk/Core.lua

- fixed mismatched packager tags (@debug@ / @end-do-not-package@) that causing lua error only once the addon had been packaged by
r136 | orgevo | 2011-04-28 08:21:14 +0000 (Thu, 28 Apr 2011) | 1 line
Changed paths:
   M /trunk/AtlasLootAdvancedSearch.toc

- whoops, version number was already incremented
r135 | orgevo | 2011-04-28 08:18:26 +0000 (Thu, 28 Apr 2011) | 1 line
Changed paths:
   M /trunk/AtlasLootAdvancedSearch.toc

- updated toc; no incompatibilities with 4.0.1 patch
r134 | orgevo | 2011-03-21 17:17:42 +0000 (Mon, 21 Mar 2011) | 1 line
Changed paths:
   M /trunk/AtlasLootAdvancedSearch.toc

- updated .toc with next version number


First Previous Page 4 of 4 Next Last
  • #9
    1.189 does not work with the present version of atlas.
  • #10
    Could you provide a little more information? I just tried a test, by removing both AtlasLoot and AtlasLoot_AdvancedSearch from my addons folder, then used the curse client to download the current version of each (by right-clicking on each and selecting "Update"). I started the game and AtlasLoot_AdvancedSearch seem to be working fine.

    - Looking at my curse client right now, the current version of AtlasLoot is v5.11.03a - is this the version of AtlasLoot you're using?
    - By "not working", what is happening, exactly? Are the AtlasLoot_AdvancedSearch menu items appearing in the AtlasLoot search options menu? (click the arrow next to the search box).
    - If my menu options are being shown, is it just not returning any results? Is that what "not working" means? Help me out here :)
  • #11
    Actually, it's probably best enter a ticket for whatever issue you're seeing, so that it can be tracked properly:
  • #8
    And version 1.0 is born! May it see long life and good health!!
  • #7
    OK, version 0.8 should have all of those lua errors resolved, and all 3 search modules should be returning accurate results.

    Hit me back if you run into any problems with this release.
  • #6
    After updating to 0.7beta I suddenly got A LOT of error messages from other addons right after logging in. Are you doing anything 'special' with Ace library
  • #4
    If you uncheck enable adv search, its gone and you cant get it back until you reboot the game.

    What I don't understand is how you get it to work and then I use it and it doesn't??
  • #5
    Which version are you using? In beta 0.6, unchecking 'Enable Advanced Search' should remove the search modules from the context menu, but it should not remove the 'Enable Advanced Search' menu option. Thanks for the report, I'll look into it.

    To answer your question, the discrepancy between the behavior you and I see is almost always caused by the process of packaging the addon for publishing to For example, there is a way for me to have remove bits of code I specify when it creates the .zip file for download. This is usually done in cases where the data that will be exposed isn't readily available during testing (for example, let's say I was working on the menus for their new realID system, but I don't have any realID contacts). I need some test data to work with, so I might hardcode a bunch of dummy entries to fill the menu options during development. In the released version, that development code would be stripped out by the process that creates the .zip files.

    So every now and then, you'll run into a situation where the code only runs correctly with the dummy code. When that happens, most times the developer won't even be aware of the issue until someone posts a comment or bug report about it (since our copy of the addon still uses the dummy data). I generally move my working code out of my addons folder, then install it from curse to protect against this exact thing.....but sometimes it gets lost in the shuffle...

    Hope that answers your question.

  • #1
    I have everything checked and I put in "Dislodged Foreign Object" and get back "AtlasLoot:No match found for Dislodged Foreign Object." It drops off Rotface.
    Will it not find the it?
  • #2
    Thank you for letting me know - I wasn't aware that the "item name" search module wasn't functioning any longer. I'm looking into it now.
  • #3
    OK, found and fixed the problem. The fix will be in the 0.6beta, which contains a few other new features as well (see the changelist for more details).

    Getting there! Release coming soon I think :)
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Leaguepedia PAX Skin Giveaway