I have come up with some suggestions for Huntercoin:
Protocol:
Fast coin has 12 second blocks. Perhaps we could reduce huntercoin's turn length.
Client:
Immediate Feedback: Instead of showing 'pending' when a character is ordered to move, make this character have its red line immediately drawn to the destination specified on. Then send out the packet to the rest of the network. When the turn finishes, the game could just leave this alone, correct it (if say the character was killed), or redraw it (perhaps easier to code). Responsiveness: When a player arrives at a waypoint in the game, the client has to issue another move command to the network. When this happens, the user is to make this character move in some other direction for the next block and has to wait a whole minute before he issue his move command. Correction: What is more, a user might decide that he needs to correct his move after deciding to move.
Each player should have a 'next move' variable. map<PlayerID, Move *>. After all of the transactions have been processed, broadcast the commands that exist in the map to the network. Then empty the map. If some player already has a command pending, then put that in this 'next move' map. If there is already one there just discard the old.
