Java Knight Game -- 3

[login to view URL] Round Table Games recently hired you as an intern, and they would like a revamp of their inaugural game, Knight Fight, with a new version Knights of Legend. While they have hired a software architect to design the layout of the game, your job is to implement it in its entirety as text based adventure game. The software architect has provided you with the following resources: Knight Fight - UML Diagram Knight Fight - Java Documentation You should familiarize yourself with the UML. Anything in the UML specification is viable for testing/grading. Not all private variables and methods are listed, but some are to help you out. (+ == public, # == protected). You will need to have private variables, and feel free to implement as many private helper methods as you need (we had many). Once you familiarize yourself with the UML, you should use the java documentation as a guideline of what to write for each method. Required Features To Implement File Reading and Saving Program data should be stored in CSV files, that will be read at the launch of the program. There should also be the feature to save the current progress of the knights. There are both default files, and the ability to pass in files via the command line. Knights Knights gain experience defeating monsters, and there can only be four active knights on a quest at a time. Fortunes / Bonus Cards Before knights start a quest, a random fortune is assigned to them. This fortune provides bonuses or even minuses if the fortune is bad. MOBS / Monsters Knights will have random encounters with 1-4 monsters (depending on the number of active knights). Team Management When not on a quest, players should be able to view information on each knight, and manage their active knight pool. Knights never "die", they are just defeated and return to the normal pool. Text-based game For now, the entire game is text based to the System console ([login to view URL] / [login to view URL]), however, it must be done in a way that can easily be replaced. The above is just for the general picture, and sometimes what clients actually give us developers to work with! This is much easier to see by looking through the javadoc.