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...
Post a Comment

Combat.combatOrganizer()

 This function is meant to organize all the combatants based on the initiative number they rolled in rollIntiative().

Local variables

def combatantOrganizer(self):
    organizedOrder = []
    theStringOrder = []
    NumOrder = []

organizedOrder is where the updated list will be stored and this will late be used to update the old order.  theStringOrder is where the names will be stored once the numbers have been organized. NumOrder is where the numbers will be stored and sorted from least to greatest.

The rundown

for fighter in self.order:
    NumOrder.append(fighter[1])
NumOrder.sort()

First, I take all the numbers from the order and put them in NumOrder. Then I used .sort to organize all the numbers.

for Num in NumOrder:
    for item in self.order:
        if Num == item[1]:
            theStringOrder.append(item[0])

Then I take the order and the NumOrder and match up the numbers with their owner’s names and store the owner’s names in theStringOrder in the same order that the numbers are in.

This is accomplished by taking one number from the NumOrder list and checking it with the pairings in the order. Then when I get a match I add the name of that match to theStringOrder, and move on to the next number in NumOrder.

counter = 0
while counter < len(NumOrder):
    organizedOrder.append([theStringOrder[counter], NumOrder[counter]])
    counter += 1
self.order = organizedOrder

I then set up organizedOrder by taking the NumOrder and theStringOrder and putting them in the organizedOrder together (name first then the number).  I used a counter to make sure the two values are being pulled from the same index in the lists which they came from. Finally, I take the order and replace it with the organizedOrder.

With the initiative, monsters, and everything in place,  combat is set up and all set to get going with turn().

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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...
Post a Comment
Read more

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...
Post a Comment
Read more