I am using the minimum bid system, set so that bids lower than current highest bid are disallowed (open bidding). However, with anti-snipe set to e.g. 5 sec, bidding gets extended by 5 seconds even when someone bids a value that is LOWER than the current highest one and is rejected. It should not delay in this case since the bid was rejected so no public info about the auction changed that needs to be reconsidered by everyone.

I think this is expected f90 as the bids may not be announced so if you bid lower and not get extended you would know you did not win and could bid again.

This is an example of typical corner case. I agree that for OPEN (announced) biddin, bids < max bid should not trigger anti snipe, but I am not sure what was @Roeshambo intention here.

This could be hard to fix in code as anti-snipe behaviour would need to change depending on whether bid announcement is on or off, so maybe just having an additional small tickbox that pops up under "anti-snipe", where you can choose whether it triggers for lower than max bid, is enough so people can customise themselves?

@lantisnt This argument might make sense for closed bidding, but there you don't really need anti-snipe at all since you are not competing directly during the bidding phase.

However, for open bidding, lower bids triggering anti-snipe means someone could delay your bid phase infinitely by repeatedly bidding low. This is not a BIG problem as it doesn't affect who gets the item and the final price, but definitely a loophole that might be exploited one way or another, no?