Techniques - Revision history

Sanglorian at 02:10, 15 November 2025

2025-11-15T02:10:50Z

← Older revision		Revision as of 02:10, 15 November 2025
Line 3:		Line 3:
	Techniques are discrete attacks, blocks, tricks and other manoeuvres that tuxemon perform in combat.		Techniques are discrete attacks, blocks, tricks and other manoeuvres that tuxemon perform in combat.

	Each tuxemon knows between one and four techniques at any one time, but which techniques they know can change. A monster can also re-learn techniques from earlier levels, by visiting the [[Dojo of the ~~Five~~ Elements]].		Each tuxemon knows between one and four techniques at any one time, but which techniques they know can change. A monster can also re-learn techniques from earlier levels, by visiting the [[Dojo of the Elements]].

	=== Acquisition ===		=== Acquisition ===

Sanglorian: Explaining monsters can re-learn techniques

2025-10-29T07:47:46Z

Explaining monsters can re-learn techniques

← Older revision		Revision as of 07:47, 29 October 2025
Line 3:		Line 3:
	Techniques are discrete attacks, blocks, tricks and other manoeuvres that tuxemon perform in combat.		Techniques are discrete attacks, blocks, tricks and other manoeuvres that tuxemon perform in combat.

	Each tuxemon knows between one and four techniques at any one time, but which techniques they know can change.		Each tuxemon knows between one and four techniques at any one time, but which techniques they know can change. A monster can also re-learn techniques from earlier levels, by visiting the [[Dojo of the Five Elements]].

	=== Acquisition ===		=== Acquisition ===

Sanglorian: /* Effects */ Clarifying what happens to two-element monsters

2025-10-29T07:41:36Z

Effects: Clarifying what happens to two-element monsters

← Older revision		Revision as of 07:41, 29 October 2025
Line 75:		Line 75:
	* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''		* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''		* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.		* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood. If a monster has two elements, both are replaced by the new element.
	* <code>transfer x</code> If the user has the specified condition (x), the target gets the condition instead. [[Suck Poison]] transfers [[Poisoned]], and is the only technique with this effect so far.		* <code>transfer x</code> If the user has the specified condition (x), the target gets the condition instead. [[Suck Poison]] transfers [[Poisoned]], and is the only technique with this effect so far.

Sanglorian: /* Effects */ Updating to indicate when a technique is unique

2025-10-24T12:57:58Z

Effects: Updating to indicate when a technique is unique

Sanglorian: /* Effects */ Explaining transfer better; technique example for each

2025-10-24T08:55:07Z

Effects: Explaining transfer better; technique example for each

Sanglorian: /* Effects */ Couple more

2025-10-24T08:45:51Z

Effects: Couple more

← Older revision		Revision as of 08:45, 24 October 2025
Line 55:		Line 55:
	* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle.		* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle.
	* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.		* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.
	* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[~~Fireball~~]] on their return. [[Burrow Blast]] does the same but with [[Strike]].		* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fire Ball]] on their return. [[Burrow Blast]] does the same but with [[Strike]]. <code>appear</code> is the matching effect that ends the disappear effect.
			* <code>empty</code> The technique does nothing, by design. [[Wiggle]] is a good example.
	* <code>foresight x</code> The technique is reused x turns later, with Power x.		* <code>foresight x</code> The technique is reused x turns later, with Power x.
	* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).		* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).
Line 75:		Line 76:
	* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.		* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.
	* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.		* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.
			* <code>transfer</code> If the user is [[Poisoned]], the target becomes Poisoned instead. [[Suck Poison]] works this way.

Sanglorian: /* Effects */ Adding a couple more

2025-10-24T08:15:29Z

Effects: Adding a couple more

