A game that runs the game Killer (or Assassin) by text message. Players are secretly assigned one other player to 'kill' with a foam dart gun. They receive new targets and report kills to 'Killer by Text' via text message.
However it does require someone to run the game. When you kill your target you tell your GM, who then confirms with the killed player. After this the GM will give you a new target. The GM also has to handle people quitting, removing inactive players, and assigning new targets. With large or fragmented groups communicating changes and receiving updates can be problematic.
To make assigning new targets easier on the GMs they could have a program that will do this automatically and display relevant contact information so the GM can communicate this. This could easily be taken one step further by connecting a phone to the computer. Now the players can communicate directly to the program, essentially eliminating the need for a GM!
The messages must be in a simple format, and user commands must be easy to execute. A user always needs to receive a reply to a message, either confirming it was executed correctly or otherwise. A 'help' command is a good idea, so a player needn't memorise all the commands.
Reassigning targets also needs to be handled. Each player must have only one target and be only one person's target. If a player is removed then a message needs to be sent to the removed player's assassin notifying them of a new target.
To send out messages a phone that can process AT commands is needed. The phone needs to be connected to a computer that runs constantly.
KillerByText is now being used! Bristol University's BUZAN society is currently running a game. Updates can be found on their Tumblr page: http://bristolassassins.tumblr.com/
KillerByText has been set up to use SMSLib — an open source API for sending and receiving text messages. The game has been run several times with no major bugs, which is great news! Minor tweaks have been made (such as confirmation from the killed player being required for kills to complete, and dead players being able to kill alive players, being used in the case of a mutual kill).
Future work will include making the system more user friendly, allowing players to communicate with the system via email or text message, and having more options per match (e.g. removing scores, disabling name changes).
More complex changes that I want to implement are simultaneous matches, persistent players (for a league table of scores), and text-to-speech software that phones players.
Lines of code: 4559
Number of classes: 72
Libraries used: RXTX, SMSLib, Simple XML Serialization.