I've been scratching my head on this one for a while.. The "PCT" reported in a Snatch Querry does not match the "PCT" of the item in the Browse window. So I started looking at it with the calculator. Turns out the calculator wasn't needed. The PERCENT reported by snatch is the percent of the price of the item ADJUSTED for the PERCENT that your told Snatch to watch out for... NOT the PERCENT relative to the MARKET PRICE of an item like you would expect it to be... another words:
If an item has a market value of 100g, and you tell snatch to watch for that item when it is 80% market value (80g), and some gets posted for 80g, Snatch will list it, and report that the price is 100% (which is 100% of what you told it to WATCH for), NOT 80%. If some is posted for 60g, Snatch will report the price as 75%, not 60%... so on and so forth.
I think that the price should be expressed relative to the worlds MARKET VALUE, don't you? maybe you could look into this?
It is working as intended, since otherwise the Pct of different items might be apples to oranges, since some might be overpriced, others underpriced, etc. doing it the way we do sorta normalizes things, so you can sort on Pct and have the result be sensible. say if two items are both normalized to 80%, they have roughly the same discount from your target price.
though i sometimes agree with you that i wish it were just the % of market price.
Essentially, when you put something on your snatch list for a certain value, you're saying the value you set *is* the true "market value" for the item. This was clearer back when we only allowed snatching by hard values, rather than percent of server market value. Allowing snatching by percent of market value has muddied the waters some.