I recently had the misfortune to play 2 droppers in one session - one with many saved games (benzion).
In both matches they left the game when in a lost position, and immediately complained about me to repbot, no doubt because 'attack is the best form of defence' and to inflict maximum harm.
Also some players use repbot as retaliation when receiving negative feedback, and IMO this makes repbot much less useful.
Therefore I propose that certain circumstances should disqualify anyone from using repbot to denigrate others - maybe even banned from repbot access.
There would need be be some safeguards - eg dropped games with known droppers (eg > 10 saved games) who are not bots might not be counted.
Is there any way to monitor invitations so that attempts to finish games can be recognised?
Excellent idea! I don't think that one has been proposed. Perhaps a player who leaves a game should not be allowed to complain?
socksey
"We are always the same age inside." - Gertrude Stein
I wonder if RepBot could notice which player left the game first... (ie who the dropper was)
tom
Quote from: Tom on October 04, 2008, 01:49:36 PM
I wonder if RepBot could notice which player left the game first... (ie who the dropper was)
I don't think this can be done, dropping causes are manifold - server breakdown, connection timeout, leave command, admin kick etc. pp.
This is how RepBot handles it:
http://openfibs.svn.sourceforge.net/viewvc/openfibs/trunk/modules/repbot/src/main/java/net/sf/repbot/linelistener/MatchEventListener.java?revision=50&view=markup
The events themselves are documented here:
http://openfibs.svn.sourceforge.net/viewvc/openfibs/trunk/modules/repbot/src/main/java/net/sf/repbot/linelistener/Monitor.java?revision=50&view=markup
I am not sure if for single event types some heuristic trick may work, but in general it will not.