My hope is that this means my sniper will continue to evaluate vendor items bought by something besides gold in the same way as always. Specifically, I posted a Savage Blood (vendor sold for primal spirits) for 1g, and it showed up immediately on my sniper (I was able to snipe it myself, yay!). One last note: For my own peace of mind, I tested this against an item that is sold by a vendor, but not for gold. When VendorBuy is higher than (or equal to) minprice, the check returns invalid, and the original string is once again used. If an item DOES have a VendorBuy price, it will return that price when it's lower than the minprice (market price). In that case, the rest of the string is used, which is the original string. If an item doesn't have a VendorBuy price (cost of buying from vendor), then the string "check(minprice - VendorBuy, VendorBuy)" will return invalid. The "first" function returns the first valid price. If the market value is below the vendor sale price, I can simply let the rest of the string evaluate the price as normal. Specifically, it sets the max sniper price to the vendor sell price for any item whose market value is above the vendor sell price. So I made an updated string to filter them out.
I don't want to buy any vendor purchased items with sniper, at least not any that you can buy with gold.
People posting them for 10g would trigger sniper, even though they cost 50s from the vendor. One common example is the dragonhawk hatchlings. These items would have a listed market value high enough to trigger my sniper string when they were posted at more reasonable prices. The problem I was having is that my sniper was bringing up a lot of vendor purchased items. The exact percentages and prices in this string are from the original, but you should consider setting them according to your own server/experience. TL DR: Evaluates vendor sold items by vendor price instead of market price if (market price > vendor price)ĭisclaimer: While I did test this, I would remind everyone to use common sense when sniping and always test new TSM strings before using them regularly. Here's the new string: first(check(minprice - VendorBuy, VendorBuy),check(minprice - 100000g, 90% minprice, check(minprice - 50000g, 80% minprice, check(minprice - 10000g, 60% minprice, check(minprice - 5000g, 50% minprice, check(minprice - 1000g, 30% minprice, check(minprice - 500g, 20% minprice, check(minprice - 50g, 10% minprice)))))))) Here's the original sniper string: check(minprice - 100000g, 90% minprice, check(minprice - 50000g, 80% minprice, check(minprice - 10000g, 60% minprice, check(minprice - 5000g, 50% minprice, check(minprice - 1000g, 30% minprice, check(minprice - 500g, 20% minprice, check(minprice - 50g, 10% minprice)))))))įor reference, here is the custom price "minprice" used: max(min(DBHistorical, DBGlobalMarketAvg, DBGlobalHistorical, DBRegionMarketAvg, DBRegionHistorical), VendorSell)
This has already made me a lot of gold, and I've only been using it for a few weeks. If you're a regular in this subreddit, you will certainly recognize it. I found out about it from /u/xionikandsheyrah in a YouTube video. This TSM sniper string was originally created by /u/BilisOnyxia. The min function appears to ignore invalid prices without error.ĮDIT 2: /u/BilisOnyxia points out that altering the custom price will filter items at different percentages of VendorBuy as specified in the string, instead of just showing everything under VendorBuy price (which my string does)įirst things first, I'd like to give credit where it's due. EDIT: As pointed out by /u/Trimestrial, you can simply add VendorBuy to the min function in your custom price.
0 kommentar(er)
