[Sub] Orcywoo6's Taming System, Rather complicated, but it works. Options

[orcywoo6]

Orcywoo6's Taming System

Introduction

Ok so I have decided to show everyone my taming system that I have created for my commercial project that is yet to be unveiled. Its a simple but effective system that allows a party member with the skill "Tame Monster" (or whatever you want to call it) to tame a monster and add it to the party...A little bit like catching pokemon.

Terms of use:

If you want to use this event system in your Non-Commercial project then you can go right on ahead and have fun with it as long as credit is given.

You may not however use this system in your Commercial product unless arrangements are made with me, if I find you have used it anyway without permission I will hunt you down.

[Show/Hide] Info

Info:

Difficulty: 7/10 - Quite complicated and time consuming.
Required knowlege of: Variables, Common events, skills, troops, Conditional Branches
Engine made for: RMXP
Other engines: Most likely works with other Rpg makers with some adjustments.
Switches needed: 1 switch
Variables needed: An absolute minimum of 6 with 3 variables added for each tame-able creature.
Common Events: Two main common events for the taming skill.
Materials: None needed other than charsets and battlers for your monsters. (RMXP has these).
Actors: You will need to create an actor for each tame-able monster.
Weapons: You will need to create a weapon for each monster too otherwise they will do 0 damage.

Drawbacks

The only drawback I am aware of is that it will not work if there is more than one tame-able creature in a battle.

The system

Ok then ladies and gentlemen, make yourself a nice hot drink and get comfortable, this may take a while...
Read through slowly and carefully to prevent errors

[Show/Hide] Part 1

Part 1 - Set up

1. The first thing you are going to need to do is create the skill that will allow you to tame monsters. So go ahead and configure it however you want. Its important that it does not do any damage because it could potentially mess up the system if it kills the monster.
It is also important that the scope is set to "one enemy"


2. You will now need to create a common event for this skill, just call it something like "taming" and leave it blank for now. Leave the trigger setting as "none". Create another common event called "No taming" and set its trigger to parallel and assign it a junk switch, this switch will need to be turned on at the beginning of your game! Now go back to the taming skill you created and set it to activate the "taming" common event you just created.

3. Go back to the skill menu and create another skill, this skill will cause the death of the enemy that you successfully tame so that it is not still fighting you after it joins your party otherwise this would happen:

[Show/Hide] Problem

See the problem? The monster added to the party seemingly came out of nowhere and the enemy is still there. Meaning there is now an extra slime.
That is why this skill is needed.

When configuring the skill you can make it one of two ways. You can either make it do 9999 damage or make it inflict the knockout state. Either way is fine but the knockout state one is less reliable because it misses and messes things up.
You also need to set the scope to "one enemy" and the Occasion to "never" (So the skill is only used after a successful tame.)
Make sure that the character you want to have the tame skill also knows this skill!

4. The final part of the set up is to create two actors for each monster that you want to be able to tame (One for male and one for female)
It is best to lock all of their equipment, its a bit odd for a slime to be able to equip mythril armor right?
They will also require a weapon otherwise they will do no damage. Just create something generic such as "Claws" and set it to be fixed so it cannot be unequipped.
For the sake of this tutorial it will be based on taming a slime.
For example:


Now onto step 2...

[Show/Hide] Part 2

Step 2 - The Bulk

1. Now that you have the base things set up its time to move onto the bulk of the system, the common event. Go back to the "taming" common event you created earlier we will now begin making that.

First of all you will need to create 6 variables.
Partysize - Checks the size of your party to make sure you have enough room to tame a creature.
creaturegender - Determines the gender of the tamed creature.
tamechance - Determines the chance of a successful tame.
slime - Checks what creature you are battling against. (To make sure that the correct one is tamed)
slimef got - Checks if you already have a female slime.
slimem got - Checks if you already have a male slime.

This is enough variables for one tameable creature (Male and Female) and to add more you simply need to add 1 more of the last 3 variables for each creature.

2. Now that you have created the required variables you can begin adding to the system.
In your taming common event add some generic text about the taming attempt e.g: "You attempt to tame the creature..."

You then need to set the variable Partysize to the size of the party by using the set variable command, the party size option is under "Other"

When you have done this, create a conditional branch if partysize < 4
For the "else" branch (this is if the party is full) just put some generic text. eg: "The party is full!"

