Creating Techniques - Revision history

Sanglorian: Explaining "sort" in more detail

2025-10-25T12:29:33Z

Explaining "sort" in more detail

← Older revision		Revision as of 12:29, 25 October 2025
Line 9:		Line 9:
	=== Basic Info ===		=== Basic Info ===
	* '''slug''': A unique name used in code (e.g. <code>"sting"</code>).		* '''slug''': A unique name used in code (e.g. <code>"sting"</code>).
	* '''sort''': ~~What kind of move~~ it ~~is (e.g~~. <code>"damage"</code> or <code>"meta"</code>).		* '''sort''': In which stage it occurs. All regular techniques should be <code>"damage"</code>, even if they are non-damaging. (<code>"meta"</code> is available for things like fleeing combat, switching to another monster, and so on).
	* '''category''': A label for how the move behaves (e.g. <code>"powerful"</code>, <code>"basic"</code>, <code>"exotic"</code>).		* '''category''': A label for how the move behaves (e.g. <code>"powerful"</code>, <code>"basic"</code>, <code>"exotic"</code>).

2025-10-25T10:32:42Z

Range: More details on ranges

← Older revision		Revision as of 10:32, 25 October 2025
Line 79:		Line 79:
	=== Range ===		=== Range ===
	* '''range''': How far the move reaches. Options include:		* '''range''': How far the move reaches. Options include:
	** <code>"melee"</code>: Close-range		** <code>"melee"</code>: Close-range (compare user's Melee to target's Armor)
	** <code>"ranged"</code>: Long-range		** <code>"ranged"</code>: Long-range (compare user's Ranged to target's Dodge)
	** <code>"touch"</code>: Requires ~~physical~~ contact		** <code>"touch"</code>: Requires mere contact (compare user's Melee to target's Dodge)
	** <code>"reach"</code>: Slightly extended range		** <code>"reach"</code>: Slightly extended range (compare user's Ranged to target's Armor)
	** <code>"special"</code>: ~~Unique targeting~~		** <code>"special"</code>: Does not involve damage
	** <code>"reliable"</code>: ~~Always hits~~		** <code>"reliable"</code>: Does a uniform amount of damage regardless of stats.

	=== ID & Accuracy ===		=== ID & Accuracy ===

2025-08-01T12:00:12Z

2023-12-26T17:53:33Z

← Older revision		Revision as of 17:53, 26 December 2023
Line 66:		Line 66:
	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`		`mods/tuxemon/db/technique/sting.json`

	json		json

2023-12-26T17:47:33Z

← Older revision		Revision as of 17:47, 26 December 2023
Line 13:		Line 13:
	\|-		\|-
	\| animation		\| animation
	\| Name of the animation under `~~resources~~/animations/technique` to use when the move is used.		\| Name of the animation under `mods/tuxemon/animations/technique` to use when the move is used.
	\|-		\|-
	\| conditions		\| conditions

2023-12-26T17:46:46Z

← Older revision		Revision as of 17:46, 26 December 2023
Line 1:		Line 1:
	Techniques in Tuxemon can be created by adding a JSON file to the <code>~~resources~~/db/technique</code> directory. With each new technique, the following data must be specified:		Techniques in Tuxemon can be created by adding a JSON file to the <code>mods/tuxemon/db/technique</code> directory. With each new technique, the following data must be specified:

	{\| class="wikitable"		{\| class="wikitable"

2023-12-26T14:34:06Z

← Older revision		Revision as of 14:34, 26 December 2023
Line 1:		Line 1:
	Techniques in Tuxemon can be created by adding a JSON file to the <code>resources/db/~~item~~</code> directory. With each new technique, the following data must be specified:		Techniques in Tuxemon can be created by adding a JSON file to the <code>resources/db/technique</code> directory. With each new technique, the following data must be specified:

	{\| class="wikitable"		{\| class="wikitable"

2023-12-26T14:33:44Z

← Older revision		Revision as of 14:33, 26 December 2023
Line 1:		Line 1:
	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:		Techniques in Tuxemon can be created by adding a JSON file to the <code>resources/db/item</code> directory. With each new technique, the following data must be specified:

	{\| class="wikitable"		{\| class="wikitable"

2023-12-26T09:49:07Z

← Older revision		Revision as of 09:49, 26 December 2023
Line 43:		Line 43:
	\|-		\|-
	\| slug		\| slug
	\| 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").		\| The slug identifier of the technique. It defines the name of the technique and there is a translation in the PO file (msgid "sting" - msgstr "Sting") as well as the description (msgid "sting_description" - msgstr "Describing the technique").
	\|-		\|-
	\| sort		\| sort
Line 55:		Line 55:
	\|-		\|-
	\| use_failure (optional)		\| use_failure (optional)
	\| ~~Text~~ will appear if the technique fails.		\| Corresponding msgid (translation PO file) will appear if the technique fails.
	\|-		\|-
	\| use_success (optional)		\| use_success (optional)
	\| ~~Text~~ will appear if the technique hits.		\| Corresponding msgid (translation PO file) will appear if the technique hits.
	\|-		\|-
	\| use_tech		\| use_tech
	\| ~~Text~~ will appear when the technique is used in battle.		\| Corresponding msgid (translation PO file) will appear when the technique is used in battle.
	\|}		\|}

2023-12-26T09:46:20Z

← Older revision		Revision as of 09:46, 26 December 2023
Line 10:		Line 10:
	\|-		\|-
	\| accuracy		\| accuracy
	\| Float parameter between 0 and ~~100~~ which decides against a random value if the technique hits or not.		\| Float parameter between 0 and 1 which decides against a random value if the technique hits or not.
	\|-		\|-
	\| animation		\| animation
Line 28:		Line 28:
	\|-		\|-
	\| potency		\| potency
	\| Float parameter between 0 and ~~100~~ which decides against a random value if the technique will give a [[:Category:Condition]].		\| Float parameter between 0 and 1 which decides against a random value if the technique will give a [[:Category:Condition]].
	\|-		\|-
	\| power		\| power