ForeverZer0

They may have made the method for convenience, but this is not how things would, or even should work. If I specify I want text drawn, and I want it to use this region of space to do it, I would not want it "automatically" start exceeding that. That is an added feature for amature game makers, that actually restricts control. If you want to create a similar method, just split the text into an array, using the '\n' character to determine where to split. text = "my string with line breaks\nis going to use\nthree lines." text.split("\n").each_with_index {|str, i| self.contents.draw_text(0, i*32, self.contents.width, 32, str) }

That doesn't work in RM, or really any graphics library that I know of. Line break and carriage returns are for writing to files, and are not parsed by the graphics context. It is simply creating a graphic based on the string and drawing it to the screen at the coordinates you specify. Your trying to mix operations of two unrelated things.

It be fixed now. Order has been restored. :)

I am not going to write it for you. If you can't look in Window_Selectable, look at the update method, copy the code, and make one slight edit, how do expect to create a whole menu system? If you seriously want to script a menu system, you are going to have to understand the base classes used for windows, its kind of a requirement... Check out some beginner tutorials for RGSS, especially pertaining to Windows, and perhaps some Ruby ones on inheritance. They would do a far better job than I am in a single post explaining it. I am sure there are some good ones on the forum here.

Don't call super in the update method, and make your own implementation. I assume it used Window_Selectable, so when you call super in the update method, its going to use the default up/down method used in it.

No, I never made one. If you know how to script, it simply a matter of creating the various pieces and defining the ways they are allowed to move. You can use a 2D array or Table to track locations of them on the board. Its actually pretty basic. Is your game online, or do you plan on having two people sit next to each other on the same computer and play? If its online, you need to give a lot more information, if its sharing a computer, then it would be easier, but in my opinion rather pointless, especially if it supposed to be a part of a larger game. I have never played an RPG where one of the mini-games in it made me go find someone else to play with, or force me to play against myself.

=~ does not mean "is there a match", it returns the position of a match if there is one, or nil if there is not. Either way, there isn't really a right or wrong, its just coding style.

True. Its a habit of mine, and I like doing it personally. Same as I use parenthesis for method calls surrounding the arguments, use a "return" at the end of methods instead of just writing the value, etc., etc. In my personal opinion, it makes it a littler clearer what is actually going on for the next person who reads the code. Without it, someone who does not know may think the value returns a boolean, when it actually doesn't, although Ruby allows nil to be used the same as false in most situations. I actually don't like that Ruby allows for such a thing, as it is a bad habit if one ever plans to move beyond Ruby into other languages. Most, if not all (at least common ones), other languages don't allow such things.

If its two player, its not real difficult. If its AI based, then it is really difficult. There are gigantic tables that are used in traditional chess games for AI. You would need to find them and create a Ruby wrapper for it to even get started.

Its the INDEX of the actor in the party, not the ID of the actor. First actor in party = 0, second actor = 1, etc, etc. If you want to use by actor ID, replace $game_party.actors with $game_actor[iNDEX].

It depends on if you know how to script or not. If you know how to script, a simple party switch without all the frills is relatively easy, just a scene with a couple windows, and a few functions on moving array elements around. If you don't know how to script, well, its a bit more complicated. You are not going to learn how to make a full script in a matter of a couple days, and you need to get the basics of Ruby and RGSS down before you can even start. The RMXP help manual is an invaluable tool for this, as it explains the core classes, and some basic Ruby 101 stuff.

Place this anywhere below Scene_Battle. It simple removes and stores the first actor in the party before battle actually begins, and adds him/her back as the scene exits.

I take you are creating an event-based party switcher? Although they are very possible, they are very messy when using many characters, requiring loads of conditional branches to do correctly. Its kinda hard to answer your question without more information, or even better a look at your implementation so far. I don't understand what a your first sentence means about the "text storage system" or "taking someone back" means in regards to events, not without seeing your event.

All you need is something simple, nothing complicated. class Scene_Battle alias remove_leader main def main actor = $game_party.actors.shift remove_leader $game_party.actors.unshift(actor) end end

Never used this script, but after looking at the code, yes, you can simply add a call script at entrances/exits to do just what you asked.

Welcome!

Serial numbers in RGSS just aren't practical. Serial numbers are usually made by performing an algorithm on the hardware id. It's extremely simple to view RPG maker scripts, even with encrypted games, which will expose the algorithm. After that, its a simple matter of using it to generate your own serial number. I am farely confident that any competent scripter could crack a serial number system in less than five minutes. It's just that easy. You wouldnt even need to reverse it, just completely bypass it.

Serial systems kind of become useless when the script is basically open-source.

MoonPearl's suggestion is the way to go. Your exact RegEx for the name "gus" to place in your scripted conditional branch would be: ($game_party.actors[iNDEX].name =~ /[Gg][uu][ss]/) != nil This would return true if the word "gus" is in the name at any point, ignoring capitalization. Alternatively you could use: ($game_party.actors[iNDEX].name.downcase =~ /gus/) != nil

I use my HTC Evo 4G at on lunch breaks at work and stuff to check the few forums I frequent, including this one. I stick with portrait since it is easier to use one-handed as Polraudio mentioned. It has a resolution of 1280x720.

That's a very good question, and frankly, I have a hard time coming up with any type of definitive opinion on the matter. The fact that he is an amputee is no matter, and should not be. If I remember correctly, there is a young woman on the table tennis team (I don't remember which country) who has an arm amputated. She obviously uses the other arm to play, so there isn't really any issue that can be made of that. This particular case begs the obvious question: Are the artificial legs an advantage? I see no way that this can be truly confirmed nor denied, which is the cause of my indecision on making an opinion. I will say this much: I am against allowing under the premise of "look what he has overcome, give him a chance...". An unfair advantage is an unfair advantage, and has nothing to do with what happened in a person's life to get them their. That being said, and if it was my decision to make, I would probably allow it. There is no real evidence to suggest that he has an advantage. The artificial limbs do not appear to give him extra "bounce", and they certainly don't make his thighs pump any faster. I am confident that the issue was thoroughly investigated by the Olympic committee, and the decision was not made lightly to permit it.

Sorry, it means "quoted for truth". :P

Yeah, my code is pretty static in that it only shows one set of text. It would only take a minor edit to be able to supply arguments for what text is used, but I was lazy; I only spent 2 minutes on the whole thing.

QFT