BuzzerBeater Forums

BB Global (English) > Burned at Auction

Burned at Auction

Set priority
Show messages by
This Post:
00
18652.16 in reply to 18652.15
Date: 3/7/2008 10:57:29 PM
Overall Posts Rated:
1515
I think I did say that in my very first post. The BB Clock part anyways.

This Post:
00
18652.17 in reply to 18652.1
Date: 3/8/2008 1:43:55 AM
Overall Posts Rated:
22
Adjust the time in your computer

This Post:
00
18652.18 in reply to 18652.17
Date: 3/8/2008 3:58:45 AM
Overall Posts Rated:
1515
You sir, are one funny guy. A true comedian from the old school. Thanks for your input.

This Post:
00
18652.19 in reply to 18652.18
Date: 3/8/2008 4:30:04 AM
Overall Posts Rated:
3535
I see. I think you ahave simply misunderstood what I meant by too early. The last time befoer this I could have logged on would have been about 20-25 minutes before the auction. I was hurrying to try and finish what I was doing in time to bid, but felt that there was no point bidding on my last login because I simply would have been outbid anyways.

this is exactly what I disagree with. If you feel a player is very important for you, you should not wait till the last minute to make the right offer... no matter if that costs you a bit more money.
We may disagree on this, but I hope you understand my point.

This Post:
00
18652.20 in reply to 18652.19
Date: 3/8/2008 11:24:47 AM
Overall Posts Rated:
1515
The point of an auction is the fact that the "right bid" is the least amount that will win the purchase. (At least for the buyer)

What does bidding 20-25 minutes early get me? To win an auction this way you are forced to overpay substantially, wasting money better spent elsewhere.

This Post:
00
18652.21 in reply to 18652.20
Date: 3/8/2008 1:45:56 PM
Overall Posts Rated:
00
Yeah, I had the same thing happen to me on a player that was bidding on. I also had the same WTF? moment. In my case, I had been bidding against another manager and apparently waited too long to rebid - I submitted a bid with about 45 seconds left (according to the BB page clock), and got the same message. I can't explain it, but I sure won't let it happen again...