Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[chaoticag]

I think I'll take a break today for now.
Here's the code so far, and it works fine up until it needs to display the name. For some reason, that function refuses to want to work.

Code: [Select]

class Player:
def __init__(self):
self.name = 'somebody'
def namePlayer():
playerName = raw_input()
print(playerName)
def displayName():
print(self.name)

def main():
Me = Player()
print ('YOU ARE A MIGHTY ADVENTURER, WHAT NAME HAVE YOU!?')
Me.name = raw_input()
Me.displayName
return 0

[Darvi]

Well, for one, your namePlayer method uses a variable called playerName that doesn't get used anywhere else.

Of course that cannot be it because that's why the 'somebody' at initialization is there for.

Try this?

Code: [Select]

class Player:
   def __init__(self):
      self.name = 'somebody'
   def displayName(self):
      print(self.name)

def main():
   Me = Player()
   print ('YOU ARE A MIGHTY ADVENTURER, WHAT NAME HAVE YOU!?')
   Me.name = raw_input()
   Me.displayName
   return 0

[Chris_24]

Code: [Select]

Me.displayName
should be

Code: [Select]

Me.displayName()


[Darvi]

Right.

Why do I never notice the most obvious things <_<

[chaoticag]

Ah, so you have to use self for functions that affect themselves. Go figure. Well, I went with Darvi's suggestion and it worked, then I went ahead and tried to make naming restricted to using a function, which works too. Here's the cleaned up code.

Code: [Select]

class Player:
def __init__(self):
self.name = 'somebody'
def namePlayer(self):
playerName = raw_input()
print(playerName)

def main():
Me = Player()
print ('YOU ARE A MIGHTY ADVENTURER, WHAT NAME HAVE YOU!?')
Me.namePlayer()
return 0

[Max White]

Try the following. Like I said, model view separation.

Code: [Select]

class Player:
def __init__(self, name):
self.name = name

def main():
print ('YOU ARE A MIGHTY ADVENTURER, WHAT NAME HAVE YOU!?')
Me = Player(raw_input())
return 0

[Biag]

You can put the input prompt inside the raw_input() statement, by the way. Like so:

Code: [Select]

def main():
        me = Player(raw_input('YOU ARE A MIGHTY ADVENTURER! NAME THYSELF: ')
Also, it's good programming practice for all your variables to start with a lowercase letter, and save the capitalized words for classes. In a game, for example, you would have the "Player" class and the "player" variable, which stores an instance of that class.

[chaoticag]

And back, time to post an even more cleaned up version of the code. And yeah, I know about naming variables and stuff, I just slipped there, so oops.
Anyway, this time, the code is about 9 lines, with 3 of those lines more or less there for debugging (the displayName bits):

Code: [Select]

class Player:
def __init__(self,name):
self.name = name
def displayName(self):
print(self.name)

def main():
player = Player(raw_input('YOU RE A MIGHT ADVENTURER, WHAT NAME HAVE YOU!? : '))
player.displayName()
return 0
Now, I'm fairly sure that improving on this code is very unlikely, as this is as simple as it gets. So what next? We have a player, and he has a mighty name, but not much else.

[Darvi]

Make some sort of combat? Pit him against an enemy and see how it works out.

Bonus points if you can get your character to shout a battle cry on a critical hit >:3

[chaoticag]

Okay, so before I move on to implement that, it seems complex enough that it'd need some planning out before hand. So here we go.

We want you, the fighter-guy-dude(tte) to fight monsters for the glory of (insert god/ideal here). Now, this is much more complicated than a program that gives you a nametag then shuts off.

So we'll need the following:
-Hitpoints, for both the player and the enemy
-Attack, in order to hit stuff
-Damage, in order to hurt stuff
-Random numbers, in order to randomly miss and stuff.
And so on.

First, we need to define an enemy class. Then we need to go ahead and give it some stats, starting with hitpoints. Once we have hitpoints, we'll work on erasing them and seeing what happens with the code we have in place. Now we can't cheat and only have one instance of the enemy, that'd be stupid, since it'd interfere with us later on.

That's the goal so far, tings having hitpoints and dying, to be replaced with new things.

[chaoticag]

And now, for something completely different.

Spoiler (click to show/hide)

Code: [Select]

import random

def main():
        x = 0
        while (x < 10):
                x = x+1
                divisorA = random.randint(1,10)
                divisorB = random.randint(1,10)
                print divisorA * divisorB, 'divided by', divisorB, 'is:'
                answer = int(raw_input())
                if answer == divisorA:
                        print 'correct!'
                else:
                        print 'wrong, the answer is', divisorA
        return 0
if __name__ == "__main__":
    main()

So, that code is something I cooked up while tutoring my little sister on division. Sadly, she never got to be my Ginny pig, but it works!

And then, there is something else. A friend of mine wrote this code:
Bonus points if you can decipher what it does (I take no responsibility on what happens if you actually run it)

Spoiler (click to show/hide)

Code: [Select]

def problem(): return (os.mkdir(os.getcwd()+"\\subdir") if not os.path.exists(os.getcwd()+"\\subdir") else None, file(os.getcwd()+"\\subdir\\"+md5.md5(str(random.random())).hexdigest(),"w").write(reduce(lambda x,y: str(x)+" "+str(y),range(0,100))),open(os.getcwd()+"\\subdir\\"+max(map(lambda x: [os.path.getctime(os.getcwd()+"\\subdir\\"+x),x],os.listdir(os.getcwd()+"\\subdir")))[1],"r").read())[-1]