← Older revision		Revision as of 08:15, 24 October 2025
Line 53:		Line 53:
	=== Effects ===		=== Effects ===

	* <code>~~scope~~</code> ~~The opponent's stats are revealed~~.		* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle.
	* <code>~~photogenesis~~ x~~, y, z~~</code> ~~Heals~~ the ~~user based on~~ time ~~of day. The entry specifies the start hour~~ (x), ~~peak hour (y, when healing is greatest) and end hour (z~~). ~~Healing is skipped if the user is indoors, the~~ technique ~~misses~~, or the user ~~is at full health~~.		* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.
	* <code>~~multiattack~~ x</code> ~~Make~~ a ~~number of~~ attacks ~~equal~~ to x.		* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fireball]] on their return. [[Burrow Blast]] does the same but with [[Strike]].
	* <code>~~splash~~ x</code> ~~If the attack misses~~, ~~do damage divided by~~ x ~~(usually 2)~~.		* <code>foresight x</code> The technique is reused x turns later, with Power x.
	* <code>~~switch~~ x, y</code> ~~Changes~~ x~~'s element to~~ y, ~~which can be~~ a ~~specific element~~ or ~~random~~. ~~X can be~~ the ~~player~~'s ~~monster, the opponent~~'s ~~monster, both, etc~~. For example, [[~~Ants~~]] ~~changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood~~.		* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).
	* <code>~~reverse x~~</code> ~~Change x's element back to its original element after it has been switched~~. X can be the ~~player's monster,~~ the ~~opponent's monster~~, ~~both~~, ~~etc~~.		* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.
			* <code>life_share</code> Shares the current HP amounts of the two monsters. The direction of the sharing is determined by the `direction` attribute, which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by the `method` attribute, which can be either "weighted", "geometric" or "simple".
	* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP).		* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP).
	* <code>~~life_share~~</code> ~~Shares~~ the ~~current~~ HP ~~amounts of the two monsters~~. ~~The direction of the sharing is determined by the `direction` attribute~~, ~~which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by~~ the ~~`method` attribute, which can be either "weighted", "geometric" or "simple"~~.		* <code>money</code> On a hit, gain dollars equal to the HP damage done. On a miss, user loses HP equal to the damage that would have been done.
	* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target.		* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target.
			* <code>multiattack x</code> Make a number of attacks equal to x.
			* <code>photogenesis x, y, z</code> Heals the user based on time of day. The entry specifies the start hour (x), peak hour (y, when healing is greatest) and end hour (z). Healing is skipped if the user is indoors, the technique misses, or the user is at full health.
			* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP).
	* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP).		* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP).
	* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP).
	* <code>step_damage x, y, z</code>Do damage based on the number of [[Steps]] that the user has taken.
	* <code>step_healing x, y, z</code>Do damage based on the number of [[Steps]] that the user has taken.
	* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.
	* <code>heal x, y</code>Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).
	* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all".		* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all".
	* <code>~~cooldown~~ x</code> ~~Increases or decreases~~ the ~~recharge time for x~~'s ~~techniques (with x being own~~ monster, ~~enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces~~ the ~~user~~'s ~~recharge time for non-damaging techniques.~~		* <code>reverse x</code> Change x's element back to its original element after it has been switched. X can be the player's monster, the opponent's monster, both, etc.
	* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), ~~and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fireball]] on their return. [[Burrow Blast]] does the same but with [[Strike]].~~
	* <code>foresight x</code> The technique is reused x turns later, ~~with Power x~~.
	* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x.		* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x.
			* <code>scope</code> The opponent's stats are revealed.
			* <code>splash x</code> If the attack misses, do damage divided by x (usually 2).
			* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.
			* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.
			* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.


	''In progress''		''In progress''

Sanglorian: en_US spelling

2025-09-28T08:15:01Z

en_US spelling

← Older revision		Revision as of 08:15, 28 September 2025
Line 37:		Line 37:

	* '''Special:''' Any technique that does not involve an attack		* '''Special:''' Any technique that does not involve an attack
	* '''Melee:''' Multiply damage by User Melee and divide it by Target ~~Armour~~		* '''Melee:''' Multiply damage by User Melee and divide it by Target Armor
	* '''Ranged:''' Multiply damage by User Ranged and divide it by Target Dodge		* '''Ranged:''' Multiply damage by User Ranged and divide it by Target Dodge
	* '''Touch:''' Multiply damage by User Melee and divide it by Target Dodge		* '''Touch:''' Multiply damage by User Melee and divide it by Target Dodge
	* '''Reach:''' Multiply damage by User Ranged and divide it by Target ~~Armour~~		* '''Reach:''' Multiply damage by User Ranged and divide it by Target Armor
	* '''Reliable:''' Multiply damage by 1		* '''Reliable:''' Multiply damage by 1

