Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Blizzard

17661
This is a new template, BTW. (-_-')
17662
Welcome! / Re: this is nice!
January 08, 2008, 06:14:00 am
I will make two skins, a dark and a bright one, so people stop complaining. But this takes time, please bear with me.
17663
News / Suggestions / Feedback / Re: Fast Reply
January 08, 2008, 06:08:36 am
I tried to add one yesterday, but it screwed up the forum and I had to reinstall the forum. #_# As I said, give me some time, I'm not able to do it all at once.

EDIT:

Actually when I think about it... Forget it. I'm not gonna waste my time make it work. Simply turn on the forum's default fast reply box in Profile->Look and Layout Preferences.
17664
I don't want people to change their names as they like. I'll change your nickname by myself.
17665
News / Suggestions / Feedback / Re: CP on the move!
January 07, 2008, 11:02:17 pm
It's... 5am... I am... tired... I'm going to sleep now and will move my scripts, Tech4X and some other stuff tomorrow. I really can't keep my eyes open anymore. Hope you guys can move your stuff over here until then. :)

'night!
17666
Recruitment / How to make a good Recruitment topic
January 07, 2008, 10:54:55 pm
Quote from: NoumanHere is a good set of things to follow when manking a  Recruitment topic

- Method of communication. Please always add a way for the person to contact you.

- What's needed? Make a list, or note clearly what is needed (mappers, eventers..)

- Number of people needed per category. (2 mappers, 4 eventers...) Please don't go crazy asking for a large amount of people.

- What YOU will be doing in the project. I always wonder when seeing the large need for what they need and the large # of members needed, what will the person requesting be doing? Nothing? Taking the credit?

- Name of game (If you are already decided on that)

- Current process (again if you are this far post what you have done with the game so far, better examples more interesting the game will sound to people.

NOT GETTING MEMBERS?

- Start the game by yourself or with the current group and post examples of the game progress to attract members looking for openings.
17667
These forums are only for topics describing or requesting help with projects being made with RPG Maker. All types of RPG Maker are allowed.


  • Recruitment topics will be moved to the Recruitment forum, please spare us the trouble and post them there from the beginning on.
  • Topics that don't meet the movement standards will not be moved.

  • Topics that don't meet the basic standards will be locked.



If you want your topic to be unlocked or moved, please PM a moderator or admin.

Basic requirements

Preventing your topic from being locked, your topic needs to fulfill following requirements:


  • At least an idea of the background story of your project.

  • At least two paragraphs of text explaining the main story idea of your project.

  • Basic character description of various characters throughout the game. You can give some yet undecided information on characters like "Age: undecided yet".

  • At least one ingame screenshot of battles, maps, menu, etc. Don't post screenshots of the submenus and don't post title screens/gameover screens. You CAN post the title screen, but it will be not considered as one of those three screenshots.



Movement requirements

If you want your topic to be moved into the main Projects/Games section where it will get more attention, your topic needs to fulfill following requirements:


  • At least three paragraphs of text explaining the background story of your project.

  • At least three paragraphs of text explaining the main story of your project.

  • Detailed character description of various characters throughout the game. You don't need to post all characters and you don't need to post many. Post at least the ones you get familiar with in the first stages of the game. Preferably with battlers or facesets.

  • At least three ingame screenshots of battles, maps, menu, etc. Don't post screenshots of the submenus and don't post title screens/gameover screens. You CAN post the title screen, but it will be not considered as one of those three screenshots.

  • At least 30-minutes long demo download link. No demo, no moving.



Whenever possible, please include all downloads and a website link for your project in your topic, preferably near the very top of your initial post or at the very end. For example, if you have a recruitment topic for it as well, it would be nice to have a link at the top of your post.

You can find an example here
17668
New Projects / Places to get your game hosted
January 07, 2008, 10:49:25 pm
You can host your game at various places on the internet:





Please add more if you know some other hosting places. Best is to be free.



The free web hosts I recommend most:


  • www.freehostia.com
    250MB disk, 5GB bandwidth, MySQL (that means forums will work)
  • www.110mb.com
    5GB disk, 300GB bandwidth, high speeds, NO MySQL (that means forums will NOT work), but you can pay for MySQL
  • www.000webhost.com
    350MB disk, 300GB bandwidth, high speeds, MySQL (that means forums will work), keep in mind that the site was marked as fraudulent not because of the hosting, but because of their affiliate program which is fraudulent




The web hosts where you need to pay I recommend most:


  • www.icdsoft.com
    99,9% uptime, high speeds, 6$ for 1GB disk and 20GB bandwidth monthly or $10 for 50GB disk and 500 bandwidth monthly, hence the probability of overselling is basically zero

17669
RPG Maker Scripts / Re: BEFORE asking for help...
January 07, 2008, 10:39:28 pm
Must've gone missing. Want me to add it to every copy of this post I made?
17670
Troubleshooting / Help / BEFORE asking for help...
January 07, 2008, 09:52:21 pm
NOTE THAT THIS WAS ORIGINALLY MADE BY ZERIAB!

If you do decide to post, please be specific. It's impossible to help a person saying: "I get an error, why?"
Answer these questions when you make a new topic or chance are, you will be asked a variant of those questions.

  • 1. What RPG Maker you are using?
  • 2. What exactly is the problem you are encountering?
  • 3. In which environment does the problem occur?




  • 1: Different versions behave different. You can get a solution which doesn't work with your version. This is a pity and a waste of time. Remember this!!!

  • 2: If you just say you have a problem it's hard to solve, because it can be one of a gazillion things.
    If you get an error message. Post exactly what it says.
    If it's an invisible error, like an event not behaving like it should. Post with which event the problem is and follow 3.

  • 3: By this I mean, when does the problem occur?
    Is it when you start the game? Start a new game? Talk to that dog?
    It's pretty important to tell when exactly you get the problem if you get an error message.
    If it's an invisible error (see 2.):
    You must tell when you notice the event behave being different.
    You must also write the event commands of the specific event and any other event where the existence of interaction is evident.
    If you have any custom scripts installed, tell about them too.
    Some of the things I mentioned here you perhaps shouldn't do as the situation in which problems occurs vary a lot. This can also be the most difficult to answer.

  • A general rule: The more specific you are, the better the chance of a proper answer.

    Also if your problem was solved, please change the title of your topic and add before [RESOLVED], like e.g.:
    Quote from: Old topic titleHow to make an item call a common event?

    Quote from: Old topic title[RESOLVED] How to make an item call a common event?
17671
Tutorials / BEFORE asking for help...
January 07, 2008, 09:52:17 pm
NOTE THAT THIS WAS ORIGINALLY MADE BY ZERIAB!

If you do decide to post, please be specific. It's impossible to help a person saying: "I get an error, why?"
Answer these questions when you make a new topic or chance are, you will be asked a variant of those questions.

  • 1. What RPG Maker you are using?
  • 2. What exactly is the problem you are encountering?
  • 3. In which environment does the problem occur?




  • 1: Different versions behave different. You can get a solution which doesn't work with your version. This is a pity and a waste of time. Remember this!!!

  • 2: If you just say you have a problem it's hard to solve, because it can be one of a gazillion things.
    If you get an error message. Post exactly what it says.
    If it's an invisible error, like an event not behaving like it should. Post with which event the problem is and follow 3.

  • 3: By this I mean, when does the problem occur?
    Is it when you start the game? Start a new game? Talk to that dog?
    It's pretty important to tell when exactly you get the problem if you get an error message.
    If it's an invisible error (see 2.):
    You must tell when you notice the event behave being different.
    You must also write the event commands of the specific event and any other event where the existence of interaction is evident.
    If you have any custom scripts installed, tell about them too.
    Some of the things I mentioned here you perhaps shouldn't do as the situation in which problems occurs vary a lot. This can also be the most difficult to answer.

  • A general rule: The more specific you are, the better the chance of a proper answer.

    Also if your problem was solved, please change the title of your topic and add before [RESOLVED], like e.g.:

    How to make an item call a common event?

    [RESOLVED]How to make an item call a common event?
17672
Event Systems / BEFORE asking for help...
January 07, 2008, 09:51:54 pm
NOTE THAT THIS WAS ORIGINALLY MADE BY ZERIAB!

If you do decide to post, please be specific. It's impossible to help a person saying: "I get an error, why?"
Answer these questions when you make a new topic or chance are, you will be asked a variant of those questions.

  • 1. What RPG Maker you are using?
  • 2. What exactly is the problem you are encountering?
  • 3. In which environment does the problem occur?




  • 1: Different versions behave different. You can get a solution which doesn't work with your version. This is a pity and a waste of time. Remember this!!!

  • 2: If you just say you have a problem it's hard to solve, because it can be one of a gazillion things.
    If you get an error message. Post exactly what it says.
    If it's an invisible error, like an event not behaving like it should. Post with which event the problem is and follow 3.

  • 3: By this I mean, when does the problem occur?
    Is it when you start the game? Start a new game? Talk to that dog?
    It's pretty important to tell when exactly you get the problem if you get an error message.
    If it's an invisible error (see 2.):
    You must tell when you notice the event behave being different.
    You must also write the event commands of the specific event and any other event where the existence of interaction is evident.
    If you have any custom scripts installed, tell about them too.
    Some of the things I mentioned here you perhaps shouldn't do as the situation in which problems occurs vary a lot. This can also be the most difficult to answer.

  • A general rule: The more specific you are, the better the chance of a proper answer.

    Also if your problem was solved, please change the title of your topic and add before [RESOLVED], like e.g.:

    How to make an item call a common event?

    [RESOLVED]How to make an item call a common event?
17673
Welcome! / Re: this is nice!
January 07, 2008, 09:49:23 pm
Just give me some time. And Rhett is the author of the skin.
17674
General Discussion / RPG Maker acronyms
January 07, 2008, 09:45:16 pm
Here's a list of commonly used acronyms to describe various elements related to RPG Maker.
QuoteABS - Action Battle System
A battle system from games like "The Legend of Zelda", "Secret of Mana", etc.

QuoteAMS - Advanced Message System
Message display system with many advanced options.

QuoteATB - Active Time Battle
A battle system from games like "Final Fantasy 4 - 9", etc.

QuoteATS - Advanced Timeflow System
A system that handles calendar, daytime and nighttime.

QuoteBABS - Blizzard Action Battle System
Same as Blizz-ABS.

QuoteBlizz-ABS - Blizzard Action Battle System
An action battle system made by Blizzard, currently exceeding every other ABS in configuration easieness, AI, non-lag and number of supported additional mini-features.

QuoteCA - Creation Asylum (www.creation-asylum.net)
A support forum for RPG Maker.

QuoteCBS - Custom Battle System
A term to describe any battle system other than the default.

QuoteCDS - Chaos Drive System
A system that allows character transformations. Now part of CLRS.

QuoteCMS - Custom Menu System
A term to describe any menu system other than the default

QuoteCP - Chaos Project (www.chaos-project.com)
The name of the game and the forum made by Blizzard.

QuoteCRLS - Chaos Rage Limit System
Chaos Drive System, Soul Rage System and Soul Limit System in one script.

QuoteDBS - Default Battle System
The default battle system from RMXP

QuoteDMS - Default Menu System
The default menu system from RMXP

QuoteDNS - Day & Night System
A system that handles the day and night cycle.

QuoteEXP - Experience Points
A value to describe how strong the character has become.

QuoteHP - Hit Points
A value to describe how much energy the character has.

QuoteMACL - Method and Class Library
A collection of more or less useful methods and classes.

QuoteMCL - Method and Class Library
Same as MACL.

QuoteMP - Magic Points (or Mana Points)
A value to describe how many points to spend on magic the character has left.

QuotePK v1.0 - Postality Knights (also called Dyna or Dynaemu)
The first illegal english translation of the Japanese version of RMXP. It's rather rare and hard to obtain.

QuotePKE v2.0 - Postality Knights Enhanced v2.0
The PK v2.0; an illegal english translation of the Japanese version of RMXP.

QuoteRM2k - RPG Maker 2000
An older version of RPG Maker.

QuoteRM2k3 - RPG Maker 2003
An older version of RPG Maker.

QuoteRMRK - RPG Maker Resource Kit (www.rmrk.net)
A support forum for RPG Maker.

QuoteRMVX - RPG Maker VX
The currently newest version of RPG Maker for the PC.

QuoteRMXP - RPG Maker XP
The most recent version of RPG Maker for the PC.

Quotermxp.org - RMXP.org (www.rmxp.org)
A support forum for RPG Maker.

QuoteRPGXP - RPG Maker XP
Same as RMXP.

QuoteRTAB - Real Time Active Battle
Same as ATB.

QuoteRTP - Run Time Package
A package of standard graphics and music.

QuoteSBS - Strategical Battle System
A turn-based battle system where players and enemies move around a battle map and execute actions. This system concludes tactical and strategical planning and sometimes battles take a lot of time to be fought. Similar systems can be found in commercial games like "Ogre Battle".

QuoteSDK v1.x - Standard Development Kit v1.x
A rewrite of the default RXMP to improve performance and compatibility. Performance was not improved and the SDK has only caused more incompatibility issues so far by separating SDK and non-SDK scripts.

QuoteSDK v2.x - Standard Development Kit v2.x
A new version of the SDK with more rewrites. Performance was decreased to improve compatibility. But SDK v2.0 is now even more incompatible with non-SDK scripts.

QuoteSLS - Soul Limit System
An Overdrive/Limit Break System based on the Soul Rage System. Now part of CRLS.

QuoteSP - Skill Points (or Spell Points)
Same as MP.

QuoteSRS - Soul Rage System
A system that mimics Ikari skills from "Lufia 2" for the SNES with enhanced possibilities. Now part of CRLS.

QuoteSSS - Skill Separation System
A system that can separate skills into "Black Magic", "White Magic", "Technics", etc.

QuoteSVB(S) - Side View Battle (System)
A battle system that shows the battle from the side. This system does not affect the type of battle (ATB, RTAB, etc.)

QuoteTBS - Tactical Battle System
A turn-based battle system where players and enemies move on a square tilemap and execute actions. This system concludes tactical and strategical planning and usually one battle takes a lot of time to be fought. Similar systems can be found in commercial games like "Final Fantasy Tactics".

QuoteTOA - Tons of Add-ons
The largest collection of little script snipplets with high compatibility.

QuoteUMS - Universal Message System
Same as AMS.
17675
General Discussion / BEFORE asking for help...
January 07, 2008, 09:44:39 pm
NOTE THAT THIS WAS ORIGINALLY MADE BY ZERIAB!

If you do decide to post, please be specific. It's impossible to help a person saying: "I get an error, why?"
Answer these questions when you make a new topic or chance are, you will be asked a variant of those questions.

  • 1. What RPG Maker you are using?
  • 2. What exactly is the problem you are encountering?
  • 3. In which environment does the problem occur?




  • 1: Different versions behave different. You can get a solution which doesn't work with your version. This is a pity and a waste of time. Remember this!!!

  • 2: If you just say you have a problem it's hard to solve, because it can be one of a gazillion things.
    If you get an error message. Post exactly what it says.
    If it's an invisible error, like an event not behaving like it should. Post with which event the problem is and follow 3.

  • 3: By this I mean, when does the problem occur?
    Is it when you start the game? Start a new game? Talk to that dog?
    It's pretty important to tell when exactly you get the problem if you get an error message.
    If it's an invisible error (see 2.):
    You must tell when you notice the event behave being different.
    You must also write the event commands of the specific event and any other event where the existence of interaction is evident.
    If you have any custom scripts installed, tell about them too.
    Some of the things I mentioned here you perhaps shouldn't do as the situation in which problems occurs vary a lot. This can also be the most difficult to answer.

  • A general rule: The more specific you are, the better the chance of a proper answer.

    Also if your problem was solved, please change the title of your topic and add before [RESOLVED], like e.g.:

    How to make an item call a common event?

    [RESOLVED]How to make an item call a common event?
17676
I have noticed that many people have problems putting my scripts in the right order into the editor. It's not that bad if it were only 3 scripts, but what if it are 6, 7 or even more...? Anyway, here is the script order that should work for my scripts.


  • ~ before the script name  means "multiple scripts" and scripts not by me.

  • Bolded script names are scripts by me.

  • Italic script names are script plugins by me.



Keep in mind that there are exceptions for scripts that need to be put between or below my scripts. Be sure to follow this suggested order, but always give priority to the instructions of other scripters! If they say to put a script at a specific location between or after my scripts, put it there.


  • XPA_Window

  • Resource Tester

  • ~ RTP scripts

  • ~ SDK

  • ~ Other people's scripts

  • Tons of Add-ons Part 1

  • Tons of Add-ons Part 2

  • Tons of Add-ons Part 3

  • Stormtronics CMS (any Edition)

  • RMX-OS Options

  • RMX-OS Script

  • Global Switches and Variables for RMX-OS

  • Remote Restart for RMX-OS

  • Blizz-ABS Part 1

  • Blizz-ABS Part 2

  • Blizz-ABS Part 3

  • Critical Sound for Blizz-ABS

  • Secondary Weapon for Blizz-ABS

  • Z-HUD for Blizz-ABS

  • EXP in HUD for Blizz-ABS

  • Random Action Sprites for Blizz-ABS

  • Auto-Targeting for Blizz-ABS

  • Rapid Fire for Blizz-ABS

  • Quick Weapon Switch for Blizz-ABS

  • Visual Equipment for Blizz-ABS

  • Blizz-ABS Controller for RMX-OS

  • Advanced Time and Environment System

  • Global Day-and-Night System for RMX-OS

  • Continuous Maps

  • Mouse Controller

  • Creation System

  • Pay to Heal

  • Chaos Rage Limit System

  • CRLS + Blizz-ABS plugin

  • Scene_SoulRage

  • Soul Force Combo System

  • Easy Overdrive System

  • Advanced Analyze System

  • Bestiary

  • Chaos Project Debug System

  • Dynamic Day and Night System

  • DREAM for Music Files

  • DREAM for Save Files

  • Easy Party Switcher

  • Unlimited Levels

  • Easy LvlUp Notifier

  • Custom Stat Growing System

  • Stat Distribution System

  • RO Job/Skill System

  • Full Reflection System

  • Blizz-ABSEAL (DO NOT USE IF YOU HAVE BLIZZ-ABS!!!)

  • ~ Main / ~ Modified Main



You do not have to maintain the exact order of my scripts, but I can't guarantee that there will be no problems if you don't. Individual scripts that I have created are not listed here. I will keep this topic updated.

Updated on 8.2.2016.
Updated on 10.2.2010.
Updated on 17.1.2010.
Updated on 14.12.2009.
Updated on 9.10.2009.
Updated on 30.7.2009.
Updated on 4.7.2009.
Updated on 8.3.2009.
Updated on 14.7.2008.
Updated on 13.5.2008.
Updated on 29.2.2008.
Updated on 19.2.2008.
Updated on 9.12.2007.
Updated on 13.11.2007.
Updated on 5.11.2007.
Updated on 25.10.2007.
17677
Scripting in RGSS Ruby for Intermediate and Experts
½th Edition
Author: Boris Mikić alias Blizzard



This is the ½th Edition! There might be typing and other mistakes!

Contents:

1. Introduction
  • 1.1. Why RAM or CPU?
2. Compatibility
  • 2.1. Aliasing
  • 2.2. Thinking in Advance
  • 2.3. Names and Problems
  • 2.4. "Stack level too deep"
  • 2.5. RAM or CPU?
3. Data Processing and Storage
  • 3.1. Why "looping"?
  • 3.2. Why Methods/Functions?
  • 3.3. How to handle Data efficiently
  • 3.4. Module or Class?
  • 3.5. RAM or CPU?
4. Windows
  • 4.1. The Basics
  • 4.2. The wrong Way to create a Window
  • 4.3. Do they look nice?
  • 4.4. Window or Sprite
  • 4.5. HUD Basics
  • 4.6. The Problem with non-vital Information being displayed
  • 4.7. RAM or CPU?
5. Lag-weg
  • 5.1. Algorithm Complexity
  • 5.2. What lags and why it lags (RGSS specific)
  • 5.3. Decrease Process Time
  • 5.4. Don't fear more Code
  • 5.5. RAM or CPU?
6. Wannabe-Cool Scripting
  • 6.1. Scripts with {} Brackets
  • 6.2. One Line Functions/Methods
  • 6.3. Too many useless and pointless Things
  • 6.4. Too much SephirothSpawn
  • 6.5. Avoid being an Idiot
  • 6.6. Re-invent the Wheel
  • 6.7. Enforcing Standards
  • 6.8. Scripts the World doesn't need
  • 6.9. RAM or CPU?
7. Hints and Tricks
  • 7.1. Pen on Paper or train your Brain
  • 7.2. "Game_System" is your save data's best friend
  • 7.3. Boolean Algebra
  • 7.4. The evil Bug in "if" Branching
  • 7.5. First this or that? - When "if" goes crazy
  • 7.6. The Trick with "unless" - De Morgan's Law
  • 7.7. Comparisons
  • 7.8. Instance Variable Access aka Encapsulation
  • 7.9. Powerful implemented Iterator Method "each"
  • 7.10. Bug Hunter
  • 7.11. Global, Local, Instance Variable or Constant?
  • 7.12. Inside-Outside or Outside-Inside
  • 7.13. "Uh, what does this Knob do?"
  • 7.14. About Superclasses and Mix-ins
  • 7.15. NFS - Need for Sorting
  • 7.16. RAM or CPU?
8. Useful Links
9. Summary



1. Introduction

Are you reading this to learn how to script? Then this is NOT for you. If you want to understand this e-book fully, you need basic scripting knowledge. You can read this, of course, but you'll end up wasting your time by not understanding even half of it.
Instead, this e-book will teach you how to become a better scripter. There are far too many scripters who know just a few basics and in the best case they can make a CMS. I will teach you how to handle data, how to make windows look nice and handle them efficiently, how to avoid lag, how to hunt down bugs and how to not be an idiot when scripting. At the end of each chapter there is a little summary, also teaching you how to choose between RAM and CPU specific for that chapter.
Note that I will explain you several things, but these are only the basics. You can't become a better scripter just by reading this e-book, it will only give you a head start in becoming a better scripter. You simply can't become a better scripter without practical experience.


2. Compatibility

This chapter will show you how to make your scripts work with scripts of other scripters more conveniently. If you don't make your scripts compatible, most won't be used. If a user has three cool scripts from three other scripters that work together just fine and yours just won't fit in, he will kick yours most likely and keep using the other three. Another reason for compatibility is to save your time and effort. If your script doesn't work with another one, you will need time to merge it with the other ones for that user.
If your script can be configured and/or has options, make a working precondition and turn off all critical options that need to be first set up correctly by users. It's always a good idea to make your script work Plug 'n' Play as most people don't bother reading instructions.


3. Data Processing and Storage

In this chapter you will learn how to handle data and data processing. In other words, this chapter IS RAM or CPU. You will learn how you can decrease the number of coded lines.


4. Windows

No, it's not the operating system. This chapter will teach you how to handle windows, since they are actually consisting out of several sprites and sprites are the ones that can cause the most lag, especially if they are large.


5. Lag-weg

This chapter will teach you about the worst archenemy of every programmer and scripter: Lag. Lag-weg literally means Lag-away as weg means away in German.


6. Wannabe-Cool Scripting

You are a scripter/programmer, but before all, you are a human being like everybody else. There just are people in the world who seem to believe they would be better than other for either no real or some really idiotic reason. You won't come over as cool if you're being an idiot and rude to people. In this chapter we will work on your relations to the world around you, since it doesn't evolve around you: You evolve around it.


7. Hints and Tricks

This chapter will show you some interesting ideas how to make your scripts work faster, be more compatible, be shorter and on top of that have a cool and professional looking code. Most probably you will enjoy this chapter most as it teaches you actually something to script and doesn't teach you the theory behind all of it too much. This chapter also includes a lot of practical experience.


8. Useful Links

Since this e-book explains just a few basics, here are several links for those who are eager to learn more.

Ruby
http://en.wikipedia.org/wiki/Ruby_(programming_language)
Stack
http://en.wikipedia.org/wiki/Stack_(data_structure)
Recursion
http://en.wikipedia.org/wiki/Recursion_(computer_science)
Interpreter
http://en.wikipedia.org/wiki/Interpreter_(computing)
Compiler
http://en.wikipedia.org/wiki/Compiler
Machine Language
http://en.wikipedia.org/wiki/Machine_language
CPU
http://en.wikipedia.org/wiki/Central_processing_unit
http://en.wikipedia.org/wiki/CPU_design
Object-oriented programming
http://en.wikipedia.org/wiki/Object-oriented_programming
RAM
http://en.wikipedia.org/wiki/Random_access_memory
Array
http://en.wikipedia.org/wiki/Array
Hash
http://en.wikipedia.org/wiki/Hash_table
HUD
http://en.wikipedia.org/wiki/HUD_(computer_gaming)
Algorithm complexity
http://en.wikipedia.org/wiki/Complexity
http://en.wikipedia.org/wiki/Computational_complexity_theory
Logarithm
http://en.wikipedia.org/wiki/Logarithm
Boolean Algebra
http://en.wikipedia.org/wiki/Boolean_algebra_(structure)
Call by Value/Call by Reference
http://en.wikipedia.org/wiki/Evaluation_strategy


9. Summary

Don't compare yourself with other scripters. You might lose your motivation by thinking "I will never get as good as him..." On the other hand you could also DO compare yourself with other scripters. You might be the type of person who says "I want to do better. I can do better. I will do better." instead. It's up to you. None of the good and known scripters today was just born with his skills. He has earned them through work and experience. This e-book is a part of my knowledge as a gift to all of you. It's not only what I have learned from scripting in RGSS, it's also what I have learned from programming in general, from what I have been taught in college and from life itself. Every scripter is unique and his experience and skills are incomparable with the experience and skills of any other scripter. One day you will just realize "Hey, I became better than that other guy..."
The RPG Maker XP help file is always a big help when you get into a dilemma asking yourself "Can I do that?" or "Does that class support that?" or... That's why I have included an enhanced English help file with an extra chapter by an unknown author and the Scripts.rxdata with English commented code, improved iteration coding, recoded to avoid the built-in RGSS bug with conditioning and overworked code to shorten the and improve the code. Many of you might not have a legal copy of RPG Maker XP and therefore not the English files. But this does not mean that I encourage illegal copies! I only give support regardless of the fact that your copy is legal or not! If you like the RMXP editor and engine, buy it! Reading through the help file once completely will help you a lot. You will find many useful methods that can give you results, instead of using your own code for that. I also included a copy of the RGSS102E.dll
By reading this e-book I hope right now you got the itches to make something more than just a CMS. And even if it's a CMS, I hope its moving windows that move from behind a window to the side and then back over the other window will look cool, since they don't lag at all.


10. Download

Full e-book download link
e-book PDF ONLY download link
e-book DOC ONLY download link

If you have problems, you can also try the .txt file download:
http://www.megaupload.com/?d=18E7942R
17678
RPG Maker Scripts / BEFORE asking for help...
January 07, 2008, 09:25:53 pm
NOTE THAT THIS WAS ORIGINALLY MADE BY ZERIAB!

If you do decide to post, please be specific. It's impossible to help a person saying: "I get an error, why?"
Answer these questions when you make a new topic or chance are, you will be asked a variant of those questions.

  • 1. What RPG Maker you are using?
  • 2. What exactly is the problem you are encountering?
  • 3. In which environment does the problem occur?




  • 1: Different versions behave different. You can get a solution which doesn't work with your version. This is a pity and a waste of time. Remember this!!!

  • 2: If you just say you have a problem it's hard to solve, because it can be one of a gazillion things.
    If you get an error message. Post exactly what it says.
    If it's an invisible error, like an event not behaving like it should. Post with which event the problem is and follow 3.

  • 3: By this I mean, when does the problem occur?
    Is it when you start the game? Start a new game? Talk to that dog?
    It's pretty important to tell when exactly you get the problem if you get an error message.
    If it's an invisible error (see 2.):
    You must tell when you notice the event behave being different.
    You must also write the event commands of the specific event and any other event where the existence of interaction is evident.
    If you have any custom scripts installed, tell about them too.
    Some of the things I mentioned here you perhaps shouldn't do as the situation in which problems occurs vary a lot. This can also be the most difficult to answer.

  • A general rule: The more specific you are, the better the chance of a proper answer.

    Also if your problem was solved, please change the title of your topic and add before [RESOLVED], like e.g.:

    How to make an item call a common event?

    [RESOLVED]How to make an item call a common event?
17679
I powered you up, now your energy is 1. :=
17680
Welcome! / Re: Hola Peoples
January 07, 2008, 09:12:28 pm
OMG LET'S GET DRUNK