I would love the ability to reference the last successful sale price and the last price at which I posted an item. In low-volume/sparse markets, my own sales records are more useful information than the market/realm/region/global aggregate prices. When I'm posting, I'm often the only person to have posted the item in days or weeks.

In this situation, I find myself wanting to implement one of two very simple strategies:

1. Start with an intentionally high price and slowly lower it each time I post


2. Start with an intentionally price and slowly raise it each time I post

I favor (1) if the item is something I can't re-acquire easily (e.g., rare drop) and I favor (2) if the item is something I can (e.g., an old enchant that I can re-craft). The most straightforward pricing for these two would be something like:

1. 95% lastPostPrice (start high, slowly lower)


2. 110% lastSellPrice (start low, slowly raise)

Right now, I instead have to resort to price source hackery to do either of these things.

For (1), I might set the price to "90% DBMarket" and post it once at a very high price. If I'm the only one posting, my single post is enough to move DBMarket, so if it doesn't sell, 90% DBMarket will be slightly smaller each time I post it.

I would much rather be able to say what I want directly, which is more like "95% lastPostPrice".

Similarly, for (2), I resort to things like "125% avgSell" or "105% maxSell." The former sucks because the actual percentage by which I increase my posting each time gets smaller for every post after a successful sale. You can work out the math, but the the short of it is that each successful sale only increases my posting price by (P/N)%, where (1 + P)% avgSell is my posting price and N is the number of times I've actually sold the item (i.e., the hidden denominator in avgSell).

So, if my posting price is 125% avgSell and I successfully sell my 100th item then avgSell increases by 0.25%.

Again, I'd rather say "105% lastSellPrice" directly.

It would be great if there were new functions:

GroupAvg(), GroupMin() and GroupMax()

The idea of these functions would be that they take one argument (a price string) and apply that pricestring to any item in the same group as the item the function is called for and then calculate the average, minimum or maximum of that.

Here is an example:

Current content raid gear comes in many different variations, many of which are more or less the same, but still treated as different items.

Take "Diadem of the Highborne" for example:

I'll list a few of the different versions (there are quite a few more) aswell as potential DBMinBuyout values:

Item: DBMinBuyout:
i915 titanforged raidfinder - 150000g
i915 titanforged raidfinder + speed - 140000g
i915 titanforged normal mode - 110000g
i915 heroic + indestructible - 400000g

Now, if I were to use "50% DBMinBuyout" as my maximum price for sniper, the i915 heroic + indestrictible version would show up as long as it gets listed below 200k gold, even though there is an i915 titanforged normal mode version (which is arguably the same item) available at only 110k gold. So buying the i915 heroic + indestructible would be a pretty bad idea.

If those three functions were available, I could simply create a group that contains all the different i915 versions of the "Diadem of the Highborne" and set the maximum auction price for this group to "GroupMin(50% DBMinBuyout)".

What this would do is it would apply "50% DBMinBuyout" to all the items in that group. So in my example this would result in this list of prices:

50% 150000g, 50% 140000g, 50% 110000g, 50% 400000g

=

75000g, 70000g, 55000g, 200000g

the GroupMin() function would then (just like the already existing min() function) return the lowest of these values.

So in this example this would return 55000g.

That way, any of these 4 items would only show up in my sniper results if the item gets listed below 55000g.

But this is just one possible use of this. Giving us the ability to reference the prices of all the items that are in the same group would open up a ton of possibilities and give us much more control over things.

A second suggestion on a similar note that could also do tsomething like this and more:

It would be great if there was an option you can enable for each group that would cause TSM to treat all items in the group as one and the same.

In regards of pricesources this could simply mean that TSM calculates the average value for all the items in the group.

But more importantly, this would enable us to also undercut the cheapest auction out of all the items that are in one group.

So, to get back to my previous example, if I were to buy one i915 "Diadem of the Highborne" that popped up in sniper below 55000g, I would now be able to run a post scan for it and TSM would post my auction at 109999g99s99c, undercutting the cheapest out of the i915 auctions up on the AH, even if I bought a slightly different i915 Diadem.

Cheers,

BilisOnyxia

My idea is custom functions to allow Dynamic rule based group allocation eg:

