Introduction Are you tierd of all those scripts who change the way your menu is going to look? A script that adds an menu-option wich causes you to put in lost of effort to get a good scripter to make your menu compatible with others with doe the same?
That time is gone!! With New Menu Items you can easily manage your menucommand-list and add ones of your own. But what's more!? Scripters can implent a function in their script so that you don't have to add their menu-items to your list...they'll appear on their own!
No more hard scripting, just a few clicks and New Menu Items is installed on your game. Now you can add every script that modifies the menucommand-list that you want withouth the pain of letting them work to gether properly!
Features v1.0
Simple menu-items management;
Make menu-disformer scripts compatible with each other in no time (follow the video-tutorial on how to get the correct information);
Easy implentation for scripters to make their scripts compatible with New Menu Items (look at the video how to do it);
The default menu-items are allready redesigned for the script!
v1.0.1
Bug fix: scripters add function moved from the ENGINE to the CONFIG part.
v1.0.2
The return_scene function is redefined, as well as the '$Menu_Items.new' creation for scripters.
v1.0.3
The '$Menu_Items.new' function can now also hold a string for the position. The new menu-item will be placed below the item with the string as name (for example,
CODE
$Menu_Items.new(Vocab::skill, "New Function", false, "p 'This is the new function!'")
Will place the function with the name "New Function" below the menu-item with the name wich is equil to the System-vocabular of 'Skill').
You can now turn of the default return_scene fix in the engine (just below the warning). This can, for example, be usefull in combination with my 'The Lost Menu'-script.
The top part of the script, the CONFIG, allows you to control the menu-items and their functions. In this way you can easily add commands to the menu from other scripts wich change the scene-menu optionlist. This part should be at least above all other custom scripts. If not the script will cause errors or disfunctionality.
The bottom part, the ENGINE, should be pasted, just above "Main". No script should be put below, since it can cause problems or disfunctionality of the script.
Compatibility VX only. Can be used to make all scripts that modify the the menu-item list compatible with each other.
Installation Put the CONFIG part of the script above all other custom scripts. Put the ENGINE part of the script just above main and below all other scripts. Configure the script if needed (when other scripts didn't implent the auto-add function for New Menu Items). Credit me pls.
FAQ Video's comming soon.
Terms and Conditions Credit me with site, and the script is free for use in NONCOMERCIAL projects. If anyone want some changes, please pm me or post it here, I'll track the topic.
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 ;)
But no video jet. Though I do am working on a very nice way to show the scripts to you all. So I've been working on a site (not scriptology yet, that's on a temporary stop now), wich is very fun and nice if I may say so Anyway, I hope to get that one to my saticfaction soon so that I can start using it
That's it for now. Oh yes...I also didn't made the video cause I've been working on a REBORN version of my AutoLight wich is turning out pretty good ...well it's almost the same though it works better now and is better compatible with other scripts
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
New Menu Items, The best way to control your menu-item list!!
Submit Your Article
Jun 5 2009, 04:04 AM
