Post by Dicko on Sept 23, 2004 14:41:31 GMT -5
Hello!
Let's get cracking, shall we?
Labels
This is hard to explain, so I'll use an example to help me.
Labels you use to switch from one piece of coding to the next instead of using switches. One difference is that a label doesn't turn anything on it just goes to the piece of coding you tell it to. Right...
EXAMPLE
You enter a choose character command.
Then afterwards you put a confirm choice.
If they press no, how will you tell it to go back to the choose character stage? Using a label.
At the start, put a label, number it 1. Then put the Choose a Character coding. After, put a choice saying
Confirm Character? On the No case, put a Go To Label 1
then on Yes just put a switch in then continue the coding. Done! Hope that was simple.
Cycles
A cycle is just something that repeats itself, over and over. Say you want a sound effect to repeat itself over and over, you use a cycle. First, make an event out of the way and make it a Parallel Process. Then, start a Cycle. 2 CASES should pop up. Cycle and End Cycle.
Whatever in between these will repeat over and over until you Break Cycle. Anyway, just put a random sound effect and a wait for 3 seconds. When you test it, that sound effect should play over and over.
And last but not least... The dreaded...
Enter Password (Or Key Input Process)
To make this simple, I will explain this for RM2K:
First of all, these numbers are VERY important.
Up-4
Down-1
Right-3
Left-2(these may be wrong. Check the Help file)
Enter-5
Cancel-6
These numbers correspond to the key. Make a variable for each then set it to that number next to it. Also, make one called COMMANDS but don't set it to a number.
Then, choose Enter Password and where it says a variable in a drop down, make sure that says COMMANDS, the variable you just made. After that, it gets REALLY tricky. After this, you must insert a fork condition for each key command. On this fork condition, fork it so that COMMANDS equals the key desired.
When this is done, you may put what you want to happen under that, and in the else case put another fork for a different key and so on and so on. This is what is used in CMS's and CBS's, but there are like 100 of these for each key then for what happens after that.
Hope I opened your mind!
Let's get cracking, shall we?
Labels
This is hard to explain, so I'll use an example to help me.
Labels you use to switch from one piece of coding to the next instead of using switches. One difference is that a label doesn't turn anything on it just goes to the piece of coding you tell it to. Right...
EXAMPLE
You enter a choose character command.
Then afterwards you put a confirm choice.
If they press no, how will you tell it to go back to the choose character stage? Using a label.
At the start, put a label, number it 1. Then put the Choose a Character coding. After, put a choice saying
Confirm Character? On the No case, put a Go To Label 1
then on Yes just put a switch in then continue the coding. Done! Hope that was simple.
Cycles
A cycle is just something that repeats itself, over and over. Say you want a sound effect to repeat itself over and over, you use a cycle. First, make an event out of the way and make it a Parallel Process. Then, start a Cycle. 2 CASES should pop up. Cycle and End Cycle.
Whatever in between these will repeat over and over until you Break Cycle. Anyway, just put a random sound effect and a wait for 3 seconds. When you test it, that sound effect should play over and over.
And last but not least... The dreaded...
Enter Password (Or Key Input Process)
To make this simple, I will explain this for RM2K:
First of all, these numbers are VERY important.
Up-4
Down-1
Right-3
Left-2(these may be wrong. Check the Help file)
Enter-5
Cancel-6
These numbers correspond to the key. Make a variable for each then set it to that number next to it. Also, make one called COMMANDS but don't set it to a number.
Then, choose Enter Password and where it says a variable in a drop down, make sure that says COMMANDS, the variable you just made. After that, it gets REALLY tricky. After this, you must insert a fork condition for each key command. On this fork condition, fork it so that COMMANDS equals the key desired.
When this is done, you may put what you want to happen under that, and in the else case put another fork for a different key and so on and so on. This is what is used in CMS's and CBS's, but there are like 100 of these for each key then for what happens after that.
Hope I opened your mind!
