- 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
http://www.tf2outpost.com/trade/10185806 - rejected 0.88 twice, also 0.77
http://www.tf2outpost.com/trade/10673129 - sold in 2 hrs for 1 ref
http://www.tf2outpost.com/trade/10410245 - rejected 2 rec
http://www.tf2outpost.com/trade/10621565 - rejected 0.77
http://www.tf2outpost.com/trade/10377122 - rejected 0.77
cant find any sold ones, so leaving range at 0.77 because most dont attract offers even after 2 weeks
3 rejected offers of .77 and another of .88, I would say .88-1 would be even better
so would i. but i cant prove that they've sold for it. which is why im going easy
its still in the current range. i find this suggestion pointless.
why would it be pointless if people are offering more than the lower end and still cant get it? that means the lower end is pointless and not this suggestion
Because low-end is usually for buyers? seller wants to sell for full price to get profit? Welcome to Mannconomy.
Please mainly focus on buyers if you want to increase low-end price
... i am. have you even looked at the proof?
ive provided 3 rejects at 0.77, one at 2 rec and 2 at 0.88 and that it sold at 1 ref.
HOW is that not focusing on buyers?
edit: yeah, downvoting my comments help you out
ive shown people trying for more than that and fails. should i show offers of 0.66 instead of 0.77 since those doesnt seem to count?
It's just that you don't really have much proof of either price, I'll go have a look on outpost first before I start making false accusations.
All I seem to see is unsold ushankas at 1 ref. Taking another look at your proof, it seems to be relatively sound, but more would be required for my upvote. I'm remaining neutral for now, thank you for explaining, I'll delete my original comment to avoid negative vibes in the comments section.