Can't promis anything right now, just 'cause I've out this scripting thing for quite some time (and still are). Though I just feel I have to return something to the community and such.
Btw, peeps can follow me on Twitter @The_SojaBird Though I'd just mention it since that would perhaps boost my scripting a bit
Anyways, keeping track of different things will be added...not sure 'bout the time thing yet though, have to figure that out. I might rewrite the whole condition-thing for this...I'll 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 ;)
Group: Member
Posts: 10
Type: Developer
RM Skill: Skilled
Great script, But one compatibility error that either I can't find or I didn't bother reading anything. -But With Yanfly's Battle Engine Melody, your script changes the selection layout of the Main Menu Melody from YEM. The icons and the default selections from the regular VX menu appear, Whether or not in the Main Menu Melody some of those selections are off.
I placed your script above MMM, and I didn't see the selection in the menu pane. So I placed it below the MMM and it did (as I said ) changed the layout, however the achievements selection was still there. And If I place your script below Wora's Enemy bestiary, the achievements selection replaces the bestiary one. I tried tinkering with the setting in all 3, but it does not change anything. Also When i placed it above MMM and I tried opening the status menu or skill menu I got this error:
Script 'YEM Main Menu Melody' line 438: ArgumentError occurred. Wrong number of arguments(0 for 1) Any ideas?
And on line 438, This is the line: 437 Sound.play_decision 438 command = @command_window.method 439 case command
__________________________
Its mind over matter... I Don't Mind And You Don't Matter.
Try using my NewMenuItems script. It's not that my script isn't compatibil with others, it's just that the default way of using the menu is kind of odd. I suggest you use my NewMenuItems script to solve this Though I'm not sure how this will affect the other scripts you use wich may use a different layout for the menu. If that's the case, this script is totaly optimized to be the best at compatibilety issues so you could go to the other script-topics if they can help you out (since MMM is the main-menu engine you're using).
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: 10
Type: Developer
RM Skill: Skilled
QUOTE (SojaBird @ Oct 22 2010, 04:55 AM)
Hey hey,
Try using my NewMenuItems script. It's not that my script isn't compatibil with others, it's just that the default way of using the menu is kind of odd. I suggest you use my NewMenuItems script to solve this Though I'm not sure how this will affect the other scripts you use wich may use a different layout for the menu. If that's the case, this script is totaly optimized to be the best at compatibilety issues so you could go to the other script-topics if they can help you out (since MMM is the main-menu engine you're using).
Greatzz and goodluck, SojaBird.
Thankiez, Yes it works fine. After resetting the CONFIG part atleast 6 times to get it right, Everything runs smoothly. Although, I tried to add Woratana's Monster Book to it, I couldn't find a way past the Vocab::<blank> part. So I put in game_end with the scene call and changed the Quit vocab to Enemy Bestiary. Since I don't use the game_end feature in my menus its fine. ( I have no scripting knowledge, At the moment.)
If I put two scene scripts in the CONFIG ( i.e "start_actor_selection('skill')" ,"$scene = Scene_Skill.new" ) separated with a comma or etc; will this effect anything? Also, when using your New Menu Items the menu loads the scene scripts slowly, as in, it takes atleast 5 seconds to load the Item menu, Is this normal? Thanks
__________________________
Its mind over matter... I Don't Mind And You Don't Matter.
@DoubleElite So a clean project works. But when you go change things, it won't... Guess you do some things wrong then with the changing If you could show me how/what you've edited, I might be able to figure out what's wrong.
@Geung Good you got it running how you want. I think that putting two things as you want in there is a big problem. Should work just fine...I'd say go try it out The slowdown...that's pretty odd. Haven't realy noticed it yet. Though yea it could be normal, perhaps the script has to load and there isn't enough free ram at the point (yes also RPG maker VX can get very heavy processor wise).
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: 3
Type: Mapper
RM Skill: Beginner
QUOTE (SojaBird @ Nov 8 2010, 06:27 PM)
Does the script work without Achievements? If so... ... Perhaps put the script in a spoiler so I can check it out
xx SojaBird.
Hey thanks for a quisk reply, i have been playing around and reading everything i can find, and i noticed your NEW MENU ITEMS scripts i have now copy and pasted that into place,
i dont have pictures on my menu now tho i did have pictures next to each word e.g (picture) items, (picture) skills etc.
they work now tho, when i click on skills or equip i have to press it twice, the first click freezes the screen and the second click opens the selection eg skills.
so all i need now is icons to appear and get rid of this freeze i can send script f you want for the place that is having error (as i shown in picture?)
UPDATE: i just tryed doing a spoiler but getting error for some reason i will post a link to down load the script kk if thats kk?
When i open achivements up in the game i get the correct layout and everything except i get the fill bar empty of course but it says -999/5 and i cant seem to get that -999 to 0? its rather annoying? could someone please help?
and the second thing is super simple....but....
How do i make a shop....not a normal shop....but the shop or whatever so i can buy achivements in the game such as the one i just showed, as i tryed it as a normal achivement from start and found out about the -999 thing. if someone could explain in NOOB term how to make the shop thing etc
much appreciated thank you!!
This post has been edited by Dreamerboy07: Nov 8 2010, 02:40 PM
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 ;)
...And actor selection. I ended making my own cuz you never upgrade yours Soja. I invite you to check mine, and if you include all that mine can do, yours will be the best menu manager ever.
__________________________
Leon's Basic VX Scripts of Awesome: Step 1. Passive Skills- Create skills that add passive bonuses. (shitty) Step 2. Learning from Everyone- Learn skills from enemies, or allies, without being the target of the skill. (nice) Step 3. Dual Battle Landscapes- Set background and foreground image for your battles. (nice) Step 4. State Details- Add description to states, and allow viewing them on menu, and in battle. (nice) Step 5. Item Quality Colors - Colourize item, weapon, armor and skill's name according their quality or affinity. (very nice) Step 6. Skill Trees- Your actors can have talent trees now, like in the MMORPGs. (extremely nice) Step 7. Main Menu Manager- Easy, straight, and intuitive total control of commands for the main menu. (very nice) Drawing commissions are open. Facesets... monsters... anything: click here.
I had a look at your script... DANG it's awsome! Think I have to rewrite the whole NMI and get a new easy format with more features
Well tnx for the awsome example. You might want to pick the few things I have that you like 'bout the script (auto-add?) and incorporate them in your script? Good luck!
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 tried to understand back then how you made the auto add thing, but I'm not that good haha. That's why I tell you: If you add all that mine can do into yours, it will be the best one.
__________________________
Leon's Basic VX Scripts of Awesome: Step 1. Passive Skills- Create skills that add passive bonuses. (shitty) Step 2. Learning from Everyone- Learn skills from enemies, or allies, without being the target of the skill. (nice) Step 3. Dual Battle Landscapes- Set background and foreground image for your battles. (nice) Step 4. State Details- Add description to states, and allow viewing them on menu, and in battle. (nice) Step 5. Item Quality Colors - Colourize item, weapon, armor and skill's name according their quality or affinity. (very nice) Step 6. Skill Trees- Your actors can have talent trees now, like in the MMORPGs. (extremely nice) Step 7. Main Menu Manager- Easy, straight, and intuitive total control of commands for the main menu. (very nice) Drawing commissions are open. Facesets... monsters... anything: click here.
I was searching for a quest script ... this one is incredible . If i don't have compatibility issue , i will use it .
Just one thing : there is a small bug in the demo . The quest "Looser" is sometimes with one "o" and sometimes with 2 . So , we cannot complete the demo .
And a small advice : put the word "Quest" somewhere in the title of this topic because when someone is searching for a script like yours , he put "quest script" in the search box .
I have some questions : - Is there a newer version than this Beta 4.0 ? - Why is there an image achief_new.png ? it seems it is not used .
Games
Resources
RPG Maker VX
RPG Maker XP
Scripts
Tutorials
Downloads
Achievements, Add/manage/display achievements (like WoW/xBox) or use as questtracker
Submit Your Article
Oct 19 2010, 03:17 PM
.gif)
i did have pictures next to each word e.g (picture) items, (picture) skills etc.
Deadly Christmas setup. 8.04 score... this one was not so fail. Yay!
Twist of Fate. Worst game in the competition... Yay!
Tie with two more guys out of 6 participants, so fail... Yay!
If you think you figured it out PM me and if your correct you will earn this valueble skill... or you can just brag about it :D
