Split out Monster into a stand alone class in it's own file.

[jamesdonkin]

I would suggest making Monster it's own class, separate from Encounters, then use them in encounters.

• [ ] Create a Monsters.py file
• [ ] Import Monsters.py into the DungeonDeliver.py file
• [ ] Create a 'super class' Monster for other monsters to descend from
• [ ] Give this Monster class attributes as in the main file - name, health, damage
• [ ] Create a subclass for each type of monster - in the constructor set the health & damage. Hard code the name.
• [ ] In the DungeonDeliver.py 'kick_down_door' method create an instance of the right type of monster in each encounter, so rather than

         monster_name = "the giant rat"
         monster_hp = 8
         monster_dm = 1

   Have something like

theMonster = GiantRat()

[jamesdonkin]

So then the games runs just the same but the monster logic is in it's own file.

[jamesdonkin]

For this to work you'll need to do other fixing up where the old monster variables are accessed. For example

def monster_attack():

Suggest changing this to:

def monster_attack(attacking_monster):

And pass in the monster doing the fighting to the method call. Then inside that block you can replace

monster_hp
monster_name

Global variables, with:

attacking_monster.health
attacking_monster.name