Hi, i think my BTM Scanner dont work right. i dont want it to search for weapons/armor. so i activated the filter under configure/filters/ignoreItemQuality, did a hook on "Enable quality-filtering" and a hook by armor/weapon from "poor" to "artifact". but when i start the bottom scan it still shows me weapon/armor.
so i wanted to try on a baserule with that, but when i type "/btm baserule" it says Unknown command [baserule]
Make sure you enable the filtering for each of the evaluators you're using as well. (activate Filter for module: appraiser etc.)
Baserules were replaced in BtmScan with evaluators, which are more modular and can be separately configured, so the /btm baserule command doesn't exist anymore.
That should work as you have it set up to stop any armour sales. It works in Advanced too, that's not a problem. At the moment I'd suspect it is to do with the german version, yes. Would you be able to see whether it returns armour of each rarity colour? Perhaps we don't have the right localization for a specific type? Or perhaps it's the word armor itself...
The item types are hardcoded (in English) in FilterItemQuality.lua. Probably best to iterate over GetAuctionItemClasses/SubClasses on startup, not least because Blizzard have changed the layout of the AH categories at least once recently. :)
Nah, it was that we hadn't localized it properly yet that was causing the problem, I'm sure the german version works fine for most other things. I'm glad you found a way to get it working properly for now though!
I am experiencing the same problem. I am not willing to install the English language pack though. ^^ Like Adi, I have checkmarked every quality for armor (and others, too: quiver, projectile, recipe...), and I have enabled filtering for module:resale, but BTM will always pop up with armor, weapons or recipes for resale. The quality doesn't seem to be the problem, I am getting popups for whites, greens, blues, and I guess there would have been epics, too, if I hadn't set the maximum price to 20g.
Hope you can fix this soon, the feature is just to good to not be used. =)
Classic should be fully localized still. With Advanced we are attempting to get it approximately feature complete and ready for a release version, at that point we'll start working on the localization, but for now we're just trying to get everything in it working the way we want. I'm sorry about that, but it seems the right way to prioritize things just now. If you need the full localization immediately it's probably better if you use Classic (but like you say, lots of the features in Advanced are just too good to not be used!)