Finish the client server API and make sure that protobuf generation works.

Need values for:

• server host
• server port
• directory for serving web-pages

It would be easier if project artifacts could be published to internal maven repo hosted within the project at github. In gh_pages?

Helper class for initiating server connection and forwarding client to server requests.

amIDealerPlayer, amISmallBlindPlayer and amIBigBlindPlayer doesn't compare by the player name correctly.
Currently these functions are written like this:

        amIDealerPlayer : function() {
            return playerState.table.dealer === getMyPlayerName();
        },
        amISmallBlindPlayer : function() {
            return playerState.table.smallBlindPlayer === getMyPlayerName();
        },
        amIBigBlindPlayer : function() {
            return playerState.table.bigBlindPlayer === getMyPlayerName();
        },

They should be written like this:

        amIDealerPlayer : function() {
            return playerState.table.dealer.name === getMyPlayerName();
        },
        amISmallBlindPlayer : function() {
            return playerState.table.smallBlindPlayer.name === getMyPlayerName();
        },
        amIBigBlindPlayer : function() {
            return playerState.table.bigBlindPlayer.name === getMyPlayerName();
        },

Notice the added .name in each function.

The split of the pot may not be symmetrical if someone does an All in.

Versioning and project management will be much easier if in common project.

Some things to improve is:

-Each player bet could be shown, not only the total for each stage.
Table cell can show each bet value from top to down and the sum ($-char is unneccesary).
maybe prefix with '+' for raise (+30) and '=' for call (=50) ?
Small blind value can be marked with italic or in bold to indicate the small blind - the starter.

Better way of showing and selecting table to view. Show tables with start date/time, nr of players.

Server status:
Section "Players" should show room for each player, grouped with room and connect-time-order.

Helper class that keeps track of the following:

CurrentPlayState

• players (with current chip amount, and investment in pot)
• chips in pot total
• community cards
• my cards
• game state
• hasPlayerFolded('emil') or playerEmil.hasFolded()
• big/small blind amount
• dealer player, bigblind player, small blind player

Each bot player must implement the client/player interface that responds to requests / messages from the game server.

The tournament tab is password protected. Make the username and password configurable (either via startup parameters or via external configuration file).

Helper class that keeps track of the following:

CurrentPlayState
- players (with current chip amount, and investment in pot)
- chips in pot total
- community cards
- my cards
- game state
- hasPlayerFolded('emil') or playerEmil.hasFolded()
- big/small blind amount
- dealer player, bigblind player, small blind player

The onPlayerFoldedEvent in playerStateUpdater.js is currently empty. One potential solution is:

onPlayerFoldedEvent:function (event) {
    getTablePlayer(event.player.name).folded = true;
},

Document how to deploy the server in Jetty, what startup parameters are available and common problems when letting a group of 30 people hack a robot during a session.

• Jetty install and configuration in Ubuntu
• Hosting a local maven repo
• nginx configuration
• how to distribute downloadable starting projects

The JS-lib should keep track of:

• Players current chip amount
• Cards in community
• Current state (PRE-FLOP, FLOP etc)
• Game result on finished game

It should be possible to limit the number of bots originating from the same IP number. This could be implemented in the GameSettings class.

Let's help client developers a bit, for example with:

• Calculate the best hand from current available cards
• List of current players and their last known chip amount

After the first real session letting a group of about 30 people try hacking a bot-player most of them were having a hard time writing the code that analyzes the current hand. Perhaps it might be a good idea to move the server code for this to the common library?

Should be able to handle 40 connected players in training or tournament play

Maybe add rule that disconnects or deactivates misbehaving player from server. For example if a player continues to respond too slow or with illegal Action. Now a slow player is left in the game only force-folded in each game bout. After say 10 times the player should be deactivated or disconnected.

If all players but one go All-In there is no meaning in letting the last player bet any more. In these cases deal any remaining community cards and go to ShowDown.

When showdown results in a draw the Pot should be split equally between winners.

Package the web-client with all dependencies in a super-jar and create a simple web-server with Jetty.

The Pot cannot handle "All in" situations.

After a tournament is run players are usually interested in looking at player stats and analyzing the game. Some function from the admin-gui to store the whole tournament for later analysis would be good. XML/JSON file or database.

så ska spelomgången alltid gå vidare efter att alla spelare har synat den som senast höjt

http://www.pagat.com/poker/rules/

The amount a player wins should be: winnings - amountInvestedInPot