Yea so a call script event is some action to do something with a script you're using. Actualy it's pure coding. So I'm not sure now how it goes with tge autolight cause I'm not fully functional at the moment on my iPod. Though open the script and I'm sure there's some help in there. I'm sertain that I've written special and easy to use call-script options in the script. I thought it was something like
CODE
AL.mode = 1
but I'm not sure. I should check the script when I'm back @ home again
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: 3
Type: None
RM Skill: Undisclosed
I couldn't find any help but I tried to make an event and clicked on advanced>Script... and wrote "Al.mode = 1", but when I start the game and activate it I get an error called : NoMethodErroroccured while running script. Undefined method `Mode=' for AL:Module.
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 ;)
I think its because there's no such thing as Graphics folder anymore and if the script checks if a light/shadow graphic for that map existed it returns false...
what i want to know is how to make it so that they will check if the file exist inside the encrypted > Game.rgss2a
I found out that thats the bug preventing an encrypted project to check if file existed... so its returning false ending up displaying nothing
This post has been edited by Legion Saga: Aug 25 2010, 03:51 PM
Darn I hadn't tested that when I made the script... It's a pretty nasty bug wich makes the script quite useless since you want to encrypt your game at some point obviously. This encrypting though, is also a problem I have to solve for me. Cause, you see, the encrypting is to protect the gamefiles so they can't be red anymore (not easily at least). So I have to find a tiny hole in that encryption so I can see what files are in there.
I'll have a look at it rather soon, cause well... This should just be solved. Thanks for letting me know
Greatzz, SojaBird.
ps. I'll post back here when I know anything more.
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: 4
Type: None
RM Skill: Undisclosed
I've been wondering, will you develop the already almighty script (besides the "bug" solution)? I don't know what others think, but for me another - independent - light mode would be of great help. I'm using your script instead of Thomas Edison VX, 'cos it gives much better results - like no pixelation. Then again, with your script as it is, I can't assign independent light modes to street lamps (lit at night only) and indoor candles (lit round the clock). I know it's easy to get round this, but the actual situation in my little game is a bit more confusing, which makes it hard to explain. I just wanted to give you a basic insight into the problem.
You actualy can set independant lights. The newest version of the script also includes the lightmode EventLight wich makes it possible to set a infinite amount of light-sources by making them correctly with a event. You could try the demo to see how they work
I'm sure you'll figure it out
Greatzz, SojaBird.
ps. Let me know if you need anymore help, I'm glad to help.
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: 4
Type: None
RM Skill: Undisclosed
Yea, I know about that. I didn't make myself clear, sorry.
I don't like it when light gets through walls, so I just use the basic Light 'mode' for every light source, and adjust the light to fit the area/image. That way the area looks both beautiful and realistic. I don't have the slightest idea if it's possible to add another Light 'mode' or how difficult it'd be.
Thanks for a fast response. Seeing how long the script's been on already, I didn't expect the reply just the day after.
Oke so what you're actualy saying is that you like to have the eventlight only show up, say at walls and not at the top of that. I'm not sure if it's possible but I could see if I could add some kind of mask-layer for the eventlights so you can mask-off the part where you don't want that to be shown. If I figure that out I'll be able to get a new mode out pretty quickly. I might have a look "rather quick" since it's some new and interesting material to look into.
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 ;)
The masking part would likely need to be tied into the autotiles that are used for roof or ceilings. It would actually be pretty complicated, I think, to make that work right :S
__________________________
[Show/Hide] Witness the mystery of my SIGNIATURE! Will you dare to uncover the truth?
Group: Member
Posts: 4
Type: None
RM Skill: Undisclosed
QUOTE (SojaBird @ Sep 16 2010, 01:32 AM)
Hey kreaven,
Oke so what you're actualy saying is that you like to have the eventlight only show up, say at walls and not at the top of that. I'm not sure if it's possible but I could see if I could add some kind of mask-layer for the eventlights so you can mask-off the part where you don't want that to be shown. If I figure that out I'll be able to get a new mode out pretty quickly. I might have a look "rather quick" since it's some new and interesting material to look into.
Greatzz, SojaBird.
Thanks, that would be great as well. I think that what I'm in need of may be done a bit differently. Maybe I'm too demanding, but seeing how much the script can do as yet makes you think that it can go one step further. It already gives quite the possibilities to make realistic lighting. I'll post a screen, it'll ease the explaining.
As you see, that's the lighting I like (not complete yet). I have a candle in a different room that when lit triggers the Light mode on (through AL.light("visible", true)) and vice versa. Now, when the candle is put out, the lights in the screen's room (let's call it so) are put out as well, although they shouldn't. I found a way to get round it somehow, but it may get confusing in the future.
With EventLight I can't get same results, so I have to stick to Light at this stage. If there were two triggers, life would be easier. Of course the two Lights (two triggers = two Lights) can't be used together on one map, as far as I know, but why would I use them together? I can imagine how it would work, but I don't know how to put it into practice, so I turn to you.
Using my 'game' as an example, I blow out the candle in the first room (AL.light2("visible", false)). Then I get to the next room - a.k.a. screen's room - where the lights are still on (AL.light("visible", true); I didn't change this one to false). I hope you understand what I mean. Is it possible?
We could also apply a different approach - make the Light2 comment-dependent. When you put a comment like "cast.light(...)", the Light2 would appear. I'm not even an amateur when it comes to scripting, so I can only give some ideas.
Another thing. As you see on the screen, there are no EventLights. When I put it into the right candelabra, it works wonders. When I put exactly same comment into the left candelabra, it doesn't work. I've been trying to figure it out. No success yet.
I hope I didn't make it worse with these explanations. They were to clear things up...
This post has been edited by kreaven: Sep 17 2010, 02:42 PM
@Braska Dealing with tile-ids and such is not something I am not experienced in, so I might figure that out. Though I'm not realy sure if I'll be using that methode to obsure the parts that shouldn't be shown. I'll have to come up with a better solution to fix this.
@kreaven Oke so thanks for the explanation. I'm not sure if I understand it quite good enough but I think I know what you meen. It's more like you would want to use the EventLight kind of setup though then for the other mode right? Like you have several parts of the light and shadow pictures for seperate parts of a map/candel. I actualy did though about this in the past, but it got lost in the proces making the script and time passing by. I'm realy gonna reconcider this and see if I could work it out for a new script or script-version with lighting.
'Bout the candle thing problem not working... that's odd. I'll have to take a look in that as well.
And in the end it all comes back to the part where I have to say when I'm able to work on this and what not. Well, that's the hard problem. I've left scripting behind a bit for the last year cause of my other very demanding works and projects. Though I'm sure I'll get back to this at some point. Getting feedback only makes me want to come back more quicker so thanks for that.
Anyways, I hope you'll be able to hold it out for a bit longer
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: 4
Type: None
RM Skill: Undisclosed
QUOTE (SojaBird @ Sep 18 2010, 12:43 PM)
Oke so thanks for the explanation. I'm not sure if I understand it quite good enough but I think I know what you meen. It's more like you would want to use the EventLight kind of setup though then for the other mode right? Like you have several parts of the light and shadow pictures for seperate parts of a map/candel. I actualy did though about this in the past, but it got lost in the proces making the script and time passing by. I'm realy gonna reconcider this and see if I could work it out for a new script or script-version with lighting.
'Bout the candle thing problem not working... that's odd. I'll have to take a look in that as well.
Yea, I should've put it that way in the first place - EventLight mode's kind of setup, but in Light mode. I think that would solve the problem. And don't thank me for explaining. I should thank you for reading my way too long and complicated explanations, ha ha.
As for the candelabras, the odd thing is, there's no problem with a similar configuration on a different map (two torches there). I'll try fumbling with it a bit, maybe I'll come out with a solution. Maybe "extracting" the map from the game will help. I'll give you the results later.
Oh, and thanks for responding so fast and good will. Most people would lose patience already.
Edit I now know what caused the problems with EventLight. I used custom images of higher resolution. When used these in events close to the upper edge of the map, EventLight simply refused to work. Is there a way to solve this? Zooming in a small image doesn't work, just like zooming out a big one. I'm almost 100% certain you did mention something about the edges somewhere...
By the way, solving this is not that important, I guess, as you can easily get round it. Oh, and no worries, I can wait. I'll just skip over to some other things.
This post has been edited by kreaven: Sep 18 2010, 09:46 AM
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: 9
Type: Developer
RM Skill: Beginner
This is just too great But I had this problem when I was using it for my game. I'm using Yanfly's Menu script(I just wanted to point it out for reference) and every time I'd press a button to go to the menu all of the light and shadow's disappear D: I really want this script for my game but I just can't find a way around it.
Here's a screenshot
Never mind what I just said, I just found a way to fix it Great Script and I'll be giving you credits on it.
This post has been edited by puddinman: Mar 26 2011, 08:15 PM
Group: Member
Posts: 1
Type: Writer
RM Skill: Beginner
I love the look of this script, but I am trying to figure out how to get it to work so the player has a light on him - like he's carrying a torch or radiating light. I've looked over the demo, but there's nothing in it to show the player emitting light. Is there a way to do this with this script?
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 ;)
Games
Resources
RPG Maker VX
RPG Maker XP
Scripts
Tutorials
Downloads
AutoLight Reborn, Draw lights, shadows, spots and eventlights!!
Submit Your Article
Aug 8 2010, 02:32 AM
Great Script and I'll be giving you credits on it.
