Reply to "How often does Auction Sniper let you down?"

quote:

Surely it doesn’t take a lot of programming nous check ‘number of wins required’ and place <= that number of bids? I kind of expected Auction Sniper to have at least that basic level of competence.

Your misfortune is definitely worth noting. I agree, checking the number of wins, then scheduling more than one snipe in the bid group if necessary WOULD be a nice feature in AS, but your experience indicates AS does NOT have that level of sophistication programmed in the bid group feature! Apparently, the way the bid groups feature works:

1) If number of wins > or = number of desired wins in bid group, then CANCEL remaining pending snipes in bid group and STOP
2) If number of wins less than number of desired wins in bid group, schedule next ONE snipe in bid group.
3) Fire snipe
4) Determine outcome of snipe (win/loss)
5) Goto #1

Apparently, the bid group feature evaluates/schedules snipes 1-at-a-time, regardless of number of desired wins vs. wins. Perhaps the way to circumvent this deficiency in the bid group feature is to schedule one of the simultaneous ending auctions OUTSIDE the bid group. This unfortunately bypasses the nice feature of the bidgroup - limiting wins to a desired number. Another possible solution would be to have 2 separate bidgroups for the same type item (#bidgroups = #desired wins?), but this has disadvantages too.