Group: Member
Posts: 29
Type: Event Designer
RM Skill: Advanced
My problem is that all my modifications to the menu are to add scripts of YERD and of KGC, only your Achievements script is wanted to add in the menu, or there's some way to remove it of the menu and open it for example with a common event?
sorry for my bad english xD
__________________________
All of u!!! Please!!! Sorry for my bad english xD
Actual Project: Tales of a Lost Memory
Current Progress: Histoy: 10% Maps: 2% Scripts: 95% Database: 90% Translated into English: 0% (I'm actually considering it xD)
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: 29
Type: Event Designer
RM Skill: Advanced
Oh, grate, So now I can us it with the KGC & YERD CMC, so thnx, I'll put you on the "credits & thnxs"
Edit: Sorry, me again, how I can remove it of the menu? When I add the script, erease the CMC configuration, and put the original menu with the achievements option, How I can remove this?
This post has been edited by IkaruTak: Jul 14 2009, 05:15 PM
__________________________
All of u!!! Please!!! Sorry for my bad english xD
Actual Project: Tales of a Lost Memory
Current Progress: Histoy: 10% Maps: 2% Scripts: 95% Database: 90% Translated into English: 0% (I'm actually considering it xD)
You meen get rid of the menu-modification? You can manualy remove that part from the script. Though I'll try to make so that it's compatible with those otherscripts in the next version (I'll try).
Anyway, Delete it manual? Get rid of the lines 799-893 That'll remove the whole menu part.
So...version 1.4 is comming up as well With point system
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: 72
Type: Writer
RM Skill: Advanced
Actually, I'm using this script with the YERD and KCG menu, so you don't have to delete the module. Hold on, I'll edit the post with what you have to do
>Make sure to put this script above the YERD menu script >Under Imported commands, you'll see this:
CODE
IMPORTED_COMMANDS ={ # These can only be from 201 onward. # -ID => [HideSw, DisbSw, Actor?, Title Name, Scene Name.new] 201 => [ 8, 9, false, "Quests", "Scene_Quest"], 202 => [ 10, 11, false, "Factions", "Scene_Factions"], 203 => [ nil, nil, false, "Rows", "Scene_Row"], 204 => [ nil, nil, false, "Records", "Scene_Record"], 205 => [ nil, nil, false, "Crafting", "Scene_Crafting"],
>Then go back to menu commands, which looks like this:
CODE
MENU_COMMANDS =[ # Make sure you've read the instructions above. 0, # Items 1, # Skills 2, # Equipment 3, # Status 15, # Bestiary 206, # Quest Log 10, # Party 4, # Save 5, # System
] # Do not remove this
# The following determines the maximum number of displayed rows for the # customized command window. MAX_ROWS = 10
>(Yours will look a little different since i'm using different menu items than you) >Change MAX_ROWS = 10 to MAX_ROWS = 11 so the Achievements Window will fit in >Under the last menu item, insert the number you gave the Achievements menu under imported commands, so it will look something like mine:
CODE
MENU_COMMANDS =[ # Make sure you've read the instructions above. 0, # Items 1, # Skills 2, # Equipment 3, # Status 15, # Bestiary 206, # Quest Log 10, # Party 4, # Save 5, # System 207, # Acheivements
] # Do not remove this
# The following determines the maximum number of displayed rows for the # customized command window. MAX_ROWS = 11
Hope this helped
This post has been edited by Malexos: Jul 15 2009, 03:41 AM
__________________________
Support Mr. Peebles!
[Show/Hide] My User-Card (Thanks to Holder from RRR)
Group: Member
Posts: 29
Type: Event Designer
RM Skill: Advanced
LOL, sorry, again, It seems that I attract the bad luck, now I can put the Achievements scene in a common event, I start to customize, well, but I have no chance to do nothing lol xD
If I only put: Start_Achievements = #[Title, Description, Icon, Hidden, Hide_Icon, Completed] ["First steps", "Complete your first equip", 1897]
The game crashes at the start and pop-up this error:
Script 'SojaBird_Achievements line 129: NoMethodError occurred.
private method `gsub!' called for 80:Fixnum
And if I add more to imitate what your you put: Start_Achievements = #[Title, Description, Icon, Hidden, Hide_Icon, Completed] ["Welcome", "Welcome to Tales of a Lost Memory", 141], ["First steps", "Complete your first equip", 1897, true], ["Victory!", "Win on your first battle'",85,true,false], ["Gold seeker", "Get 10000 G", 142]
Group: Member
Posts: 72
Type: Writer
RM Skill: Advanced
@IkaruTak: If you follow my post, you won't have to edit much to get the Achievements script working with the YERD menu. It works excellently and with no problems on my game.
__________________________
Support Mr. Peebles!
[Show/Hide] My User-Card (Thanks to Holder from RRR)
@Malexos Thanks for posting how to use it with YERD's script. Though it will not work the correct way. Try get a achievement completed and then open the menu. The achievement-alerts won't go away. Now if you open the item or skill scene you'll find that the achievement-alerts will show on top of the help-window at the top. That's why I've written the Achief.call methode wich will get rid of the achievement-alerts.
@IkaruTak Can you pls sent me a copy of your game/script cause I don't know what could be wrong. The first error you get is based on a wrong input. It seems that you've the number '80' as name or something for a achievement The second one you're getting...I think it comes from your common event. I'm not sure but I guess it is... Your common event (that you're calling with YERD's menu right) should only have a codecall with the next in it
CODE
Achief.call(true)
That should do the trick. If you get me a copy of your game/project/script I'll be able to help some 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 ;)
Oke so I'm still working on the update wich is going to be epic nice. So it has the point system included and also a shop for buying and unhiding achievements. I'll post it today. The compatibility is not done yet but for now I'm sure you'll be able to pull it off the default way by modifing those menu scripts you're using. So that's for a later version or add-on.
Hope you're gonna like it.
Oh and I also found some bugs again so I've fixed those as well. Now the start-up's will show correctly, also if there's only one in the list (that causes fixnum problems).
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: None
RM Skill: Undisclosed
Hey Soja, If you find a way to fix IkaruTak's first error, can you please post how you did it, because i'm getting a similar error when i try to make my own/change the origional starting achievements.
Yep it's all in the new version. I prommise to post the new version today. It'll have the whole new feature of the pointsystem wich can be checked as conditions and can be spend in a special shop to buy new achievements and to reveal hidden ones when points are paid. Also in-message show of the amount of points. I've also been working on the reward display. It's not optimal yet, though a bit better.
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 ;)
"Get rid of some nasty bugs such as the start-up-bug and reward-bugs."
I'm asking since I'm using the old version (1.3) and I like it more then the new one (plus I already configured it and I really don't want to do it again with the new script). I don't want the points window, I also don't want the points shop and stuff like that. So what are these "nasty bugs" and "reward bugs" that have been fixed in the new version?
__________________________
Nobody dies a virgin. Sooner or later life f***s everybody.
Group: Member
Posts: 13
Type: None
RM Skill: Intermediate
This version is great once again !
I have a suggestion for rewards, without blocking the view :
When you complete an achievement, something like showing the little "completed achievement" window (the same size as the first version), and 2 seconds after replacing it with the "reward" window : a same-sized window that include the icon of the achievment, located as the same place.
I don't know if i've been understood, it's quite difficult to explain...
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
Jul 14 2009, 12:42 AM
