Gw Temp

Menu

Tutorial - 'Teleport System: Translocation' by ATARI

An item about RPGMaker 2000 posted on

Blurb

How to create a teleportation system similar to that in Unreal Tournament

Body

Hi Folks, It's ATARI here again, this time I'm going to talk about how to make a translocation type system in your rpg.


Things you'll need to know how to use

1. Forks Options
2. Labels
3. Switches
4. Variables

Now first off, what is a translocation? Well, if you've ever played Unreal Tortument, you should know, but if you haven't, I'll explain. Basically you fire the transloctater to a place and then you 'call' the translocater at a certain time and you are teleported to the place. How about we do something similar to that in an rpg!

First thing you'll want to do is create an item. Call it translocater. Make it's description and price whatever you want. Now make it a switch item. Make it turn on switch, 'translocation.' Have one use. Hit apply.

Now go into your common event tabs. Make a new common event. Call it translocater. (Use a different name so it doesn't seem like a rip-off of UT in your real game, we'll just call it this in the tutorial) Make the strarting condition switch 'translocation.' Now the first thing you want to put into the common event is a label event. Make it any number. Then you put a message asking if you want to use the translocater. Make a message that says, "Do you want to use the translocater?" Next make a show choice option that has yes or no. In the "yes" case, make another show choice option that has the following choices, "Fire [translocater]" "Use [Translocater]" "Erase [transloctaer] slot" "Cancel." (Translocater is in [ ]'s because this is only their tutorial name.) Nothing goes under the "No" Case.

First thing tis' first. Under the "Fire [translocater]" Event, have a sound effect mimicking the firing of something. Then show a message that says translocater has been fired or something. Then make a message that says "Store in what slot." Now wait a minute. Slot? Well in this tutorial you can store three unique translocated spots at a time. Okay that's covered. Make a label event (differnt from the first one), choose a label number that has not been used. Now make a show choice that has "slot 1" "slot 2" "slot 3" "cancel." (When using the 'which slot' choices, always make the cancel case choose 4) Now under "slot 1", make a fork option. That says if switch 'slot 1' is off, then under neath that, memorize hero position. Use three variables, one called "TransSlot1 X," "TranSlot1 Y" "TranSlot1 ID" It's pretty obvious which variable you would use for what. Then under that, make an change switch event that turns on switch 'slot 1'. Then show a message that says "Your position has been stored." Okay-dokey. Under the cancel case, go back to the very first label. (Go to label event)

Before we go on any father, I'll explain what is with the slot 1 etc switches and forks and such. What you have just done with slot has made it that slot has already been used, and cannot be used, unless it is erased, which can only be done in the erase [translocater] slot option.

Now under that same choice (Slot 1) make a fork option in the else case, that says "If switch 'slot 1'
is on..." make a message below it that says "Slot is already used! Please use another slot. If all slots are used, use erase [translocater] slot to erase one." Okay-dokey. Now make a go to label event. Go to the label you used for this case (not the very first one. That is very important). Do the same things in the slot 2 and 3 events, except you use different switches (ex. Slot 2, TranSlot 3 Y, etc. You don't use anything for cancel) Hit apply. You can now store your translocated spots. Now it's time to be able to use them.

Under the "Use Translocater" choice, make a message that says "Use which slot?" Then make a show choice event that says "Slot 1" "Slot 2" "Slot 3" "Cancel." Now in the first slot, make another fork that says "if switch 'slot 1' is on," then go to memorized hero place, using variables TranSlot 1 X, Y, and ID. Now make another fork that says "if switch 'slot 1' is off," then make a message that says, "there is no position stored here." Then make a go to label event that sends you to the very first label. (The one at the top.) Easy enough? Do the same things for all the other slots(except for cancel) with your other switches and variables, (slot 3, and such) Then don't forget to go back to the very first label under the "cancel" slot.

Now under the "Erase [translocater] slot." event, make a message that says, "What would you like to do?" or something. Make a show choice event that has "Erase [Translocation] Slot," "Cancel" (Set cancel to go to choice 2) Nothing in the "Cancel" choice except going to the very first label. Now go under the "Erase [translocation] slot option. Make a new label, (different from the other two) Make a message that says "Erase which slot?" Make a show choice option giving the three slot salute. (Okay, that was corny, just the basic slot 1, slot 2, slot 3, cancel thing) Under the first choice, make a fork option that says "If slot 1 switch is on...," make a message that says, "do you wish to erase?" Then make a show choice that has "yes" and "no." In the "yes" case, set 'TranSlot1 X' variable to 0, "TranSlot1 Y' to 0, and 'TranSlot1 ID' to 0. Turn off switch 'slot 1.' Under the else case, make a fork that says 'if switch 'slot 1' is off..' then display a message that says "There is nothing to erase here!" Then go to the label you used (not the first or second of course). Under the no case, make a message that says, "Okay!" then go to the very first label. Do the same with the 'erasing' 'not here' and stuff for slots 2 and 3. (Using the variables and switches that fit the slot, of course)

Almost done. One last little thing. Under the very, VERY VERY bottom end case, turn off the translocater switch. That wasn't so hard!

Now we have made our own little translocation type system in our rpg. Don't forget you lose the translocater item when you use it, and have to buy new ones. (Unless you want it to be an unlimitied thing)

Good Luck!!
Remember,
"Even the greatest gamers were n00bs."
ATARI