Line 49:		Line 49:
	A damaging technique does damage based on the below formula:		A damaging technique does damage based on the below formula:

	(User Melee or Ranged/Target ~~Armour~~ or Dodge OR 1 if Reliable) * (7 + User Level) * Technique Power * Weakness or Resistance Multiplier		(User Melee or Ranged/Target Armor or Dodge OR 1 if Reliable) * (7 + User Level) * Technique Power * Weakness or Resistance Multiplier

	=== Effects ===		=== Effects ===

Sanglorian: /* Effects */

2025-09-13T22:13:45Z

Effects

← Older revision		Revision as of 22:13, 13 September 2025
Line 72:		Line 72:
	* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fireball]] on their return. [[Burrow Blast]] does the same but with [[Strike]].		* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fireball]] on their return. [[Burrow Blast]] does the same but with [[Strike]].
	* <code>foresight x</code> The technique is reused x turns later, with Power x.		* <code>foresight x</code> The technique is reused x turns later, with Power x.
			* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x.

	''In progress''		''In progress''

Sanglorian at 12:11, 11 September 2025

2025-09-11T12:11:16Z

← Older revision		Revision as of 12:11, 11 September 2025
Line 68:		Line 68:
	* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.		* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.
	* <code>heal x, y</code>Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).		* <code>heal x, y</code>Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).
			* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all".
			* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.
			* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fireball]] on their return. [[Burrow Blast]] does the same but with [[Strike]].
			* <code>foresight x</code> The technique is reused x turns later, with Power x.

	''In progress''		''In progress''

← Older revision		Revision as of 12:57, 24 October 2025
Line 54:		Line 54:

	* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle. [[Firestorm]], for example.		* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle. [[Firestorm]], for example.
	* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.		* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques. Currently [[Pouch]] is unique in using this effect.
	* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fire Ball]] on their return. [[Burrow Blast]] does the same but with [[Strike]]. <code>appear</code> is the matching effect that ends the disappear effect.		* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fire Ball]] on their return. [[Burrow Blast]] does the same but with [[Strike]]. <code>appear</code> is the matching effect that ends the disappear effect.
	* <code>empty</code> The technique does nothing, by design. [[Wiggle]] is ~~a good~~ example.		* <code>empty</code> The technique does nothing, by design. [[Wiggle]] is the only example so far.
	* <code>foresight x</code> The technique is reused x turns later, with Power x. ''(No such examples yet.)''		* <code>foresight x</code> The technique is reused x turns later, with Power x. ''(No such examples yet.)''
	* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP). ''(No such examples yet, except among items.)''		* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP). ''(No such examples yet, except among items.)''