For the party size being less than 4 branch we can continue the system.

Create another conditional branch, this time checking if the variable Slime is equal to 1.
Leave the "else" branch blank and continue the system in the equal to 1 branch.

Now you need to set the variable creaturegender to a random number between 0 and 11 using the set variable command and the random number option.

After this create another conditional branch if creaturegender <=5
Leave the "else" branch blank for now and continue the system on the <=5 branch.

Now add the text " The Slime you are trying to tame is female." To notify the player what gender the creature is.

Below this add another conditional branch that checks if the variable slimefgot = 0
On the "else" branch put the text "You already have a female slime!"

On the slimefgot = 0 branch put a set variable command. This time setting the variable tamechance to a random number between 0 and 10.

After this put another conditional branch if tamechance <= 4
On the "else" branch you need to put the result of an unsuccessful tame attempt, just some text saying the attempt failed is fine.

On the tamechance <= 4 branch you need to put a message saying the result.

[Show/Hide] Example

"The slime seems to be warming up to you"

Wait 20 frames.

"...The slime joins your side in the battle, the attempt was a success"

"Would you like to name the slime you tamed?"

Choices "yes", "no"
[When Yes]
Name input for Slime F

[When No]
(Leave blank)

Below this use the "force action" command to force the actor to use the knockout skill that you created, on the "last target"
Then put the "add party member Slime F" command to add the tamed creature to the party.
Below this set the variable slimefgot to 1.

That is the female slime completed, to enable taming of a male slime just copy and paste everything you have done, starting from "the slime you are trying to tame is female" and ending at "setting the variable slimefgot to 1" and just change the variables and text to the male versions.

3. The last few things you need to do are:

Set the common event "No taming" to set the variable Slime to 0 (after every tame-able creature you add, add its variable to this common event)

Go to the troop menu and set the tame-able creature to set its respective variable, in this case Slime to 1 on the first turn.

You will also need to do this for each extra tame-able creature with their individual variables.

Support

Post any questions or problems here and I will try to help you as soon as possible.
Don't hesitate to post if you can't understand the way I have explained it. (I'm not good at explaining )
I will not post a demo as it will be better for you to implement the system yourself, it will give you more eventing knowlege in the long run!

[RzrBladeMontage]

I just finished putting your entire event system together, and I do have to admit, it's pretty nifty! However, there are some problems with it.

1.) If the player who uses the taming skill "Misses" the common event still gets activated (I don't think there is a way around this, but I'm just telling you)

2.) If the slime you're trying to tame is a Male, and you fail to tame, and then you try and tame the same slime again, there is a chance it could now be a female, and vis-versa.

3.) The skill that kills the enemy slime while the ally slime is being added sometimes misses, causing the enemy slime to remain on the other side, as well as you obtaining the allied slime.

[Show/Hide] FIXED

What I did was create a state called "Death" and an element called "Death." I made the Taming Skill use the Death Element, and the skill that kills the enemy use the Death Elemental and the Death State. Change the slimes defenses to "A" for both the Element and the State and you will always 1Hit-KO it when using the final skill. The original Taming Skill also seems to hit a little more now as well."

4.) If you capture a female slime and try to capture another, it may also be a "female" however, if you keep trying you can eventually get "male" and be able to add another slime to your party.

5.) If you try and name a slime after you capture it, the event will force you out of battle and you won't get the slime.

But like I said, it is a very good system, especially seeing how it's using events. Great job! I'll add this to the Event Submission List!

[orcywoo6]

I just finished putting your entire event system together, and I do have to admit, it's pretty nifty! However, there are some problems with it.

1.) If the player who uses the taming skill "Misses" the common event still gets activated (I don't think there is a way around this, but I'm just telling you)

2.) If the slime you're trying to tame is a Male, and you fail to tame, and then you try and tame the same slime again, there is a chance it could now be a female, and vis-versa.

3.) The skill that kills the enemy slime while the ally slime is being added sometimes misses, causing the enemy slime to remain on the other side, as well as you obtaining the allied slime.

[Show/Hide] FIXED

What I did was create a state called "Death" and an element called "Death." I made the Taming Skill use the Death Element, and the skill that kills the enemy use the Death Elemental and the Death State. Change the slimes defenses to "A" for both the Element and the State and you will always 1Hit-KO it when using the final skill. The original Taming Skill also seems to hit a little more now as well."

