And created an aspoker category

I've done some more testing and came to conclusion that it's actually not the server issue. Tracing out IDs of kicked player helped to place the issue in aspoker.

So, the bottom line, it is my current belief that INT() was the only issue here and server does kick correct players.

thnx for implementing the fix into trunk!

PokerTable doesn't kick inactive players. There are a number of issues related to this functionality:

1. in PokerTable.__init__
self.max_missed_round = description.get("max_missed_round", factory.getMissedRoundMax()))

the variable always ends up being a string if it's specified in XML config because it's not typecast to INT. This prevents PokerTable.cashGame_kickPlayerSittingOutTooLong() from ever satisfying player.getMissedRoundCount() >= self.max_missed_round condition and self.kickPlayer(player.serial) is never called

should be

self.max_missed_round = int(description.get("max_missed_round", factory.getMissedRoundMax())))

2. fixing the issue above leads to self.kickPlayer() call, which exposes another problem - wrong player get kicked out from table. When I tested it with 2 bots and 2 players, having one player fold for inactivity leads to one of the bots being incorrectly kicked from table instead of the inactive player.