|AnS 2.1.2 release||493.13 KB||Jun 14, 2020||1.13.4 +1||343||Download|
|AnS 2.1.1 release||491.47 KB||May 17, 2020||1.13.4 +1||522||Download|
|AnS 2.1 release||490.29 KB||May 13, 2020||1.13.4 +1||244||Download|
|AnS 2.0.6 release||125.15 KB||Feb 9, 2020||8.3.0||759||Download|
|AnS 2.0.5 release||125.01 KB||Feb 3, 2020||8.3.0||300||Download|
|AnS 2.0.4 release||124.64 KB||Feb 1, 2020||8.3.0||190||Download|
|AnS 2.0.2 release||121.43 KB||Jan 24, 2020||8.3.0||295||Download|
|AnS 2.0.1 release||118.61 KB||Jan 21, 2020||8.3.0||247||Download|
|AnS 2.0 release||118.04 KB||Jan 20, 2020||8.3.0||140||Download|
|AnS 220.127.116.11 release||136.58 KB||Nov 25, 2019||8.2.5 +1||1,016||Download|
|AnS 18.104.22.168 release||136.70 KB||Oct 12, 2019||8.2.5 +1||359||Download|
|AnS 1.0.7 release||135.01 KB||Sep 6, 2019||8.2.0 +1||417||Download|
|AnS 22.214.171.124 release||126.59 KB||Aug 27, 2019||8.1.0 +1||920||Download|
|AnS 126.96.36.199 release||125.72 KB||Jan 25, 2019||8.1.0||969||Download|
|AnS 188.8.131.52 release||125.63 KB||Dec 29, 2018||8.1.0||568||Download|
|AnS 184.108.40.206 release||125.63 KB||Dec 27, 2018||8.1.0||235||Download|
|AnS 220.127.116.11 release||125.35 KB||Nov 22, 2018||8.0.1||798||Download|
|AnS 18.104.22.168 release||125.23 KB||Nov 3, 2018||8.0.1||498||Download|
|AnS 22.214.171.124 release||125.10 KB||Oct 26, 2018||8.0.1||424||Download|
|AnS 126.96.36.199 release||148.33 KB||Oct 16, 2018||8.0.1||309||Download|
|AnS 188.8.131.52 release||145.63 KB||Sep 28, 2018||8.0.1||691||Download|
|AnS 1.0.6 release||145.01 KB||Sep 27, 2018||8.0.1||109||Download|
|AnS 184.108.40.206 release||95.34 KB||Sep 18, 2018||8.0.1||458||Download|
|AnS 220.127.116.11 release||42.74 KB||Sep 13, 2018||8.0.1||308||Download|
|AnS 18.104.22.168 release||42.96 KB||Sep 9, 2018||8.0.1||280||Download|
|AnS 1.0.5 release||40.97 KB||Sep 8, 2018||8.0.1||130||Download|
|AnS 22.214.171.124 release||38.10 KB||Sep 7, 2018||8.0.1||161||Download|
|AnS 1.0.4 release||38.09 KB||Sep 7, 2018||8.0.1||107||Download|
Need help, have questions, suggestions or just found a bug?
I just updated to 2.1 and stuff is broken
If you just updated through curse or twitch, then please restart your WoW Client first. As quite a bit has changed.
AnS [Auction Snipe]
A lightweight addon for WoW auction sniping
Must have at least one of the below for retail:
* Undermine Journal
In 2.1 Settings Have Moved!
Settings are no longer under Esc -> Interface -> Addons -> AnS
Instead use the new Minimap button to access all stuff AnS related.
Billis String in 2.1 for Classic
Define a custom source named minprice with value:
In the global Max Price / Boolean Filter or in a Sniper Operation Max Price / Boolean Filter:
max(ifgte(ItemQuality, 1, minprice * ifgte(minprice, 250g, 80, ifgte(minprice, 100g, (minprice - 100g) * (80 - 70) / (250g - 100g) + 70, ifgte(minprice, 50g, (minprice - 50g) * (70 - 60) / (100g - 50g) + 60, ifgte(minprice, 10g, (minprice - 10g) * (60 - 40) / (50g - 10g) + 50, ifgte(minprice, 5g, (minprice - 5g) * (40 - 30) / (10g - 5g) + 30, ifgte(minprice, 1g, (minprice - 1g) * (30 - 10) / (5g - 1g) + 10, 0)))))) / 100, 0), VendorSell - 1c)
Note for 2.x Regarding Retail Max Percent
Max percent may need to be adjusted higher than necessary if looking for equipment with the same id and varying levels of iLevels. Since, the initial browse query filtering is based on the base item id in pricing in TSM / TUJ / Auctionator. However, the final filtering is based on the item id + bonus ids, but only if the initial browse group is considered. You can combat cases of this by using a operation that will override the percent check in the final case and filter out the lower ilevels that are not really deals.
- Sniper Operations must be set before starting a sniping session
- Changes to sniper operations during a running sniping session has no effect.
To update sniper operations stop and restart the session.
Pre-built Groups for:
Allows for quick settings of:
- Max Percent
- Max Buyout
- Min iLevel
- Min Quality
- CLevel Range
- Name filter for further refinement
How to Buy & Other Controls
Double click an auction list item, and ba da bing, ba da boom. It will purchase it if it can.
Or use the new mouse wheel macro creation under Ans Minimap Button -> Settings -> Macro
Settings -> Sniper -> Price Source
The sniper price source must return a numerical value and can use Custom Sources as well in it.
The sniper price source is used for the default percentage calculations.
Settings -> Sniper -> Max Price or Boolean Filter
The max price or boolean filter here is the global version. Sniper operations ignore this value and use their own instead.
You can either return a numerical value here and it will work as a max price cut off, or return a boolean value such as: ppu lte 20g
Lua operators can be used
>=, ~=, ==, <=, <, >, not, and, or, -, +, *, \
Predefined functions for use in strings:
first, check, iflte, iflt, ifgte, ifgt, ifeq, ifneq, avg, min, max, mod, abs, ceil, floor, round, random, log, log10, exp, sqrt, eq, neq, bonus, startswith, contains,
Predefined Item Variables:
vendorsell, vendorbuy, percent, ppu, stacksize, buyout, ilevel, quality, tsmId, id
Predefined TUJ Variables:
tujmarket, tujrecent, tujglobalmedian, tujglobalmean, tujage, tujdays, tujstddev, tujglobalstddev
Predefined TSM Variables:
dbmarket, dbminbuyout, dbhistorical, dbregionmarketavg, dbregionminbuyoutavg, dbregionhistorical, dbregionsaleavg, dbregionsalerate, dbregionsoldperday
Most variants on TSM variables are also available such as DBRegionMarketAvg, ItemLevel, etc. in 2.1
Predefined AnsAuctionData Variables:
ansmin, ansrecent, ansmarket, ans3day
Using Predefined bonus function in 2.1
The bonus function will check to see if an item has a specified bonus id
You can pass it the following as an example:
If the above has the bonus 100 then it will return the first value of 110g, otherwise it will return the secondary value of 0. If only a bonus id is provided and no values are passed, then it will return just true or false.
The function parameters:
Settings -> Custom Sources (Previously called Custom VARS)
Custom sources can be anything you want them to be and are case sensitive.
They can be referenced in any other area of AnS from operations to global settings.
You can do the following just like TSM:
Example of Price Source
avg of tujmarket and tujrecent
min of tujmarket and tujrecent
min of dbmarket, tujmarket, tujrecent, dbregionmarketavg
Using custom math in strings
You can use any of the standard lua operators for math such as: * (multiply), \ (divide), + (add), – (subtract)
0.25 * min(tujmarket,tujrecent);
Boolean Filtering Examples
Only show auctions less than 50%
percent lt 50
Only show auctions with a ppu less than equal to 5g
ppu lte 5g
Only show items with ilevel greater than 350
ilevel gt 350
Only show items with a stacksize of greater than equal to 20
stacksize gte 20
Only show items that are rare and above
quality gte 4
Combining More Than One Boolean Examples
quality common or better and ppu less than equal to 10g
quality gte 1 and ppu lte 10g
iLevel greater than 350 and percent less than 50
ilevel gt 350 and percent lt 50
One or the Other Boolean Examples
Only accept items that are less than 1000g or above 5000g ppu
ppu lt 1000g or ppu gt 5000g
Only accept items with stacksize 200 or ppu gt 200g and ppu lt 250g
(stacksize eq 200) or (ppu gt 200g and ppu lt 250g)
What is it?
It is a core library used for various things. But mainly for AnS [Auction Snipe].
It also handles the configuration of all AnS related addons.