4.) If you capture a female slime and try to capture another, it may also be a "female" however, if you keep trying you can eventually get "male" and be able to add another slime to your party.

5.) If you try and name a slime after you capture it, the event will force you out of battle and you won't get the slime.

But like I said, it is a very good system, especially seeing how it's using events. Great job! I'll add this to the Event Submission List!

Thank you very much, I spent ages trying to get it to work lol

About the problems:

1) Yeah, sadly this is a problem that I couldn't seem to fix...

2,4) I don't think theres a way around the gender problem unless you get rid of it altogether and dont have genders...The only reason they were there is for some variation and a possible breeding system

3) Ah awesome thanks, I will add that to the main post when I am not being lazy

5) Hmm...Never noticed that problem...Maybe there is a way around it. I will look into it.

[Knot]

Hey, I love the system, it's giving me some very interesting ideas for different battle mechanics :x. I also have a few ideas for some of the problems, but they kind of complicate the system a bit xD.

For the first one with the "miss" thing, you can have the skill put a state that cannot be resisted on the enemy you are trying to tame. Then, the common event first checks if any enemy has this state and if an enemy does then it continues from there. So you'd have a conditional branch that checks if enemy 1 is Dummy State inflicted etc...until you reach the maximum number of enemy's any one troop has. You would then have to turn off this state on the enemy at the end of the event, but the good thing is that if the attack misses then this state won't be inflicted and the common event won't run.

As for the gender, it's more work, but you could put these variables in the troop section instead. For example, say you have a troop with 4 enemies, at the beggining of the battle you would have 4 variables called "enemy1", "enemy2", "enemy3", "enemy4". you get the first to roll, like you said, a number between 1~11 etc...once it's decided if it is male or female you put a state on this enemy, either Male or Female that lasts until the battle ends. Going back to the Dummy state mentioned in the first idea, since you know which enemy you have used the skill on (it's the one inflicted with the Dummy State) you can then check whether it is male or female and it won't be able to change genders during the fight.

Anyway, I hope those ideas help, all in all it's a really cool system.

[orcywoo6]

Hey, I love the system, it's giving me some very interesting ideas for different battle mechanics :x. I also have a few ideas for some of the problems, but they kind of complicate the system a bit xD.

For the first one with the "miss" thing, you can have the skill put a state that cannot be resisted on the enemy you are trying to tame. Then, the common event first checks if any enemy has this state and if an enemy does then it continues from there. So you'd have a conditional branch that checks if enemy 1 is Dummy State inflicted etc...until you reach the maximum number of enemy's any one troop has. You would then have to turn off this state on the enemy at the end of the event, but the good thing is that if the attack misses then this state won't be inflicted and the common event won't run.

As for the gender, it's more work, but you could put these variables in the troop section instead. For example, say you have a troop with 4 enemies, at the beggining of the battle you would have 4 variables called "enemy1", "enemy2", "enemy3", "enemy4". you get the first to roll, like you said, a number between 1~11 etc...once it's decided if it is male or female you put a state on this enemy, either Male or Female that lasts until the battle ends. Going back to the Dummy state mentioned in the first idea, since you know which enemy you have used the skill on (it's the one inflicted with the Dummy State) you can then check whether it is male or female and it won't be able to change genders during the fight.

Anyway, I hope those ideas help, all in all it's a really cool system.

Thank you very much, it really does add an extra sense of collection to the game. Hopefully I can create a breeding system like the day care on pokemon that can work alongside this system. Fixing up the gender issue is one of the priorities. Thanks again

Thanks for the great ideas I shall try them and see if they can solve those pesky problems I have been using events for years so its almost like second nature to me so don't worry about complication. I will find a way to explain it to others XD

[Reshiram//Exe]

I wonder if this is possible with VX. It sounds great.

[Mototuku]

5.) If you try and name a slime after you capture it, the event will force you out of battle and you won't get the slime.

I am new and I am making a game on RMXP. I have just tried this system and I noticed this problem too. I worked on it and changed somethings after the text that says you are successful.

[Show/Hide] Changed System

*I'm Turkish so texts are Turkish. And I did not add genders, I passed that part.