Mission Accomplished: Time to Play - Programming GPS and OpenStreetMap Applications with Java - page 195

a waste of time to wait until two random players actually meet at a game
station. Therefore, the first player implementation should be a GUIPlayer
to serve two purposes. The game should be visualized for intuitive obser-
vations, and it can be used to invite real people to interact in the game
and challenge the automated players.
Problem 13.3 (Create a client GUI player to interact with the game server.)
Extend the LCPlayer to a GUIPlayer and add a GUI front end showing the
game board. The user should be able to participate in the game via mouse
and keyboard.
As an interactive GUI player is really useful, we implement Problem 13.3
in Section 13.3 and also provide some guidelines for Problem 13.2.
Note that classroom sessions should be restricted to the ldn packages,
while the roaf packages should be recognized as a given library (and can
also be isolated in jar files). Before modifying the library, the developer
should read the nal part of the topic for an overall understanding of the
ROAF directions. At this point, we should only be modifying the game,
not modifying the ROAF.
The server team can start out with the file LondonChase.java , which
is reasonably short and introduces the application logic. This team is
responsible to keep the game server up as long as possible and announce
down times in advance. A first task could be the following:
Problem 13.4 (Create a server cycle.) Modify the application logic to wait
for players to start a game. When the game is over, or interrupted, the
server should allow candidate players to enter a new game.
Here is another task that would be helpful.
Problem 13.5 (Modify game parameters during server uptime.) For effective
development cycles, the server administrator should be able to delay a game
start, modify game parameters, and then start the game.
Besides improving the game software, the server team can also act as a
game referee for unexpected situations. Competing players could be ana-
lyzed by examining their source codes or even added to the server logic with
a local server player. There are many such tasks and the server team will
certainly devise some of their own. Nevertheless, here is another mandatory
item:
Problem 13.6 (Implement game over.) If the chaser gets caught the game
should be finalized.
In addition to the server and GUI team, two main teams should compete
in runner and chaser development. Section 13.4 will demonstrate the basic