Chaos Project

RPG Maker => RPG Maker Scripts => Scripting School => Topic started by: Ryex on May 24, 2011, 07:41:51 pm

Title: Third Lesson, Know the System You're Working With
Post by: Ryex on May 24, 2011, 07:41:51 pm
Third Lesson, Know the System You're Working With




Because we are building our system to tie into existing scripts we need to know how the existing scripts work.

This next task is designed to familiarize you with how the RTP scripts work.

Make a diagram of the control flow of the RTP scripts. Show how everything is connected together with arrows. This is not to be as detailed as the last task it is just a general control flow. I'll give you a diagram of the main loop and how it connects the two of the scenes to get you started but it is up to you to fill in the rest.

This is a large and complex task, you'll have to read the RTP scripts and understand what they are doing. Right now your just trying to get the object modal and the control structure striate. Do don't bother with what individual methods and lines do. If you need help with what a particular block of code does feel free to post or PM me. Again, don't sweat the details, just get the general design of how the RTP scripts flow into your diagram

Use this diagram to start the process. If you feel it needs to be remade feel free to do so..

(http://img101.imageshack.us/img101/4979/text3299.png)

Title: Re: Third Lesson, Know the System You're Working With
Post by: cyclope on May 28, 2011, 07:17:22 pm
 :twitch: So we have to read ALL the default scripts and figure out what each word means? If so sounds like a long task but ill get to it...
Title: Re: Third Lesson, Know the System You're Working With
Post by: G_G on May 28, 2011, 07:51:59 pm
No, he's saying look at all the default scripts that are involved.
Title: Re: Third Lesson, Know the System You're Working With
Post by: Ryex on May 29, 2011, 01:44:13 am
actually I am telling you to to look at the entire RTP of scripts :\

don't look at each and every word. look at methods and classes and find their general purpose and how they are inter connected. yes it will take a while but you need to have an idea of how the RGSS scripts work.
Title: Re: Third Lesson, Know the System You're Working With
Post by: G_G on May 29, 2011, 01:46:53 am
Oops my bad :x. Misread the original post completely.
Title: Re: Third Lesson, Know the System You're Working With
Post by: Blizzard on May 29, 2011, 06:24:11 am
Nobody expects you to learn all the default scripts and what they do exactly. You are just supposed to go through them as you will recognize some patterns and that will help you later on.
Title: Re: Third Lesson, Know the System You're Working With
Post by: cyclope on July 11, 2011, 05:30:44 pm
I read all the RTP scripts, but do I really need to do the diagram?
Title: Re: Third Lesson, Know the System You're Working With
Post by: Ryex on July 12, 2011, 11:45:33 am
ok how about you just give a description of what each RTP script handles. i'll accept that instead.
Title: Re: Third Lesson, Know the System You're Working With
Post by: Jragyn on July 13, 2011, 08:51:53 pm
Game_Temp = all the various non-saved variables used all throughout the rest of the scripts.
Game_System = Holds many methods involving Audio, though holds variables that ARE saved throughout other scripts.
Game_Switches = Manages...switches. (max is 5000 apparently?)
Game_Variables = Manages...variables. (max is also 5000, by default.)
Game_Selfswitches = Manages the selfswitches with boolean logic. (uses hash instead of array like above)
Game_Screen = handles all the shaking and weather and flashing on the screen.
Game_Picture = takes care of all the displaying/moving/rotating/etc of pictures being displayed on the Game_Screen.
Game_Battler1/2/3 = Handles seemingly everything involved in converting a Game_Actor/Game_Enemy into a battle-able character; ie: defines methods of stats, gives battle formulas, explains states and their effects, skills/items and their usability...its huge and full of stuff useful to making sure a battle works properly.

To be continued tomorrow when I have access again to interwebs.