Another suggestion\way of maybe going through this is creating an auction detector that wrote notes on who did what.
Ex:
Code: Select all
/mac Detect.mac "Fungus Covered tunic" "Flowing Black" "Mold" "FBSS"
then any auctions with the keywords above.. let's say these auctions were said.
blah blah1 auctions, 'WTB Fungus Covered Tunic"
blah blah2 auctions, "uhm rawr Want To Sell this thing called Fungus covered tunic 45k OBO"
blah blah3 auctions, "PC Flowing Black Silk Swatch?"
blah blah4 auctions, "PC FBSS!?"
all these would be picked up in the filter, and not neccessarily a bad thing.
If you wrote the detect to write the results into a log, you could simply open the log later and maybe read stuff like:
Code: Select all
[Fungus Covered Tunic]
(11:32pm 8/8/03) blah blah1 auctions, "WTB Fungus Covered Tunic"
(11:42pm 8/8/03) blah blah2 auctions, "uhm rawr WTS Fungus covered tunic 45k OBO"
[Flowing Black Silk Swatch]
(12:42pm 8/8/03)blah blah3 auctions, "PC Flowing Black Silk Swatch?"
[FBSS]
(1:42pm 8/8/03)blah blah4 auctions, "PC FBSS!?"
You could then go through the log later, see all the spam pertaining to each search criteria, and contact the person accordingly. Sure you'd see both WTS and WTB's, but this is off the top of my head the easiest way to detect all auctions for a certain item.
Having it autotell the guy is probably no good, You're better off just contacting them later and asking if they're still selling\buying the item.
Another thing you could easily implement is an anti-spam detector, if X person spams the same msg 20 times the duration you run the macro, you could have it log every person's name you see auction and not let it log the same person twice for the same item.