1. Improve the rendering so that each grid square is represented by a box created out of characters.
2. Improve the rendering so that each ship type is in a different color. Ships should be visible, not hidden from view. Yes, that’s a poor game but we are just using this to test our algorithms and design.
| S |
3. Improve the rendering so that the grid has horizontal labels (A through J) and vertical labels (1 through 10).
4. Parse the input to get the guess in the form LetterNumber e.g. B7, G10, A1. You will find [url removed, login to view] and [url removed, login to view] to be useful API calls. Invalid input should cause the input to be requested again – it should not be possible to crash your program with bad input.
5. When you have a valid input mark the grid location as used and then render an X in the square to indicate it has been used. The X should be Red if it was a hit on a ship.
| X | | X |
• You may not modify the char array to store the extra characters to print. The array should only store information about the gameboard and the extra output should be generated by your code.
• Your grid rendering must display the ships. At this stage we are just testing parts of the game so we don’t need them hidden from the user. (And it makes it much harder for one of your users to grade!)
• You do not need to determine end-of-game conditions, validate repeated hits or any gameplay. However, feel free to add any of those things if you feel the urge.
• There are many useful APIs in the Console class. You may render the grid line by line using Write and WriteLine or you may render it using the SetCursorPosition API. You may redraw the entire grid each time or simply replace the sections that have changed.
• You may find it useful to set the size of the console window to something a little larger. There are APIs to do this in the Console class. The example above is just one style of drawing – feel free to experiment with different characters and grid sizes.