- 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
Sold for Smoking TC (3.9)
http://www.tf2outpost.com/trade/24544357
Sold for a Burning Toque (4.1):
http://www.tf2outpost.com/trade/24549262
Mini for Toque (currently has an ongoing suggestion):
Sold for C.hearts capo + 3 buds (5 buds, seller's b/o):
http://www.tf2outpost.com/trade/24374397
Sold for 45 keys + 1 bud (4 buds, but b/o was 3 buds 10 keys. Sold in a day though):
http://www.tf2outpost.com/trade/24368751
Using midpoint of current suggested value.
Since there's a range of 3.9-4.1, 4 buds flat seems reasonable.
since there is a range, I'll just suggest a flat price?
I'm not understanding that.
Rounding is key
Just like how keys are keys
If you round up 3.9, it'll be 4. If you round up 4.1, it'll be 4.
What is there not to understand?
Its less accurate to say that the hat sells for 4 buds than it is to say the hats sells for 3.9 to 4.1 buds.
Why use 'rounding' and degrade the quality of the information when the range can be captured just as easily.
Extracted from:
http://forums.backpack.tf/index.php?/topic/6033-new-unusual-price-suggestion-guide-the-cheat-sheet/
Giving the suggested range the appropriate level of precision: all unusual suggestions are approximations. As such, the suggested range should be rounded off appropriately. The following suggested approximations are guidelines and NOT rules. Please use common sense to guide you.
For unusuals listed in keys, please round to the nearest integer
For hats <10 buds, using up to 1 decimal place is fine.
For hats 10-15 buds, rounding to the nearest 0.5 buds is reasonable.
For hats 15-50 buds, rounding to the nearest 1 buds is reasonable
For hats 50-100 buds, rounding to the nearest 5 buds is reasonable
For hats >100 buds, rounding to the nearest 10 buds is reasonable
Examples:
http://backpack.tf/vote/id/5362b9b04cd7b82b7c8b472e - value here is really 100 +/- 10. Giving it any more precision, even 97-105, is honestly more precise than we can reasonably tell.
http://backpack.tf/vote/id/53567ece4cd7b8ae2d8b4661 - instead of 4.1-4.9, a range of 4-5 - it keeps the average constant while giving a decent approximation.
For hats <10 buds, using up to 1 decimal place is fine.
Yup. I mean... you wrote it out yourself, guess you didn't read it first or something.
Its not in keys so it doesn't need to be an integer and its under 10 buds so 1 decimal is fine.
3.9-4.1
Its not that I didn't read, I pasted that extract to show you how flexible the range can be depending on the suggestor since you asked "Why use 'rounding' and degrade the quality of the information when the range can be captured just as easily."
I wrote a 3.9 value beside the TC, but that's using the original midpoint value of the TC (which is 4.35 buds) when calculating overpay. Based on the extract above, I rounded up 4.35 to 4.4 before calculating the overpay which comes out to 3.96 buds for the TC which I will still round it up to 4 buds. As for the burning toque, the value after overpay is 4.05 buds which I then rounded up to 4.1 buds. So in other words, I can have a range of 3.9-4.1 buds, 4-4.1 buds, or even a 4 buds flat price.
You can choose to continue debating over a small issue like this, its up to you. As far as I'm concerned, I am allowed to suggest at 4 buds flat as well.
edit: Just confirmed that the safeguard was offered to the TC owner (which had a b/o of 4), so 3.9 buds would've been irrelevant anyway.