ID:141241
 
Code:
image/target
layer=MOB_LAYER+1

mob/human/player/New()
if(!istype(src,/mob/human/player/npc))
spawn()src.regeneration()

..()

turf/Title
icon='title.png'
turf/Select
icon='title2.png'
turf/Creation
icon='charactercreation.png'
mob/proc/Get_Hair_RGB()
src.hair_red=input("How much Red do you want in your hair (1-150)") as num
src.hair_green=input("How much Green do you want in your hair (1-150)") as num
src.hair_blue=input("How much Blue do you want in your hair (1-150)") as num
if(src.hair_red>150)
src.hair_red=150
if(src.hair_blue>150)
src.hair_blue=150
if(src.hair_green>150)
src.hair_green=150


Problem description:ok i recently download a source just for the icons and stuff, i have my login screens but how do i get it on the game it self, heres some screenies:














I consider myself a good programmer and I make all of my games from scratch. I've read the DM Guide over 50 times and gone through the various tutorials each around 10 times.

Learn through reading, it'll get you farther than by downloading a source and making it "better" even thought you don't know how to code yourself.
Mysame wrote:
Don't be a ripping idiot without a clue.

This is not helpful at all.
If you want to criticise, fine, but be civil and give constructive feedback.
Support your points with valid facts and sources.
That is not only way more convincing (to a mature person, at least), but even helping those in need.

Nas331 wrote:
well ive talked to other programmers and they ve said the best way to learn is to download a source and to build off of that so **** =/

Yes, a lot of people will tell you that, but the problem here is that they might call themselves programmers and yet are not. I can call myself a cook as well, because I can "cook eggs" and I could call myself a mechanic, because I can "pump up a wire".
Non of that means that a real cook or a real mechanic would see me as fitting to wear the title.
Yes, they will hint you at learning by stealing a source code, because that is what they did (when failing to really learn how to program), in the wrong assumption that they would be good at what they are doing.
But when you take a look at reality, an engineer does not learn how to create a car by taking a Trabant (symbolising bad source code) and tuning it, without ever having read about cars before.
Not only is the "future engineer" bound to break the car while trying to tune it, not having any knowledge, but s/he can never really break free from the bad design decisions made to create the car.
Or, in the realms of programming, a (bad) source code can never teach you object-oriented working, nor show you all the possibilities of a function that only the documentation would.
You are stuck with the bad habits and limitations of these that came before you.

You can see that when looking at your code relatively simple.
You're asking the user for three colour values, when you could use the "as color" argument, to make use of BYOND's internal and great looking alternative, where a user can just click on the colour of her choice!
Needless to say which one is more user friendly and looks way better (professional).

This does not mean that you should not work with code.
The opposite is true. Only by writing, by trial and error can you fully master the tasks head of you, but, make sure that it is your own errors you're bothering with.
Take the guide and not only read it, but work with it.
Use the reference to look up functions and explore their interface. Read up on articles written by (not only self called) programmers.