So that picture looks pretty odd. The size of the picture should indeed be 1280x1280. Makse sure you've the correct mode on. Perhaps you could follow my tutorial wich perhaps can help you with your problem. Just follow all the steps and you'll be fine...I hope. If not, take the script again 2morrow since I think I'm going to put my Reborn version online.
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 ;)
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 keep getting an end of archive error when I try to download it, I think something might have gone wrong when you uploaded it. I can't wait to test it
~Miget man12
__________________________
By the way:
I'm bored because it's summer so I decided to drop by for a bit.
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 ;)
Mmm well I think it's just working. When I download it it's working fine. And I've uploaded it to my own website so the chance that it's not working isn't that big I guess. Well anyway, let's hope it keeps working
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 ;)
Oke so sorry for the dubble post but I have to make this anouncement now
I won't be online till 05-08-'09 since I'll be in Sweden selebrating holiday. Though you can still keep posting, I'll awnser all replies when I get back.
Post about what you think of the script, what can be improved and if you have suggestions or found any bugs.
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: 96
Type: None
RM Skill: Beginner
Hey SojaBird, gotta say, I love the script! It makes all of my levels look fantastic!
I have one probelm though, your script allows each level to have one light layer and one shadow layer. Ot it can have a spot light thing that follows the player. Im glad you have these features, but what if someone (like me) has a level that is both indoors and outdoors at night, so that one would need to have a light/shadow layer to portray the darkness and illuminate the windows, but also would need the spot light so that they have limited sight when walking around?
In other words, I would like to be able to make my level have both a light/shadow layer for the map, AND a spot light that follows the player. And you cant really do that on one map
Maybe you could add the feature to have both kinds of light on the same map?
Hope that made enough sense
EDIT: Oops, it turns out you can do that afterall through your latest update lol. Way to beat me to the punch!
This post has been edited by FauxMask: Aug 1 2009, 02:38 PM
Group: Member
Posts: 96
Type: None
RM Skill: Beginner
Is there a way to turn a spot light on/off during using a switch? As far as I can tell now, If I use a spot light (in otherwords mode = 2), then it is active in all of my maps, which I dont want Any help anyone?
Okay, after reading through everything it sounds like there is a way to turn on/off the spotlight by using a switch, but I really cant figure out how! Would anyone please help me? I read through all the instructions and watched the video 3 times and I dont understand how to make a switch to change the light mode.
Please, will someone help me? Okay. I figured it out, but it wasnt noob friendly lol. So for anyone who was like me and didnt know how to make the spot light turn on or off via a switch, you just look in the script and at the top is "Call Scripts" and under that is something like "AL::mode(var)" or something, and you change the var to the mode number you want to change it to. Then just make a common event with that and set it to a switch.
This post has been edited by FauxMask: Aug 2 2009, 11:24 AM
Oke so let's help some of you out...if it was neccesary So first @eflyefl, thanks for liking it haha, I also just love that random color dude
@FauxMaster Well it seems you're a fast learning student Haha, good that you found all those things out yourself I'm sorry if some things are a bit complicated. Perhaps I'll make that switch thing in a new version
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 ;)
#------------------------------------------------------------------------------# # How to use # #------------------------------------------------------------------------------# # *AutoLight # # MODE 0/2 # # To use autolights, put a light- and/or shadow-map picture in the # # folder ../Graphics/Pictures/ # # Name to picture correct! Start with the, by you set, light- and/or # # shadow-map name, followed by the corresponding map-ID. # # Put the AutoLight mode to 0 or 2 to show light- and/or shadow-maps. # # # # MODE 1/2 # # To use the spot, put your spotpicture in the folder ../Graphics/Pictures/ # # and set the name correct! # # Put the AutoLight mode to 1 or 2 to show the spot. # # # # # # *EventLight # # To make a event cast a light, give it a comment with the following code: # # cast(*picture, *color, *opacity. *blend_type, *zoom) # # All the parameters are optional. Default they are set to: # # picture: Default, set in the module # # color: White # # opacity: 255 # # blend_type: 1 # # zoom: 1 # # For the color you can choose: # # - white # # - red # # - green # # - blue # # - yellow # # - orange # # - purple # # - random (one of above, but not the same as it is at the moment (if set)) # # # #------------------------------------------------------------------------------#
#--------------------------# # Customization AutoLights # #--------------------------# module AL
def check_existence(file) format_list = [".png", ".jpeg", ".jpg"] format_list.each do |format| return true if FileTest.exist?("Graphics/Pictures/#{file}#{format}") end return false end
def create_lights @viewport = Viewport.new(0, 0, 544, 416) case Mode when 0 draw_light draw_shadow when 1 draw_spot when 2 draw_light draw_shadow draw_spot end update end
def dispose case Mode when 0 dispose_light dispose_shadow when 1 dispose_spot when 2 dispose_light dispose_shadow dispose_spot end @viewport.dispose end
def dispose_light return if !(@light_exist and !@light.nil?) @light.dispose end
def dispose_shadow return if !(@shadow_exist and !@shadow.nil?) @shadow.dispose end
def dispose_spot return if !(@spot_exist and !@spot.nil?) @spot.dispose end
end
#--------------------------# # Script eventlight engine # #--------------------------# class EventLight
attr_reader :event_lights
def initialize create_autolights end
def create_autolights @event_lights = {} $game_map.events.values.each do |event| next if event.list == nil event.list.each do |list| if (list.code == 108 or list.code == 408) and list.parameters[0].include?("cast") data = eval(list.parameters[0]) el = Event_LightHolder.new(event, data) settings(el, data) @event_lights[event.id] = el update end end end end
def cast(pic = EL::Default, color = "white", opacity = 255, blend_type = 1, range = 0, zoom = 1) return [pic, color, opacity, blend_type, range, zoom] end
#---------------# # Read event_id # #---------------# class Game_Interpreter
attr_reader :event_id
end
#---------------------# # Change Functions AL # #---------------------# module AL
def self.mode(val) @val = val return if !fixnum?(@val) eval("AL::Mode = #{@val}") $AutoLight.dispose $AutoLight = AutoLight.new end
def self.light(parm, val) @val = val case parm.capitalize when "Name"; @val.to_s! when "Visible"; return if !boolean?(@val) else; return if !fixnum?(@val) end eval("AL::Light::#{parm.capitalize} = #{@val}") $AutoLight.dispose $AutoLight = AutoLight.new end
def self.shadow(parm, val) @val = val case parm.capitalize when "Name"; @val.to_s! when "Visible"; return if !boolean?(@val) else; return if !fixnum?(@val) end eval("AL::Shadow::#{parm.capitalize} = #{@val}") $AutoLight.dispose $AutoLight = AutoLight.new end
def self.spot(parm, val) @val = val case parm.capitalize when "Name"; @val.to_s! when "Visible"; return if !boolean?(@val) else; return if !fixnum?(@val) end eval("AL::Spot::#{parm.capitalize} = #{@val}") $AutoLight.dispose $AutoLight = AutoLight.new end
def self.flicker(parm, val) @val = val return if !fixnum?(@val) eval("AL::Spot::Flicker::#{parm.capitalize} = #{@val}") $AutoLight.dispose $AutoLight = AutoLight.new end
end
#---------------------# # Change Functions EL # #---------------------# module EL
def self.bitmap(val, index = nil) @val = val index = $game_map.interpreter.event_id if index == nil $EventLight.event_lights[index].el.bitmap = Cache.picture(@val) end
def self.color(val, index = nil) @val = val index = $game_map.interpreter.event_id if index == nil old_value = $EventLight.event_lights[index].el.tone $EventLight.event_lights[index].el.tone = pick_color(@val, old_value) end
def self.opacity(val, index = nil) @val = val return if !fixnum?(@val) index = $game_map.interpreter.event_id if index == nil $EventLight.event_lights[index].el.opacity = @val end
def self.blend(val, index = nil) @val = val return if !fixnum?(@val) index = $game_map.interpreter.event_id if index == nil $EventLight.event_lights[index].el.blend_type = @val end
def self.visible(val, index = nil) @val = val return if !boolean?(@val) index = $game_map.interpreter.event_id if index == nil $EventLight.event_lights[index].el.visible = @val end
def self.range(val, index = nil) @val = val return if !fixnum?(@val) index = $game_map.interpreter.event_id if index == nil $EventLight.event_lights[index].range = @val end
# String/Fixnum -> Boolean def boolean?(val) return false if !(val.is_a? FalseClass or val.is_a? TrueClass or val.is_a? String or val.is_a? Fixnum) @val = eval(val) if val.is_a? String if val.is_a? Fixnum or @val.is_a? Fixnum val = @val if @val.is_a? Fixnum if val == -1 or val == 1; @val = true elsif val == 0; @val = false else; return false end end return true end
# String -> Fixnum def fixnum?(val) return false if !(val.is_a? Fixnum or val.is_a? String) @val = val.to_i if val.is_a? String return true end class Sprite alias mm12_autolight_change_sprite_init initialize def zoom__x return @zoom__x.is_a?(NilClass)? 0 : @zoom__x end def zoom__y return @zoom__y.is_a?(NilClass)? 0 : @zoom__y end def zoom__x=(val) @zoom__x=val if val.is_a?(Integer) or val.is_a?(Float) return @zoom__x.is_a?(NilClass)? 0 : @zoom__x end def zoom__y=(val) @zoom__y=val if val.is_a?(Integer) or val.is_a?(Float) return @zoom__y.is_a?(NilClass)? 0 : @zoom__y end end
Just replace your script with it; you won't need to change anything, but if you want to make an eventlight bigger, just add a 5th thing in the comment, e.g.:
CODE
cast(EL::Default, "white", 155. 1, 3)
Where the 3 at the end is the zoom amount.
~Miget man12
__________________________
By the way:
I'm bored because it's summer so I decided to drop by for a bit.
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 ;)
Well... It depends on what functions I need to add. For now it's only the zoom function. Though I think that's a pretty small thing to do so I'll wait with that 'till I've some more things to add.
So if you think of some other nice features I'll be able to pull it off in no time
EDIT! Oke so never mind the delay and stuff. I'll just post the new version now Only added the zoom function atm Check the first post for the new version (4.1 Reborn) The demo is also updated.
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 ;)
Games
Resources
RPG Maker VX
RPG Maker XP
Scripts
Tutorials
Downloads
AutoLight Reborn, Draw lights, shadows, spots and eventlights!!
Submit Your Article
Jul 12 2009, 02:45 PM
haha 
