2 Jul 20:05
User departure, game suspension, and bot thoughts
Jason McIntosh <zendonut <at> gmail.com>
2005-07-02 18:05:31 GMT
2005-07-02 18:05:31 GMT
Coding like mad, including my attempts to implement [[user departure]] and its three possible outcomes (throw, suspend, bot). This leads to some interesting thoughts, including some small protocol changes I feel are necessary, and some related questions. User departure stuff: I think I am going to add suspend_game() and resume_game() to the core protocol. These are natural complements to start_game() and end_game(), and allow the client to react to these situations. Originally I had throw_game() in there as well, to signal the difference between a natural game-end and an abrupt one, but decided it was better served by adding an argument to end_game(). That call now accepts a boolean, and if it's false that means the game was thrown. The effects are so similar for a user in either case that it didn't seem right to make a new method for it. Maybe I am wrong. I don't think any special calls are needed for when a bot replaces a player. It's pretty self-evident, when it happens. I have specified that game records can take an optional "finished" boolean, signaling wether the game finished normally (true) or was thrown or abandoned (false). (Assumed to have value "true" if not defined.) Records of unfinished games do not affect players' rankings for those games' rulesets. (They're still useful for other reasons.) I grumbled for a while on "finished" versus "completed", because "incomplete" implies that the game didn't end and never will, and "unfinished" sounds more like it's in a state of suspended animation.(Continue reading)
RSS Feed