Gw Temp


Tutorial - 'Forks and Passwords' by ATARI

An item about RPGMaker 2000 posted on


ATARI's guide to forks and passwords in rm2k


Hi folks. I'm going to talk about how to use fork conditions and enter password (set password) commands.

First off all, I'll explain what their basic definition is. Enter Password really just means enter "key code." You enter the key code and they are stored in a variable. A fork condtion means when a certain thing is set/owned or whatever, then something happens. You may be asking why they are in the same tutorial. This is because in many ways they are very similar from each other. Okay moving on.

1) Passwords.
Let's talk about how to use the enter password command. Open up the enter password option. (located in the event commands page 3.) You should then see the following things

1. A "Place Password to Variable"
2. A "wait until key hit" option.
3. An Input passable key options with the following choices, a (1,2,3,4,) a (5), and a (6). The ( ) = grouped together.
4. Beside the (1,2,3,4) a label that says "direction," by the (5), a label that says "Decision," and by the (6) a "Cancel."

Now first of all, this may seem quite confusing to you. What do all the numbers and checks and stuff mean? Well look down for a diagram of what they mean.

-The (1,2,3,4) stand for direction keys, or arrow keys
-The (5) stands for the decision key, or enter key
-The (6) stands for the esc key.
-Wait until Key hit means that nothing happens until you hit a key
-1 stands for Down
-2 stands for Left
-3 stands for Right
-4 stands for Up
(Note: The 1,2,3,4 stand for all the arrow keys, they can each induviguly set for something)

What do they do? Well, when you select the buttons you want to use (say enter) the number beside it (so if you're using enter, the variable you stored you password in would go to 5, when you let go it would go back to 0). You can choose different variables and run different enter password commands at once. So how do you make it that when you hit the button you do something? Thats where the fork condtions come on in!!

2)Fork Conditions
Hokey dokey!! Time to open up the fork conditions option. (on page 3 of the event commands) Look through all the different options that you have. You have switches, variables, money, timers, item etc. Now how exactly do you use them? Well in this tutorial, we will be using the variable option. Click on the radio button beside the variable option. The stuff beside it should light up. Here now you can choose what variable you want to use, the number it is set at, and below above etc., and another variable box. How does it work? For example. Use a new variable, call it "for_forks" have it set at "36," now click on the radio button for the next variable box. Use a new variable, "for_forks2." Choose the same option. Hit ok. Now below your fork option, make it display a message that says, "You have been sucesful in using a fork." Whayay! Hit ok.

Go onto your map. Make two new events. Have them both set at 'push key' have the one display a message that says "Hello there!" Or something, and then below that, change the first variable to 36. Now at the other event, make it says "Hi there!" and set the second variable to 36. Your sucesful message should pop up. Congradulations!! You have sucesfully just used a fork condition. That wasn't so tough was it? Delete the fork option and the events and the message and move on.

3) Forks and Passwords
Now how do passwords and fork options relate? Well since passwords store the value of the key in a variable (as said above), you then use a fork option with the same variable. Make a new enter password command in a new event. Set the event's conditions to parrell process. Don't check the wait until key hit button. Choose the (5) option. Store it in a new variable called "Password1." Hit ok. Go into the fork condition optin, go into the variable option, set it to the number that you used and have it set to same. Hit ok. Then below that fork option, make a new message that says "You have used a password." Hit ok and test out your game. When you press enter, the message should pop up. Congradulations, you have sucesfully used a password and had some extra practice with fork options.

4) Else Case
Now you should have an else case in your event. (If you don't edit your fork option and check the 'add else case' option.) Now in the else case, make it show a random message. Hit ok and test your game. It should auto matically display your random message. Why? Because the else case stands for, "If your fork option doesn't happen, or isn't true." This is the part of the fork option that you want to use for things to happen if your fork option doesn't become true.

Well, that's pretty much all there really is to using fork conditions and enter password commands.

Good Luck
"Even the greatest gamers were n00bs."