Line 62:		Line 62:
	* <code>life_share</code> Shares the current HP amounts of the two monsters. The direction of the sharing is determined by the `direction` attribute, which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by the `method` attribute, which can be either "weighted", "geometric" or "simple". ''(No such examples yet.)''		* <code>life_share</code> Shares the current HP amounts of the two monsters. The direction of the sharing is determined by the `direction` attribute, which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by the `method` attribute, which can be either "weighted", "geometric" or "simple". ''(No such examples yet.)''
	* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP). ''(No such examples yet.)''		* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP). ''(No such examples yet.)''
	* <code>money</code> On a hit, gain dollars equal to the HP damage done. On a miss, user loses HP equal to the damage that would have been done. [[Gold Digger]] ~~uses~~ this effect.		* <code>money</code> On a hit, gain dollars equal to the HP damage done. On a miss, user loses HP equal to the damage that would have been done. [[Gold Digger]] is currently the only technique to use this effect.
	* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target. ''(No such examples yet.)''		* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target. ''(No such examples yet.)''
	* <code>multiattack x</code> Make a number of attacks equal to x. For example, [[Leaf Barrage]] attempts two hits.		* <code>multiattack x</code> Make a number of attacks equal to x. For example, [[Leaf Barrage]] attempts two hits.
	* <code>photogenesis x, y, z</code> Heals the user based on time of day. The entry specifies the start hour (x), peak hour (y, when healing is greatest) and end hour (z). Healing is skipped if the user is indoors, the technique misses, or the user is at full health. [[Solar Synthesis]] heals the user via <code>photogenesis 6,12,18</code>.		* <code>photogenesis x, y, z</code> Heals the user based on time of day. The entry specifies the start hour (x), peak hour (y, when healing is greatest) and end hour (z). Healing is skipped if the user is indoors, the technique misses, or the user is at full health. [[Solar Synthesis]] heals the user via <code>photogenesis 6,12,18</code>.
	* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP). [[Panjandrum]] deals 25% of the target’s max HP.		* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP). [[Panjandrum]] deals 25% of the target’s max HP. [[Tooth for Tooth]] does proportional damage to both user and target.
	* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP). [[Blossom]] heals its user for 20% of max HP after damaging the foe.		* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP). [[Blossom]] heals its user for 20% of max HP after damaging the foe.
	* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all". [[Feint]] removes positive conditions from the enemy.		* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all". [[Feint]] removes positive conditions from the enemy.
	* <code>reverse x</code> Change x's element back to its original element after it has been switched. X can be the player's monster, the opponent's monster, both, etc. [[Neutralize]] reverses type changes for every creature on the field, if they have been <code>switch</code>ed.		* <code>reverse x</code> Change x's element back to its original element after it has been switched. X can be the player's monster, the opponent's monster, both, etc. [[Neutralize]] reverses type changes for every creature on the field, if they have been <code>switch</code>ed, and is currently the only technique to use the reverse effect.
	* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x. [[Undertaker]] spends all of the user’s current HP to do that much damage.		* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x. [[Undertaker]] spends all of the user’s current HP to do that much damage; currently the only technique to use this effect.
	* <code>scope</code> The opponent's stats are revealed. [[Scope]] is the archetypal example.		* <code>scope</code> The opponent's stats are revealed. [[Scope]] is the archetypal (and to date only) example.
	* <code>splash x</code> If the attack misses, do damage divided by x (always 2 in the conditions implemented so far). [[Surf]] is such an example.		* <code>splash x</code> If the attack misses, do damage divided by x (always 2 in the conditions implemented so far). [[Surf]] is such an example.
	* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''		* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''		* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.		* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.
	* <code>transfer x</code> If the user has the specified condition (x), the target gets the condition instead. [[Suck Poison]] transfers [[Poisoned]].		* <code>transfer x</code> If the user has the specified condition (x), the target gets the condition instead. [[Suck Poison]] transfers [[Poisoned]], and is the only technique with this effect so far.

	(Damage is technically an effect too, but is omitted from this list since it is discussed above.)		(Damage is technically an effect too, but is omitted from this list since it is discussed above.)

