#Rpg maker vx ace screen size how to
#Rpg maker vx ace screen size code
#Rpg maker vx ace screen size windows

= Graphics.height - code positions the window on the screen. An objectвЂ“in this case, an instance of the Window_ClassвЂ“is a copy of that template that we can work with. Remember: a class is a templateвЂ“an abstract concept. WeвЂ™re also creating a new instance of the Window_Gold class to store in that field (which will call the initialization code we saw earlier). WeвЂ™re essentially saying, вЂњwhenever weвЂ™re displaying a Menu scene, store a copy of the Gold window in the sceneвЂ™s field.вЂќ That way, we can reference the gold_window whenever necessary. At this point, we might actually want to read the code line-by-line to see whatвЂ™s going on (although, since weвЂ™re removing the window it doesnвЂ™t really matter): = Window_Gold.new

If we read down a bit, weвЂ™ll actually see the method. Right there in the start method, thereвЂ™s a call to a create_gold_window method. WeвЂ™ll check our other candidate, Scene_Menu: We know our gold window is simpler than that. вЂ¦ but this seems to reference actors and menu commands (created by the set_handler method thatвЂ™s called in start). We might then skip to the Scenes section, since the gold window is likely part of a scene.

If we simply delete Window_Gold, then that code will cause a crash. We should assume thereвЂ™s code in another class thatвЂ™s creating a new instance of Window_Gold. You might be tempted to think that we could just delete Window_Gold and be done, but code doesnвЂ™t exist in a vacuum. ThatвЂ™s OK, because weвЂ™ve narrowed down our search. Note that if the classes, properties, and methods are named well, we donвЂ™t actually have to read through each one line-by-line to guess what it does.)ДЄfter skimming the code, it looks like Window_Gold doesnвЂ™t actually help usвЂ“it defines what the gold window looks like when itвЂ™s shown, not whether itвЂ™s shown. Indentation and commentsвЂ“lines that start with a #, which indicate to Ruby they shouldnвЂ™t be executedвЂ“are used to make it more readable. Each of these blocks is closed by an end statement. (How do we know that? Well, the code for a class is contained in the class block, and each def block represents a property or method within that class. It has properties like window_width that define how the gold window is shown, and value and currency_unit that define what the gold window shows. Upon further inspection, this class has methods like initialize, refresh, and open. The Window_Gold class might catch our eyeвЂ“it sounds exactly like what weвЂ™re looking for: Since we have a vague idea of what the class that shows the gold window might be named, we can identify possible classes and skim them to see if they actually affect whether or not itвЂ™s shown on the menu screen. Within these groupings, we know weвЂ™re probably looking for a class with Gold, Menu or Status in the name (since weвЂ™re looking for the gold window on the status menu screen).

#Rpg maker vx ace screen size windows

We know weвЂ™re looking for a window, so odds are the code is in a class that starts with Window_ or Scene_ (since scenes often show and hide windows on the screen). ItвЂ™s intimidatingвЂ“unless you have both copious programming and RPG Maker experience, it takes some effort to scan through it and figure out what it does.ДЇortunately, we have a few guidelines to help us. Step 1: WhereвЂ™s the code that affects this?ДЄs discussed in the last post, thereвЂ™s a lot of Ruby code in a default RPG Maker project. Our first step is to dive into the Script Editor: The player wonвЂ™t be distracted by trying to figure out which features are used and which arenвЂ™t, and wonвЂ™t feel like we hacked this together. We could leave this window in, but itвЂ™s going to contribute to a tighter experience for the player if we remove unnecessary bits. In this sort of game, we might not have the concept of вЂњgold.вЂќ However, because RPG Maker provides a complete JRPG engine, itвЂ™s there on our status screen anyway: LetвЂ™s say weвЂ™re building a narrative-only game (like To The Moon), or a game where we want to tightly control the playerвЂ™s progression by giving items or skills at key narrative points (sort of like Legend of Zelda). (Admittedly, this is exactly how I did the LD37 project.) ItвЂ™s sort of like taking a list of common phrases when traveling to a foreign country.

#Rpg maker vx ace screen size how to

Note that IвЂ™m not formally teaching you how to write Ruby hereвЂ“IвЂ™m just teaching you enough to be able to guess what a particular line of code might do. If you want to create a new project, you should be able to follow along. So, letвЂ™s walk through how weвЂ™d think through a very simple change. From the comments I got on it, I realized вЂњinfo dumpвЂќ is not an exaggerationвЂ“itвЂ™s literally a bunch of abstract, raw information without any examples, and so itвЂ™s confusing if you havenвЂ™t messed with it before. My last post was basically an info dump on what IвЂ™d learned about RPG Maker Ruby scripting during Ludum Dare 37.