Posted 2011-May-12, 09:50
Welcome to BBF redshoes. Yes this is something we've been trying to think about recently. But we have not figured out a solution to this problem yet.
The fastest fix would be something like using "Tourney Completion Rates" again. If you are unfamiliar with it, BBO tracks 2 ratios for everyone. Tourney Completion Rates (TCR) - how often players finish normal tourneys, and Main Bridge Club Completion Rates (MCR) - how often players finish their normal table games.
Those using the new BBO to create tables or tournaments can choose to filter out players with lower TCR or MCR than they desired. They can only filter out those with as high a TCR or MCR as they themselves possess. (ie, someone with MCR of 85% cannot ask that everyone at his table have an MCR of at least 90%) This is an optional filter, and table creators and TDs need not use it if they don't want to.
-------------------------------------
Sorry for the slight digression. We started out by imposing TCR in free tourneys like the free version of Express tourney. The idea being that we wanted to keep out those who dally too long and cause an unpleasant experience for others. But this method still doesn't solve the problem of those who are deliberately trying for the better average score, and it was hurting players who don't play enough to qualify for a good TCR, or any TCR at all.
So this restriction has been removed from all the house free tourneys right now.
We also increased quite drastically (recent improvement) the number of free Express tourneys, but apparently it led to potential bailers having more opportunity to play the next free tourney, so it kinda provided a disincentive to stay(!)
If we were to use this as a crude solution to the automated tourneys behavioral problems, the solution can be implemented very fast as the code is ready and in place.
But I think what we're seeking is a better way, which is why it's taking so long to come up with anything. And for anything that involves tracking "time taken" by a player, this will take too much resources to produce.
My current thought about this is that we should do something slightly less crude (along the lines of TCR) so that it can be implemented faster, yet still be a bit more effective at targeting the problem. Something like, track players individual no. of AVE scores or AUTO ADJUSTED boards. When it gets above a certain threshold, then we block it. This would require the tracking of some factor that we can already do, and not require coding something extra like exact time. Still trying to fiddle with the idea though, and suggestions are appreciated!
"More and more these days I find myself pondering how to reconcile my net income with my gross habits."
John Nelson.