- 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
0/0? HAH!
CV Bomber:
Sale 1:
http://backpack.tf/profiles/76561198116230594/#!/compare/1450425600/1450512000
1:1 C Moon Samur
B/O was 250: http://www.tf2outpost.com/trade/27583350 Capping.
Sale 2:
http://backpack.tf/profiles/76561198116230594/#!/compare/1448524800/1448611200
Duped Cloudy Moon Backwards Ballcap + Duped Time Warp Prancer's Pride + It's a mystery to everyone Hellmet
115 + 24 + 52 = 191, gonna use 200 for neatness.
Cap Mini:
http://backpack.tf/profiles/76561198101606378/#!/compare/1454745600/1454832000
HG Rack + 14 keys
Rack is 4 months out of date, and im tired. Gonna use current.
100 + 14 = 114, using 115 for neatness.
Not gonna mini prancers, it's too cheap to matter.
Gonna use 200 - 250 here.
yea looks nice. on sale 2 at the time the prices i said where 140 for ballcap (at the time his was ok with that cause it was duped) + 25 for prancer + 80 for hellmet (was unpriced at the time of sale. but it looks good man) nice suggestion :)
http://backpack.tf/vote/id/568c5a49dea9e97c6a59701d the samur sale was used here. Other sales on the samur support a higher value, though.
Since you cant use the samureye here its probably best not to update this since the samur is obviously more than 200, 200 sale consists of dupes and the hat is pretty recently updated already
Buyout still caps without that sale involved. Should be fine
No. You're forcing an update with a sale that literally happened less than a week after the current accepted suggestion and a sale you cannot use because it was used in the other suggestion. First sale shouldnt be used, 2nd sale is from the same time frame as the other sales from the previous suggestion and clearly in it's vicinty, making this update both wrong and redundant
Agreed. It's not a matter of "oh the value still caps at the B/O", it's a matter of "this sale was used elsewhere so it cannot be used here". That simple.
So, wat d0
I commented below as well. In general, here is how I approach these situations - the hat with more sales should be used to price that hat with fewer sales. Here the sam should be used to price the bomber with a lot more sales over there. Just as foamy suggests, remove the bomber sale from the sam suggestion and use the other sales as a mini here. Will be easily over 250.
If the sam suggestion was made in the last week, I'd even allow a resuggestion there throwing the sale at 240 based on the bomber out. But it's old at this point, and the range in general should be close enough for it to be a non-issue
Personally think it's okay here. I see this essentially as a refresh with a wider range. If we group sale 2 with the sale in the last suggestion, we'd get a range of 200-240.
And it wouldn't be appropriate to go with 200 flat when there is clearly a sale much higher than that. Hats with more sales should be used to price hats with fewer sales, so the sam should really be used here instead of the other way around.
I'm comfortable saying that the value hasn't changed much in the last 3 months and feel comfortable enough with the value to have this used in other suggestions.
So, close or leave open