Group: Revolutionary
Posts: 137
Type: Artist
RM Skill: Undisclosed
QUOTE (AmIMeYet @ May 13 2008, 08:25 AM)
QUOTE (pim321 @ May 12 2008, 03:07 PM)
- Autogenerate mappicture (using Andreas21 and Cybersam "Screenshot Script")
You might want to know that this script is bugged for vista users who use the 'Aero' skin. They get a black screen.... (well, atleast with Woratana's neo save system, with wich I've seen it, but I don't know if the screenshot script is updated to fix this, though... ) Or have you already found a fix for this?
Not really, I use the Aero skin, and I have implemented the Neo Save System into my project. Works fine. o.O
@daredeamon thats true, there still is a boat on the picture, it's just what you like to have on the picture...you could also make a picture that isn't for that map...you can create very funny and cool things with that concept
@namio well I think it has something to do with your other scripts or the use of arial as normal font...try to solve that, it has nothing to do with MapRadar
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
Group: Member
Posts: 45
Type: Musician
RM Skill: Skilled
liek OMG dis skript Ownz n00bs hard rite i wuz in teh prossis of finding a good skript and i kame akros tihs 1 rite n i almost had a hartattck n stuf..
basically what i am saying is THANK YOU for this genious piece of code writer architecture its really a cool and fun feature to have in my game.. although i really need that *((Autogenerate mappicture (using Andreas21 and Cybersam "Screenshot Script"))* because if this means what i think it does it will save me alot of trial and error in drawing my maps (screenshots and ms paint lol) i cant seem to figure out what size my map needs to be for the radar to pick it up but ill keep at it until you incorporate this new thing.. i really need to learn RGSS2 myself lol i like coding and i actually understood ruby but i cant find a good tut on it... nonethe less THANKS again ill be looking forward to future installments of this =Ž
__________________________
Go not where there is as path and follow someone else, go instead where there is no path and leave a trail...
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
@pim321 I'm waiting to see the next version of your script. All I need is a world map which can be turned on and off using one key (M or what so ever) and that displays in realm time the position of the player. So if I'm in a town A and press M a picture/window appears and shows me the world map and a dot (the player) in town A. If I go out of the town and press M the same picture/window appears and shows me the world map and the dot which is outside of the town and so on. Like in GTA VC, SA (and many, many other games) where when you call the world map it shows you where you are.
This post has been edited by drebenk: May 16 2008, 05:03 PM
__________________________
Nobody dies a virgin. Sooner or later life f***s everybody.
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
Group: Member
Posts: 45
Type: Musician
RM Skill: Skilled
lol i copied over the old script with the new one and (im not sure) but i think the switch idea is whats now stopping the map from showing up entirely it could be an unforseen problem that i unforsaw but none the less the game works like always yet lo and behold... no map.. what do you think it could be? in the general configuration in the script the switch that controls wiether the map is used or not is default set to 1.. but theres no indication whitch one is true and which on is false.. i know im gonna feel like an idiot for this one because its probably the easiest solution but iv tried many things so far...
__________________________
Go not where there is as path and follow someone else, go instead where there is no path and leave a trail...
He pwner, thanks for comment and useing my script. I'm not sure what causes your problem but I'll just explain what you should check to help me out helping you.
At first, do you have "MapRadar v1.7.2"? Just go to the script and see in the first textline (line2) wich version it is. Next, see if at line62
CODE
UseRadar = true
is set, if it's
CODE
UseRadar = false
, set it to True, else the script won't load. Then, get to line13 and look what is set after
CODE
Radar_Switch =
. If it is as you say default 1, than when you go in the game, turn switch 1 on. You can also go to the OpacitySetup beneath line40 to see if the opacities of each picture isn't nil. Also what you need to look for is if your pictures have come in properly. To do so, get to the project and open the "Resource Manager" (fourth button from the right on the top bar). Get to the picturefolder and do a preview on every picture (at least the maps). See if under the PictureSetup (line18) the width- and heigthvalues aren't set to nil. The problem can also be that you have set the custom placement to a negative number, not realy obvious but just to be sure. When you have this, the pictures are drawn outside the screen wich causes the Radar also not to showup (at least not visable for you).
More I can't think off... If you still have the problem, pls post wich scripts you have other than "MapRadar v.1.7.2".
Update me pls what your conclusions are when you've solved to problem.
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
Group: Member
Posts: 45
Type: Musician
RM Skill: Skilled
lol like i said was going to be an easy solution... it was the fact that i had to turn (in my case) switch 12 on which i set to mapradar but i got a new problem after that lol now when i use an event to turn on the switch the event freezes the whole game lol... dont worry though i should be able to solve this one momentarily (im not a complete noob lol) thanks for your help though woratana your still the shit man
on another note im actually picking up a bit on this code language =) i slowly began scripting what i like to call (project complete failure) im just starting simple i need to learn more things like modules aliases and all that but for the time being im starting from nothing at all and trying to get it so at the input of a button (j) my charactor jumps forward once lol (not the most brilliant idea but i still wanna try to start somewhere lol) im beginning to account for the fact that means you could jump over impassable walls and say into water .. ill need to make an instant death scenario for when you jump directly onto an impassable tile.. lol
like i said its a work in progress but its fun as hell..
thanks again woratana your the shit man =) happy trails
This post has been edited by tehpwnerer: May 20 2008, 09:43 AM
__________________________
Go not where there is as path and follow someone else, go instead where there is no path and leave a trail...
I know I still got some problem with that eventing stuff...I can get it to turn the map on and off but when I try to open it again, it printing a error...Still need to fix that...However
About learning to script, it's just Trial-And-Error, well actualy...that's how I got into this (I'm still a bit n00by on this but he, I posted some scripts allready )
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
Group: Member
Posts: 45
Type: Musician
RM Skill: Skilled
Unbelievable... not only does this new code work.. but i ACTUALLY figured out EXACTLY how big to make my map... it WORKS BEAUTIFULLY
just for referance for anyone else who might have the same problem with largescale maps where the radar dont line up properly.. in the database my main map is 250 by 250 (database terms) in MS paint i had to make the bitmap an astounding 2000 pixel by 2000 pixel... i dont know the exact math behind this but using this as a referance maybe anyone with the same problem can sort it out?
thanks a million for this beautiful script pim you really rule dont think of yourself as nooby my man because i couldnt code half this myself IM nooby lol your pro..
thanks again ~Teh~
__________________________
Go not where there is as path and follow someone else, go instead where there is no path and leave a trail...
@pim321 mate can you make a demo with the new script version? I saw the screenshot from the 1st page of this topic and I want this thing to happen when I'm on a map a image showing wider area to appear on the radar map. So can you make a demo with the new 1.8 ver. that wil look like the screenshot on the first page?
__________________________
Nobody dies a virgin. Sooner or later life f***s everybody.
@pwner the math behind it is that you take your amount of tiles wich is 250 and multipy that with the playerindicator size (yours is 8*8) in script at line 28 you'll find this
CODE
# You need a picture of every map you want to display in the Hud, where the width=PlayerSize*[number of X-tiles] and where is the height=PlayerSize*[number of Y-tiles]
@drenbenk allright I'll make that, im not as good with demo's, im also working on my AutoLight demo atm but i'll just post that projectfile from the screen
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
@pim321 good script mate and a good demo too. One problem when I put image of one of my maps (size 192x192) instead of the one you've put it works fine. BUt if I copy paste one of my maps in your demo and put the two guys on my map and start the game it doesn't even start. It just shows me black screen for a sec and turns the game off. So what do I need to do in order to aplly your script to my game? Will copy/paste (above Main) work? I'll also copy/paste the images for the player indikator and the map frame.
__________________________
Nobody dies a virgin. Sooner or later life f***s everybody.
well what error do you get? the picture u're using for your map need to have the correct name, els it won't work check the map id and changes your picture name so that it corresponds with that map
works now?
o and yes, just copy paste will work, though to set it up, you do have to create these map pictures and all...so be sure that all is set correct
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)