October 9th, 2012!
Antifreeze Entertainment requires your service again for the completion of their upcoming MMORPG "NeverQuest". They are providing you with their modified versions of all the components for a Characters Gear and require you to build them the structure which will hold Quests and rewards for the completion of such quests. All the need, is for you to provide a data structure in which quests can come one after another, and quests can be added in between. One quest can only lead to another quest.
You have to provide Antifreeze Entertainment with your implementation of QuestList. Implementing this class will require you to build something which is known as a LinkedList. However ONCE AGAIN you cannot use any code previously written by anyone but yourself. You can utilize this file which should help you get started.
What is provided
- Creating at least 10 random GearItems
- Inserting them into your NeverQuestList
- Removing one at random
- Replacing the GearItem currently worn by a Character (CharacterGear) with the newly acquired item based on the type
- Printing the stats of the Character (CharacterGear.getStats())
- Repeating the steps at least 10 times
- CharacterGear- Modified with some set/get
- HeadGear- implements GearItem already
- UpperBodyGear- Implements GearItem already, modified with get/set
- ArmGear- Implements GearItem already
- TorsoGear- Implements GearItem already
- LowerBodyGear- Implements GearItem already, modified with get/set
- FootGear- Implements GearItem already
- LegGear- Implements GearItem already
Learning about LinkedLists
Your TA will go over how to create linked lists, insert nodes, get nodes, and remove nodes with you in lab. It will either be on the white board or using the following files (or a combination of both):
This will be done in lab, so it is advised that you pay attention and ask QUESTIONS if you get stuck or want to see how things are done again.
Look at the provided code, a good example of how to comment things. When implementing an interface, you ONLY have to comment the method once, when declaring it within the interface. Implementing classes of the interface should use the @Override notation for the method, indicating that the method is overriden and the doc for it comes from somewhere else.
THE DUE DATE FOR THIS ASSIGNMENT IS: OCTOBER 24th, 2012 at 235959 (11:59::59 PM) . Pay attention to this deadline!