now it has undefined proc, i'm a newb at this ( u can tell) and this the the coding i got for click() i have no clue if it has the part u want but i thopught i might as well try..

client/Click()

pretty small huh...lol
don't no if that's the click() proc

• Delete the line that said mob/proc/NewChar() (and the one after it for Load()).
• Remove the slash in front of proc/NewChar() on the line that begins the proc itself.
  
  You didn't do the second thing. If you had, you wouldn't have had an undefined proc error.
  
  You also did another thing I've talked to you about several times. Whenever you make a change, you almost never post the code you changed to show what you did differently. If you do that, people can make comparisons. And that's important because you only ever make about half the changes anyone tells you to. And when you encounter a problem with that, you don't go back to reread what they said to make sure you did exactly what they said; instead you just go off and try things totally at random, like this client/Click() nonsense.
  
  Please don't take this the wrong way; I don't mean to be harsh here. But nobody can help you if you only pay attention 20% of the time, and then only poorly. You have to listen to what I say, not just skim it and nod and go off and make a half-baked attempt. When you have a problem, do the following things that I've told you each several (or many) times before:
• Post the relevant code, always. In this case that meant not only the NewChar() proc, and the Click() procs for your buttons, but also the other line that you deleted (the mob/proc/NewChar() line). It's better to err on the side of posting too much code than too little; obviously no one needs to see your whole game, but you only showed small pieces at a time. It was like trying to see your code through a keyhole--I only saw the real problem tonight because you never showed a very important line until now. Nobody can help you this way. Post all the relevant code, and do it consistently; don't post one section today, another tomorrow, and a new one the day after that.
• Whenever you make a change, post the same sections of code to show what you changed. This is vital. It's about ten times as vital in your case because you never make all the changes you need to; you make one or two at most and then stop. Then you tell us you did everything, even though you didn't, but you don't post the code so we can see you didn't.
• If something isn't working out for you, go back and reread to make sure you got it right. Do NOT just try random stuff. All that does is make the problem worse: You introduce brand new bugs, which require more changes that you never get around to making, and half the time you don't show those sections so we can't tell you did anything else. Trying random stuff is what caused this whole problem in the first place: You made a syntax error (the / in front of proc/NewChar()) that gave you a message you didn't understand, and you tried a random solution for it; lo and behold it compiled, but it didn't work right, all because you tried something without really looking. Instead you should have asked the question: "Why does it say 'undefined proc' if it's right there?" If you'd asked that on the forums first we'd have had a good answer for you; if you'd just taken a close look at the line where NewChar() is defined you probably would have realized (given time of course) that the / didn't belong there.
  
  Finally, and this is very key:
• Actually try to understand what you're doing. It doesn't look to me like you're doing that at all. I've seen people put in an effort on code they have trouble understanding, and this isn't it. You're not making that effort. You're just doing one or two things at a time, wrongly, and then doing one or two things on top of that that are even worse, and then you come back for help but you don't even take the time to ask for help in a constructive way by giving people the details they need. So far you haven't been trying to understand what you're doing; you're just putting in code blindly.
  
  There's a scene in UHF that goes like that: A blind man turns a Rubik's Cube and says to the guy next to him, "Is this it?" And the other guy says, "Nope!" Over and over. That's what you're doing here. If you want to solve the problem, take the time to look at it.
  
  I hope this doesn't discourage you; my point is to encourage you, to code with both eyes open. Doing it blindly as you have been, you're only wasting your time and ours. But if you actually apply yourself to figure out what's going on, you'll spot problems quicker and be a lot less frustrated.
  
  Lummox JR

client/click

turf/Create/creating_character
layer = MOB_LAYER+150
NewCharacter
icon = 'create.bmp'
Click() usr.NewChar()
density = 1
LoadCharacter
icon = 'load.bmp'
// icon_state = "create"
Click() usr.Load()
density = 1
i no the proc/NewChar spacing isn't right... my tab is screwed up I think that's the click() thing...

Click() usr.NewChar()

Click()
  // this is called "type-casting"
  var/mob/creating_character/M = usr
  // this will check to see if M is the type it's supposed to be
  if(!istype(M)) return
  // it's the right type, so call NewChar().
  M.NewChar()