Skip to main content

Item() rundown

 The item() class holds the information of the item and also runs the item effect when it gets used. Constructor def __init__ ( self , command , name , cost , usage): self .effect = command self .name = name self .cost = cost self .usage = usage The effect holds the string name of the effect for the item,  usage holds the value of the Effect . The rest are self-explanatory. EffectHandler() def effectHandler ( self , user: PlayableCharacter , equip= True ): #learned how to specify type of parameter. if equip: if self .effect == "Def" : user.defense = user.defense + self .usage elif self .effect == "AtkPhy" or self .effect == "AtkMag" : user.attack = user.attack + self .usage else : if self .effect == "hp" : user = self .healing(user) return user This handles the effects of the item when it is used. If equip is true then it will check for the equip...

combat.combatEndCheck()

def combatEndCheck(self):
removalList = []
follow = False
playerCounter = 0
for figther in self.listing:
removeFlag = self.listing[figther].deathCheck()
if removeFlag == True:
removalList.append(figther)
i = 0
for thing in self.order:
if thing[0] == figther:
break
i += 1
self.order.pop(i)
continue
if isinstance(self.listing[figther], Monster):
follow = True
if isinstance(self.listing[figther], PlayableCharacter) and self.listing[figther].currentHealth > 0:
playerCounter += 1
for body in removalList:
self.exp = self.exp + self.listing[body].experience
self.listing.pop(body)
if playerCounter <= 0:
follow = False
return follow

This is the final function we need to discuss for Combat(). It takes no parameters and it returns bool depending on whether or not combat ends.

The rundown

removalList = []
follow = False
playerCounter = 0

These variables will be used to do a good chunk of the work. removalList will be used to remove dead monsters from listing and order. Follow will hold the bool which we return at the end. Lastly, playercounter will be used to keep track of how many playable characters are still standing.

for figther in self.listing:
removeFlag = self.listing[figther].deathCheck()
if removeFlag == True:
removalList.append(figther)
i = 0
for thing in self.order:
if thing[0] == figther:
break
i += 1
self.order.pop(i)
continue
if isinstance(self.listing[figther], Monster):
follow = True
if isinstance(self.listing[figther], PlayableCharacter) and self.listing[figther].currentHealth > 0:
playerCounter += 1

This loop goes over all the characters in listing. I save the bool from deathCheck() to removeFlag. If removeflag is true then we add them to the removalList and remove them from order. Then I check if it is a monster or playable character. In case of a monster we make follow true. In the case of playable character, we check to see if they have more than zero hp and if they do, we increase the playercounter by 1.

for body in removalList:
self.exp = self.exp + self.listing[body].experience
self.listing.pop(body)

This loop takes the names in removalList and removes them and their corresponding objects from listing.

if playerCounter <= 0:
follow = False
return follow

Lastly, I check the playercounter. If it’s less than 1 we will set follow false. Afterward, we return follow.

Comments

Popular posts from this blog

Combat() completion! Fights exist now!

Combat() has been completed and the game now is starting to feel like a game. It was a lot of work, but I will be honest I was distracted by holiday events and starting University and that's why it took so long to complete. There is so much to go over with Combat() that I'll be making separate posts for each piece of the Combat class with breakdowns on what they do and how. Here I'll post the results and an implementation overview. Comba() as of now: class Combat( object ): def __init__ ( self , continueStatus = True ): self .order = [] self .listing = {} self .continueStatus = continueStatus self .taunt = [] self .defRaise = [] self .atkRaise = [] self .protected = [] self .exp = 0 def combatantOrganizer ( self ): organizedOrder = [] theStringOrder = [] NumOrder = [] for listing in self .order: NumOrder.append(listing[ 1 ]) NumOrder.sort() for...

UML Diagram and Object Oriented Programing.

Currently, the game uses only global variables and the methods in theMain.py to open and load data. It's become cumbersome to constantly call on the global variables for all my methods and I've realized that I'll be limited in the number of monsters I have if I only use global variables for everything. So this has led me to decide to shift to using Object-oriented programing to run my game. Thus I've prepared a UML diagram to show you all my classes, and subclasses, as well as their interactions, methods, and variables.      theMain.py will function as my main line where all classes and methods will be called as well as have some very important functions built into it. That's they it is connected to almost all the other classes. It'll take care of exploration, descriptions, story tracking, starting the game, ending the game, encounter rates, and gold.      GameMenu will be treated as a static class that has information displayed for the game menu as well as...

Item() rundown

 The item() class holds the information of the item and also runs the item effect when it gets used. Constructor def __init__ ( self , command , name , cost , usage): self .effect = command self .name = name self .cost = cost self .usage = usage The effect holds the string name of the effect for the item,  usage holds the value of the Effect . The rest are self-explanatory. EffectHandler() def effectHandler ( self , user: PlayableCharacter , equip= True ): #learned how to specify type of parameter. if equip: if self .effect == "Def" : user.defense = user.defense + self .usage elif self .effect == "AtkPhy" or self .effect == "AtkMag" : user.attack = user.attack + self .usage else : if self .effect == "hp" : user = self .healing(user) return user This handles the effects of the item when it is used. If equip is true then it will check for the equip...