← Older revision		Revision as of 08:55, 24 October 2025
Line 53:		Line 53:
	=== Effects ===		=== Effects ===

	* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle.		* <code>areas</code> Do damage to all enemy creatures currently in the battle. In other words, this effect makes no difference in a one-on-one battle but damages both enemies in a two-on-two battle. [[Firestorm]], for example.
	* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.		* <code>cooldown x</code> Increases or decreases the recharge time for x's techniques (with x being own monster, enemy monster or both). Can indicate which types of technique are not affected, so for example [[Pouch]] reduces the user's recharge time for non-damaging techniques.
	* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fire Ball]] on their return. [[Burrow Blast]] does the same but with [[Strike]]. <code>appear</code> is the matching effect that ends the disappear effect.		* <code>disappear x</code> The user disappears for a turn (not able to be targeted by attacks), and then returns to use technique "x". For example, [[Oven]] causes the user to disappear for a turn and then use [[Fire Ball]] on their return. [[Burrow Blast]] does the same but with [[Strike]]. <code>appear</code> is the matching effect that ends the disappear effect.
	* <code>empty</code> The technique does nothing, by design. [[Wiggle]] is a good example.		* <code>empty</code> The technique does nothing, by design. [[Wiggle]] is a good example.
	* <code>foresight x</code> The technique is reused x turns later, with Power x.		* <code>foresight x</code> The technique is reused x turns later, with Power x. ''(No such examples yet.)''
	* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP).		* <code>heal x, y</code> Heal x by y damage, if y is a number (say, 20 or 50). If y is a fraction, heal x by (y * target's maximum HP). ''(No such examples yet, except among items.)''
	* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.		* <code>healing</code> Heal the user an amount equal to (the technique's "healing power" value * (7 + user's level)). For example, [[Gourmet]] has healing power 3.
	* <code>life_share</code> Shares the current HP amounts of the two monsters. The direction of the sharing is determined by the `direction` attribute, which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by the `method` attribute, which can be either "weighted", "geometric" or "simple".		* <code>life_share</code> Shares the current HP amounts of the two monsters. The direction of the sharing is determined by the `direction` attribute, which can be either "user_to_target" or "target_to_user". The method of the sharing is determined by the `method` attribute, which can be either "weighted", "geometric" or "simple". ''(No such examples yet.)''
	* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP).		* <code>life_swap</code> Swaps the current HP amounts of the two monsters. The user receives the target's HP (up to the user's max HP), and the target receives the user's HP (up to the target's max HP). ''(No such examples yet.)''
	* <code>money</code> On a hit, gain dollars equal to the HP damage done. On a miss, user loses HP equal to the damage that would have been done.		* <code>money</code> On a hit, gain dollars equal to the HP damage done. On a miss, user loses HP equal to the damage that would have been done. [[Gold Digger]] uses this effect.
	* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target.		* <code>move_type x</code> The element of the move changes to match the element of x, which is either the user or the target. ''(No such examples yet.)''
	* <code>multiattack x</code> Make a number of attacks equal to x.		* <code>multiattack x</code> Make a number of attacks equal to x. For example, [[Leaf Barrage]] attempts two hits.
	* <code>photogenesis x, y, z</code> Heals the user based on time of day. The entry specifies the start hour (x), peak hour (y, when healing is greatest) and end hour (z). Healing is skipped if the user is indoors, the technique misses, or the user is at full health.		* <code>photogenesis x, y, z</code> Heals the user based on time of day. The entry specifies the start hour (x), peak hour (y, when healing is greatest) and end hour (z). Healing is skipped if the user is indoors, the technique misses, or the user is at full health. [[Solar Synthesis]] heals the user via <code>photogenesis 6,12,18</code>.
	* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP).		* <code>prop_damage x, y</code> Do damage to x, an amount equal to (y * the target's maximum HP). [[Panjandrum]] deals 25% of the target’s max HP.
	* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP).		* <code>prop_healing x, y</code> Heal x an amount equal to (y * the user's maximum HP). [[Blossom]] heals its user for 20% of max HP after damaging the foe.
	* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all".		* <code>remove x, y</code> Remove y condition from x (own monster, enemy monster or both). Can indicate a single condition or multiple, or use "positive", "negative" or "all". [[Feint]] removes positive conditions from the enemy.
	* <code>reverse x</code> Change x's element back to its original element after it has been switched. X can be the player's monster, the opponent's monster, both, etc.		* <code>reverse x</code> Change x's element back to its original element after it has been switched. X can be the player's monster, the opponent's monster, both, etc. [[Neutralize]] reverses type changes for every creature on the field, if they have been <code>switch</code>ed.
	* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x.		* <code>sacrifice x</code> The user loses all of their HP, and the target takes damage equal to the user's HP loss * x. [[Undertaker]] spends all of the user’s current HP to do that much damage.
	* <code>scope</code> The opponent's stats are revealed.		* <code>scope</code> The opponent's stats are revealed. [[Scope]] is the archetypal example.
	* <code>splash x</code> If the attack misses, do damage divided by x (~~usually~~ 2).		* <code>splash x</code> If the attack misses, do damage divided by x (always 2 in the conditions implemented so far). [[Surf]] is such an example.
	* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.		* <code>step_damage x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken.		* <code>step_healing x, y, z</code> Do damage based on the number of [[Steps]] that the user has taken. ''(No such examples yet.)''
	* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.		* <code>switch x, y</code> Changes x's element to y, which can be a specific element or random. X can be the player's monster, the opponent's monster, both, etc. For example, [[Ants]] changes the opponent's element to Earth while [[Chameleon]] changes the user's element to Wood.
	* <code>transfer</code> If the user ~~is [[Poisoned]]~~, the target ~~becomes Poisoned~~ instead. [[Suck Poison]] ~~works this way~~.		* <code>transfer x</code> If the user has the specified condition (x), the target gets the condition instead. [[Suck Poison]] transfers [[Poisoned]].


	~~''In progress''~~

	(Damage is technically an effect too, but is omitted from this list since it is discussed above.)		(Damage is technically an effect too, but is omitted from this list since it is discussed above.)