That would not be hard for a local application. However, I do not think it would be workable on the site. I am not saying it would not be possible at all -- I just think that it would not be very user-friendly and take an extended amount of time to play.

@lordhershey, making them not be able to mark an invalid spot would take away from them playing their own card. As far as the calling of numbers, I thought about that and decided not to -- at least for now.

Added controls to change some running states (orbiter spawn rate, orbiter spawn distance from Centre object, lifespan of new orbiters, orbiter turn rate and orbiter speed). Also, code viewing was implemented.

@NikZ, simplified code for shots to go a set distance before exploding instead of testing x and y coordinates. The problem should be fixed now.

After the move or setLocation command, compare the returned value of getY to the lower y limit (somewhere around 420, I am guessing; I will call it 'minimumY'). If the value returned is less than the minimum, set the location back to (getX(), minimumY).