Editing Creating Techniques
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
Techniques | Techniques can be created by creating a simple [http://en.wikipedia.org/wiki/JSON JSON] text file in the '''Technique Folder''' folder under `resources/db/technique`. This folder contains all of the details of each technique available in Tuxemon. Here you can specify the technique's type(s), power, and [[Technique effects]]. With each new technique, the following data must be specified: | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 10: | Line 10: | ||
|- | |- | ||
| accuracy | | accuracy | ||
| Float parameter between 0 and | | Float parameter between 0 and 100 which decides against a random value if the technique hits or not. | ||
|- | |- | ||
| animation | | animation | ||
| Name of the animation under ` | | Name of the animation under `resources/animations/technique` to use when the move is used. | ||
|- | |- | ||
| conditions | | conditions | ||
| | | A comma-separated list of effects that will go off when this move is used. Multiple effects can be bound to a single technique. | ||
|- | |- | ||
| effects | | effects | ||
| | | A comma-separated list of effects that will go off when this move is used. Multiple effects can be bound to a single technique. | ||
|- | |- | ||
| flip_axes | | flip_axes | ||
| | | The id of the individual technique. | ||
|- | |- | ||
| is_fast | | is_fast | ||
| | | The id of the individual technique. | ||
|- | |- | ||
| potency | | potency | ||
| Float parameter between 0 and | | Float parameter between 0 and 100 which decides against a random value if the technique will give a [[:Category:Condition]]. | ||
|- | |- | ||
| power | | power | ||
Line 35: | Line 35: | ||
| range | | range | ||
| The kind of technique: [[Melee]], [[Ranged]], [[Touch]], [[Special]], [[Reach]] or [[Reliable]]. | | The kind of technique: [[Melee]], [[Ranged]], [[Touch]], [[Special]], [[Reach]] or [[Reliable]]. | ||
|- | |- | ||
| sfx | | sfx | ||
Line 43: | Line 40: | ||
|- | |- | ||
| slug | | slug | ||
| The slug identifier of the technique. It defines the name of the technique | | The slug identifier of the technique. It defines the name of the technique, since inside the PO file there is a translation corresponding at the slug (msgid "sting" - msgstr "Sting") as well as the description (msgid "sting_description" - msgstr "Describing the technique"). | ||
|- | |- | ||
| sort | | sort | ||
Line 55: | Line 52: | ||
|- | |- | ||
| use_failure (optional) | | use_failure (optional) | ||
| | | Text will appear if the technique fails. | ||
|- | |- | ||
| use_success (optional) | | use_success (optional) | ||
| | | Text will appear if the technique hits. | ||
|- | |- | ||
| use_tech | | use_tech | ||
| | | Text will appear when the technique is used in battle. | ||
|} | |} | ||
Here is an example of what a technique file might look like: | Here is an example of what a technique file might look like: | ||
` | `resources/db/technique/sting.json` | ||
json | json |