- 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
https://imgur.com/2f28jvc — unsold @ ~22 Keys for 1 month
B/Os alone can only be used to drop the value on a hat (you cannot raise based on a b/o.) if all three of these criteria are met:
• There are no usable sales. 🗹
• You must drop the mean value of the hat by at least 15%. 🗹
• The trade must have a reasonable time to mature (and must be reasonably bumped). 🗹
You need to include snapshots of the listings of over the last month, since bots can change their listings prices without refreshing the time it was listed for.
Example - https://backpack.tf/suggestion/680adbe522478383570b33fb
June 19: 22 keys https://imgur.com/UEyMSdg
June 26: 22 keys https://imgur.com/EOLeI2W
July 3: 22 keys https://imgur.com/fwyECUA
July 10: 22 keys https://imgur.com/rD9bvXt
July 17: 22 keys https://imgur.com/P3Oh3aN
One snapshot per week in the past month, the listing has been consistent at 22 keys so it should be fine
thankfully you were willing to give plant the free help, you can never be to careful with the "listed for" time with bots.
I know that sometimes it can be a mess when for an example the key price is updated
A slight mess yeah, that's why I picked the example I did above, b/o dropping is simple yet requires more proof than a single sale suggestion to be accepted given all the variables. Great to see others attempt them, but would love to see it correctly done and not just lazily attempted.