Classes

• You need to include classes in your solution.
• I used the following classes.
  • A character class.
    • This contains all of the elements of a character.
    • It handles the logic for an attack.
    • It handles the logic for advancement.
    • This is a large class.
  • A challenge class
    • This holds all of the data/logic for a challenge.
    • This is a smaller class.
  • An encounter class.
    • This is composed of a character and a challenge.
    • It takes a player (character) and resolves the challenge.
    • This is a minimal class.
• I did not build the following classes
  • A die class.
    • There really is no data that this holds.
    • I built a roll function
      • roll
      • Input int sides, int die to roll
      • Output in the result of a roll
    • In this case the die has an action but no data.
    • But you could build a die class that has
      • Member data: sides
      • Functions:
        • get and set sides.
        • Roll n times, return sum.
      • This is really a personal choice.
    • A weapon class
      • In my implementation this is just a table lookup.
      • It is just data
      • Making the weapon a class would add flexibility to the implementation.
        • Adding diversity to the weapons would be easier.
  • I built three enumerations
    • One for weapon type
    • One for Attributes
    • One for the player's next action
    • All had the methods
      • StringTo*T (StringToWeaponT, StringToAttributeT)
      • *TToString
      • *TBonus : takes the enum and returns the corresponding bonus.
    • Attributes also had a function that calculated the next attribute.
      • I stored the attributes as an array, and this allowed me to loop over the attributes.
      • I also use this in the function that asked for the attribute to modify.
  • In the end, I had
    • a Player, an instance of the CharacterT
    • An array of encounters.

    Main:
       LoadEnounters
       While the the player is alive and there are still encounters 
           get what the player wants to do next.
           Do what the player wants to do next.
       Print status of game
    
    LoadEncounters
        input: empty encounter array, encounter size =0 
        output: filled encounter array, valid encounter size
    
        Get filename from user
        open file
        read number of encounters
        for i = 0 to number of encounters
            read encounter[i]
    
    GetNextAction
       input: none
       output: ActionT: the action the user wishes to  take.
    
        While invalid action
             Present the user with a menu of actions
             Get the action the user wishes to perform
    
    Take Action
        input: the encounter array, the player's current position, 
               the player, the action to perform
        output: the modified player or encounter
    
        take the appropriate action based on the action input
        NOTE: This is a big switch statement, at this point in your programming
              journey, you probably don't need to explain this.