- 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
1 year outdated :c (well 12 months, but close enough)
Only one usable sale in forever.
Solds:
18 keys http://www.tf2outpost.com/trade/19828884
Sellers:
17 keys http://www.tf2outpost.com/trade/21293388
B/O 1 bud http://www.tf2outpost.com/trade/20698212
B/O 1 bud 5 keys http://www.tf2outpost.com/trade/20355614 1 offer in 1 month :c
For Offers http://www.tf2outpost.com/trade/21428645
Well if there's only one usable sale at 18, I think that should be the suggested price since you can't back up your low-end with sellers
No sense in making the price 18 keys when its available for 17
Yes but you'd need solds at 17, and with one valid sale in the past months at 18, that makes perfect sense
Actually, you can't base suggestions on B/O's but since he has got a seller of 18 the suggestion is not based on B/O's wich means this is valid.
When talking about unusuals, you do need solds when lowering/raising.
When you have sold at 18 keys and a seller at 17 keys, the range should be 17 - 18 which is what it is here. There is no need for solds here other than the 18 well because its not possible to find any other solds as dabears mentioned. He is showing one sold for 18 keys and there is a seller at market at 17 making the range 17 - 18 keys.
I suggest you to read over the guide again theguynextdoor.
you don't need solds when lowering a price
For unusuals you do. Became a rule in early may
http://forums.backpack.tf/index.php?/topic/6033-new-unusual-price-suggestion-guide-the-cheat-sheet/
B/Os alone cannot be used to make an unusual suggestion. Just like we don't like to use offers as the only proof to raise the value on an item, we don't like using B/Os alone to drop the value as this has frequently caused bp.tf to lead the market with consecutive suggestions every 1-2 weeks dropping the hat (see Miami Wraith). This also creates an issue when future suggestions use those values as proof when they are still inaccurate.