Function group.additem{items, group} {
While I <= MasterGroup.itemCount (

this.Item = MasterGroup.itemAt{i}

If I.quality = rare
(moveItem(I,RareItems)
I++
}

Or as above but
If I expires > customexplimit move to De group.

UI could be part of operations just apply to master group.

Alliance group management op could simply have a criteria and an action.

Eg: items in <group applied> to <equal> <quality> rare THEN <move> item to <custom group> Unless item = level 110 and /or on whitelist

Etc

Thats a very brief mixed pseudo code example we clarify on request

• What shortfall are you trying to solve in the current functionality of the addon?

There's a few things I'm trying to do with TSM that requires me to scan the SavedVariables since TSMAPI doesn't support what I'm trying to do.

• What new functionality do you hope to attain with the addition of this feature?




• A table of items put up on the auction house with their stats (last sold, ammount sold, ammount expired, ammount expired since last sold,...) similarly to TSM:GetAuctionStatsSinceLastSale(itemString) and TSM:GetAuctionStats(itemString, lastSold) wich we can't use.
  I am currently splitting, iterating and analysing through: TradeSkillMasterAccountingDB["r@"..GetRealmName().."@csvSales"] and TradeSkillMasterAccountingDB["r@"..GetRealmName().."@csvExpired"]
  wich is slow and really not pretty.




• Get the current profile on current character.
  I'm using "TSMprofile = TradeSkillMasterDB["_currentProfile"][UnitName("player").." - "..GetRealmName()]" to achieve so.




• Get the minimum/normal/maximum price of an Auctionning operation.
  It's currently possible to get operations of an item or group through TSMAPI.Operations:GetFirstByItem(itemString, module), but you can't go into more details. I currently have to use "minimumPrice = TSMAPI:GetCustomPriceValue(TradeSkillMasterDB["p@"..TSMprofile.."@operations"]["Auctioning"][TradeSkillMasterDB["p@"..TSMprofile.."@groups"][v]["Auctioning"][1]]["minPrice"], itemString)" (and similar for normal/maximum) to achieve this result.




• How would you or others use this feature? (perhaps the most important question - please provide SPECIFIC use-cases)

I use all of this (and more) to automatically know about bad auctions that won't sell when mass posting (with the expired since last sold by sold ratio), automatically sell my items in the "Bad Auctions" group (I prefer that over TSM_Vendoring) sort and rearrange my mogs into different price brackets, know when an item is to low to even be worth auctionning, know when an item has previously sold but isn't currently in a group and (in conjunction with CanIMogIt) automatically sell ungroupped learned mog pieces that are not worth selling.

As an enchanter who sells old world enchants I have a lot of stock. A little bit of this kind of dust, some various greater essences, all sorts of shards - you know the pain. I would like to be able to hover over these items in my bank and determine how many of them I use on (for example) a monthly basis. If some of them haven't been used enough I can convert them to something more usable or sell them!

For example:
I have made 5 Enchant Weapon - Exceptional Spellpower this month. I want to know how many of an item I've used in the past month so I select the option so see how many I've used in the past 30 days. When I hover over Infinite Dust it should say (50/30 days) and Greater Cosmic Essence should say (10/30 days). Let's say I never use Volatile Water or at least haven't in the past month. When I hover over it I would see (0/30days). That way I can reconsider how much space that Volatile Water is taking up in my bank. I think a daily/weekly/monthly/ever option would be useful.

I find that the dbmarket prices are often wildly inflated and unreliable as a source for determining whether I can turn a profit on resale. I flip many items daily and find that using the region average sale price as my benchmark allows me to turn more items quickly. The tedious part is that I have to visually compare the auction price to the region average sale price in the tooltip. It would be handy to be able to set the source price for the %MktValue column to something other than the easily-manipulated dbmarket. I could then get a quick sorted list of everything that is underpriced according to my criteria.

I see that this idea was suggested back in 2013 and was declined for lack of votes, but I thought perhaps there might be more interest now.

I want to be able to sort all my items by "# failed since last sold" and "Failure Rate (# failed overall / # total units auctioned)

The current options are not helpful when identifying bad sales, they are seperated, but the tooltip shows the amalgam of the two numbers (cancelled and failed) which gives no idea if the auction organically failed due to never being bought or because you had been undercut, so you just have to assume all failures are bad failures (side suggestion to record a cancel scan mark against these auctions)

But i want to be able to go to one screen and sort it and see oh, Ice Frag Bombs have NEVER sold, i should just go ahead and vendor that

I know there is a failed limit, but that counts per unit and includes cancelled, so it doesn't help if you are fighting an undercut war with someone over the Stylish Purple Hat