- Forums
-
Pricing
- Community Pricing
- Pricegrid
- Spreadsheet
- Browse Suggestions
- Latest Changes
- Unusual Pricelist
- Browse by Item
- Browse by Effect
- Steam Community Market
- Market Pricelist
-
Trading
- Classifieds
- Classified Listings
- Utilities
- Calculator
- Premium Search
- Statistics
Basically, I need to price this to price another Unusual which will be used to price another one so I can price another one just to price another Unusual so another Unusual can be priced to price another one in order to price another Unusual...
The pain will never end.
Sale 1
http://www.tf2outpost.com/trade/21387328 - Sold for 16 keys
Sale 2
http://www.tf2outpost.com/trade/21893890 - Sold for Smoking Scotch Bonnet (15*0.9 = 13.5 keys)
Mini for Smoking Scotch Bonnet
http://backpack.tf/vote/id/53ecc6864cd7b8837f8b4750
Sale 3
http://www.tf2outpost.com/trade/21810687 - Sold for 12 keys (QS)
Sale 4
http://www.tf2outpost.com/trade/21876581 - Sold for 90 ref = around 12 keys (QS)
Sale 5
http://www.tf2outpost.com/trade/21867104 - Sold for a Strange Professional Killstreak Black Box (33$ on SCM = 28$ after paying fees = 11 keys) (Outlier)
Sale 6
http://www.tf2outpost.com/trade/21864086 - Strange Australium Frontier Justice (14.5*0.9 = 13 keys)
Sellers
http://www.tf2outpost.com/trade/21974297 - 16 keys
http://www.tf2outpost.com/trade/21854949 - 14 keys
Feel free to counter / support my proofs.
basically by chaining unusuals like that. you can never rise them.
you just make every single one lower.
The problem is not from me.
The problem is from the market. I'm just according it.
everything depends on the order in which you price them
you could have not used the bonnet sale. and price this at 13
then price the bonnet even lower using the dogger.
that's something that always bothered me.
and the fact that you calc in * 0.9,where it would be more logical to multiply by 1.1 for example
There are always an offerer and a buyer. The hat which is offered will not be overpay-calculated so the never-end-circle won't happen.
And if I didn't use the Bonnet sale, I still can price this at 13 - 14 keys because my high-end is based on B/O, not Bonnet sale.
but as the offerer/buyer can't be estabilished overpay has to be taken either way.
wohoo, gotta love the system.
and that's exactly my point. you can price this with 13-14,and then price the bonnet lower. :D
and because there is currently no proof who offered,overpay needs to be taken.
If I were to suggest this, I would go with 14 - 16 keys.
i wouldn't suggest in the first place
but yea that's better
I wouldn't with that 14-key seller.
You round up the 13.5 key sale, simple. You are actually suppose to in the first place. 13 keys seems low. 14 - 16 would be much better.
where comes the 14 from? i can only see 12, 13, 13.5...
Seems like a "mini chain", that's a thing right?
That's how I price Unusuals :P
16, 13.5, 12, 12, 11, 13, and sellers at 14 and 16.
I don't see how you get 13-14 from that. Surely it's either going to be 12-14 or 13-16 or something?
12 keys = QS.
14 keys from a seller with B/O of 14 keys.
Don't apply overpay twice on the same suggestion.
It's hard to control for sales across suggestions. But the problem with doing that is that when you get consecutive sales on hats you go from a value of 90% to 81% to 72% etc. even if all the hats were 1:1. Suddenly, after a string of 1:1 trades, what started out as a 10 buds hat is now <5 in value.
The issue we have is it's not often clear who offered. No overpay should be applied if the hat was offered, and if we assume that the other hat was offered every time, we get into this problem of hats losing values. If there are two consecutive sales where it's unclear which was offered, I think it would be fair to count overpay on one and not the other.
Impossible to account for this across suggestions but at the very least we can reduce some of this within a suggestion.
I don't.
Yes you do, you aplied overpay on the scotch bonnet in the suggestion you made for it, and in this suggestion.
In Bonnet suggestion, I don't use Bubbling Hot Dogger sale so no. Check it up.
You used overpay on the trash man sale, yes you do.
And then again, I don't use Bubbling Hot Dogger on the Trash Man suggestion so no. Check it up.
That doesn't matter. You first used overpay on the trashman sale to make the price, then use overpay again on this suggestion on the same hat.
First of all, let's check about Trashman.
http://backpack.tf/vote/id/53ecc6064cd7b8307f8b4827 - Low-end is based on a B/O while high-end is based on pure sale so no overpaying got involved.
Then Bonnet:
http://backpack.tf/vote/id/53ecc6864cd7b8837f8b4750
Low-end is based on Trash Man, which is fine. High-end is based on pure sale so again, no problem.
Finally, this suggestion: Low-end is based on price of FJ, high-end is based on the Bonnet, which is fine again.
I seriously have no idea what you are moaning about. Overpay rule applied here is just fair and square.
You used overpay to make the price for the scotch, and then use it again here.
Read what polar said to me here: backpack.tf/vote/id/53d269fd4cd7b877278b4568
I'm not taking this further because you clearly can't spot your own mistakes.
It's because of you using mini-suggestion meanwhile I don't do the exactly what you did.
When a hat is priced, it's fine to use it and apply overpaied again.
Your problem is not the same as mine.
I'm not taking this further because you clearly can't spot where you are wrong.
Want proof to destroy your logic? Here: http://backpack.tf/vote/id/53ecc6864cd7b8837f8b4750
You still didn't manege read what polar said. After he said I shouldn't apply overpay I asked why I wouldn't need it, because when making a mini suggestion you are making it like a real suggestion. He said it was a valid point but I still wouldn't need it.
makes sense to me
and giang,you didn't destroy his logic
even if you didn't apply overpay,the sale would be limited by the b/o (which is stupid)
I don't understand the 16 key sale. His b/o was 14.5 as stated in the trade. Where did you get 16 from?
Oh...
I forgot to check his B/O again...
No worry, I'm going to resuggest now.