Group: Member
Posts: 81
Type: None
RM Skill: Beginner
Say my character is Ralph,when I open the status window It goes directly to he's stats,while in the menu when you press enter you have the option of choosing who's status in your party that you want to see
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: 96
Type: None
RM Skill: Beginner
Hey can you make it so that it doesnt disable the menu, so that it still pops up when you press a button? I know someone else already asked this, but you didnt give a solution on how to edit the script to allow it. Thanks
I don't know about anybody els asking for it but you'll be the one that will be heared It's not a real hard job but it'll have to wait till I return from my holiday break to Sweden. I'll be back at the forum, say the 5th or 6th of August '09.
But thanks in advance. You all 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
QUOTE (pim321 @ Jul 18 2009, 03:37 PM)
Hey,
I don't know about anybody els asking for it but you'll be the one that will be heared It's not a real hard job but it'll have to wait till I return from my holiday break to Sweden. I'll be back at the forum, say the 5th or 6th of August '09.
But thanks in advance. You all can still keep posting, I'll awnser all replies when I get back.
Alright, and thanks for being friendly
So the question remains, does anyone else know how to get back the main menu by pressing Q? Much please and thank you.
Could you make it that the players themselves could set the keys to what they want opened? Like I'd use X to open up Skills while my friend would use X to open up Items instead. That'd allow for better and more personal customization.
Group: Member
Posts: 71
Type: Developer
RM Skill: Advanced
I noticed a problem if you didn't know yet...Anytime during an event, if you press the buttons to activate the menus, the events stop and the menu comes up. Also, if there is no character in the party, the script gets an error.
I think I'm going to spend more time revieuwing all of my old scripts and make reborn versions of it so that it has more features and more throughthought things...and that all is working So this script will be one of them. Though perhaps I'll update it
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 ;)
class Scene_Item < Scene_Base def update_item_selection if Input.trigger?(SojaBird_TLM::Item2) Sound.play_cancel return_scene elsif Input.trigger?(Input::C) @item = @item_window.item if @item != nil $game_party.last_item_id = @item.id end if $game_party.item_can_use?(@item) Sound.play_decision determine_item else Sound.play_buzzer end end end end
There's three lines missing at the beginning, under class Scene_Item < Scene_Base. Essentially, what happens without these three extra lines is that whenever you exit the Items menu, it takes you back to the actual main menu.
Here's the fix.
Code Fix
CODE
class Scene_Item < Scene_Base def return_scene $scene = Scene_Map.new end def update_item_selection (Don't add this. It's already in there.)
Derp to me if someone's already figured this out before me and posted it.
This post has been edited by Crescent: Apr 19 2011, 07:13 AM
__________________________
When life throws you lemons, don't make lemonade. Get angry!
Group: Member
Posts: 68
Type: Artist
RM Skill: Intermediate
I apologize for reviving a thread, but what am I suppose to do, make a new thread about something that has already been made. I know it tick people off to ask for something that has been repeated already. It also ticks people off to revive a thread. So either way I will be ticking people off, because it is unavoidable. But here goes...
Question about this script!
How will I go about setting it so that I can have skills set as the hotkeys and not the menu options. So that instead of cycling through all of the menus I can hit 1 or F1 to do "Fire Ball Attack?" While having the Menu as an optional way of selecting attack or pick another skill the player has, but did not set as a hotkey? Also how would you go about making these hotkeys customizable, so that I may be able to set my skill for any button on the keyboard?
This post has been edited by Jackal26: Jun 29 2011, 07:39 AM
__________________________
From these lips, a Ballad I tell; The light pierced the storm clouds, and down she fell; A lullaby from the reigns, that cleanses the breath; Her strife of forgiveness and has nothing left. -Jackal Himself
Don't let games be a service package, which is why I wish Playstation should get hacked again, with XBOX included! I want the world to learn a lesson of what is to come in the game industry in the future.
Please Hacker! Please Hack the hell out of Microsoft and Sony! If you do it again.You will be a God among men! For those of you that lost out on the money, that should make you even more angry and want to boycott the service package system that is coming in the near future.
@Jackal26 Guess I'll add some life to the topic aswell Now it is true that the script supports a methode of shortcut keys. Though the request you make can not be done with this script, I'm afraid (and very sorry). Linking to a skill or item or other sub-component will require addition code and conditions since they act differently. For example: Linking a skill to a hot key requires it to check if it is allowed to be cast (can't be cause on map for example, or you'd need a map-battle-system). I'm pretty sure I've seen other scripts do just that going around the forums somewhere. I'm sorry that the script didn't do what you'd hope it would.
@radis My motto used to be that my scripts were as compatible as they could be, so they could be used with any other propperly scripted scripts. Now this might not have been applied to this script, since it was one of my earlier ones. I'm known a bit with Yanfly's work and I have to say, it's a shame that the feature that my script adds to the game, isn't implemented her menu system script. I also have to say that the scripts Yanfly makes, aren't really optimized to be used with other scripts since they should provide a huge library of functionalities (shamefully not the one of shortcuts and such). I'm sorry to say, but it would be up to Yanfly to add the functionality or make her script compatible with this one
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
The Lost Menu, Open+close item/skill/equip/status/save/end with keys.
Submit Your Article
Mar 8 2009, 04:13 PM
Thanks
