Aspect - Revision history

Pbelanger: /* Aspect Parameters */ Added $abilityNameParam0 and $aspectNameParam0

2022-02-09T03:20:47Z

Aspect Parameters: Added $abilityNameParam0 and $aspectNameParam0

← Older revision		Revision as of 03:20, 9 February 2022
Line 20:		Line 20:
	If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.		If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.

	In aspect and effect names, blurbs, and formulas, you can use '''$param0''', '''$param1''', etc. to show a certain parameter to the player. For example, in very specific scenarios with parameterized damage amounts, you may want to display something like "Deals $param0 damage". If the parameter referenced matches a text key in the dynamic.properties file, it will instead show the related text. For example, the aspect potencyBonus\|111\|REASON has the name "$param1 Potency Bonus". When the aspect is added to the Bone Bow in the form potencyBonus\|2\|item.bowBone, the aspect name shows up as "Bone Bow Potency Bonus"		In aspect and effect names, blurbs, and formulas, you can use '''$param0''', '''$param1''', etc. to show a certain parameter to the player. For example, in very specific scenarios with parameterized damage amounts, you may want to display something like "Deals $param0 damage". If the parameter referenced matches a text key in the dynamic.properties file, it will instead show the related text. For example, the aspect potencyBonus\|111\|REASON has the name "$param1 Potency Bonus". When the aspect is added to the Bone Bow in the form potencyBonus\|2\|item.bowBone, the aspect name shows up as "Bone Bow Potency Bonus". You can also use '''$abilityNameParam0''' to show the name of the ability with the given id, and '''$aspectNameParam0''' to show the name of the aspect with the given id. (Doesn't currently work if the given id has parameters)

	==Hooks==		==Hooks==

Pbelanger: /* Aspect Parameters */ $param can be used to display dynamic.properties text

2020-12-14T17:42:55Z

Aspect Parameters: $param can be used to display dynamic.properties text

← Older revision		Revision as of 17:42, 14 December 2020
Line 20:		Line 20:
	If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.		If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.

	In aspect names, blurbs, and formulas, you can use $param0, $param1, etc. to show a certain parameter to the player. For example, in very specific scenarios with parameterized damage amounts, you may want to display something like "Deals $param0 damage"		In aspect and effect names, blurbs, and formulas, you can use '''$param0''', '''$param1''', etc. to show a certain parameter to the player. For example, in very specific scenarios with parameterized damage amounts, you may want to display something like "Deals $param0 damage". If the parameter referenced matches a text key in the dynamic.properties file, it will instead show the related text. For example, the aspect potencyBonus\|111\|REASON has the name "$param1 Potency Bonus". When the aspect is added to the Bone Bow in the form potencyBonus\|2\|item.bowBone, the aspect name shows up as "Bone Bow Potency Bonus"

	==Hooks==		==Hooks==

Pbelanger: /* Aspect Parameters */ Added note on $param

2020-10-14T02:06:40Z

Aspect Parameters: Added note on $param

← Older revision		Revision as of 02:06, 14 October 2020
Line 19:		Line 19:

	If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.		If debugging non-hero aspects (for example, if you want to see aspects on the company, enemies, or sites), you can turn on Options>Interface>DEV[inspectNonHeroes] to allow showing the character sheets for non heroes.

			In aspect names, blurbs, and formulas, you can use $param0, $param1, etc. to show a certain parameter to the player. For example, in very specific scenarios with parameterized damage amounts, you may want to display something like "Deals $param0 damage"

	==Hooks==		==Hooks==

Pbelanger: /* Special Cases */ Added recruitCostAdjustment

2020-07-29T16:31:47Z

Special Cases: Added recruitCostAdjustment

← Older revision		Revision as of 16:31, 29 July 2020
Line 135:		Line 135:

	===Special Cases===		===Special Cases===
	~~Scenery has different aspects that are primarily used for interfusion abilities.~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 145:		Line 144:
	\|-		\|-
	\| {{!}}isLargePet{{!}}_ENTITY_ \|\| individual \|\| This is a large pet. See [[Outcomes#AddPet]]		\| {{!}}isLargePet{{!}}_ENTITY_ \|\| individual \|\| This is a large pet. See [[Outcomes#AddPet]]
			\|-
			\| {{!}}recruitCostAdjustment{{!}}REASON{{!}}AMOUNT \|\| individual \|\| Adjust the cost to recruit this individual by a certain amount. Specifically useful if you want to increase the cost of a legacy hero, which you could do with an [[Outcomes#AddHistory\|AddHistory Outcome]] that persists over the legacy, with an associated aspect like recruitCostAdjustment\|myReason\|1

	\|}		\|}

Pbelanger: /* Implicit Aspects */ Added SPELL_DAMAGE

2020-04-24T20:50:17Z

Implicit Aspects: Added SPELL_DAMAGE

← Older revision		Revision as of 20:50, 24 April 2020
Line 192:		Line 192:
	\|-		\|-
	\| UNIT_MAY_STOP_MOVING \|\| unit \|\| It's possible for this unit to stop moving where there are right now (i.e. they're standing on a walkable tile, not scenery or another unit)		\| UNIT_MAY_STOP_MOVING \|\| unit \|\| It's possible for this unit to stop moving where there are right now (i.e. they're standing on a walkable tile, not scenery or another unit)
			\|-
			\| SPELL_DAMAGE \|\| unit \|\| Amount of interfusion spell damage from relevant weapons (wands and staves, most notably)
	\|}		\|}

Pbelanger: /* Scenery */ Made scenery aspects bold

2020-02-05T19:13:57Z

Scenery: Made scenery aspects bold

← Older revision		Revision as of 19:13, 5 February 2020
Line 121:		Line 121:
	\|}		\|}
	Scenery also has different aspects that are primarily used for interfusion abilities. These aspects are as follows:		Scenery also has different aspects that are primarily used for interfusion abilities. These aspects are as follows:
	bone, book, liquid, mechanism, metal, plant, rock, shards, statue, textile, tools, tree, wood		'''bone, book, liquid, mechanism, metal, plant, rock, shards, statue, textile, tools, tree, wood,'''
	~~And~~ some more special ones, like:		and some more special ones, like:
	interactiveLampOn, lampCanFlare, lampIsFireSink, lampIsFireSource		'''interactiveLampOn, lampCanFlare, lampIsFireSink, lampIsFireSource'''

	===Abilities===		===Abilities===

Pbelanger: Added a lot of common and implicit aspects

2020-02-05T19:03:22Z

Added a lot of common and implicit aspects

Show changes

Peffers: /* Hooks */

2019-12-22T10:50:23Z

Hooks

← Older revision		Revision as of 10:50, 22 December 2019
Line 17:		Line 17:

	==Hooks==		==Hooks==
	[[Hook]]s are a special subcategory of aspects, which are usually designated when a hero is first generated, and are used to trigger hook quests.		[[Hook]]s are a special subcategory of aspects, which are usually designated when a hero is first generated, and are used to trigger [[Event#Opportunity\|hook quests]].

	[[Category:Character]]		[[Category:Character]]
	[[Category:Modding]]		[[Category:Modding]]
	[[Category:Modding Reference]]		[[Category:Modding Reference]]

Pbelanger: Moved information from Aspect Parameters into here, added link to Data Format Overview

2019-12-11T21:03:37Z

Moved information from Aspect Parameters into here, added link to Data Format Overview

← Older revision		Revision as of 21:03, 11 December 2019
Line 1:		Line 1:
	A named ~~marker~~ tied to an [[entity]], usually reflecting ~~its~~ narrative state, that add stats or ~~applies~~ specific effects.		Aspects are named markers tied to [[entity\|entities]], usually reflecting their narrative state, that '''add stats''' or '''apply specific [[Effects\|effects]]'''.

	For [[hero]]es, aspects are just facts about the hero. Stuff like "human", "female", "attractedToMen", "hunter", "missingLeftArm". Aspects can carry stat modifiers and Effects. Aspects are the workhorse of the dynamic content in the game, almost everything you need to know about a hero, site, anything really, can be accessed as an aspect (other than stat values). Aspects can be queried to find out almost ~~things~~ about an entity (other than [[history]], but that applies aspects that can be queried).		For [[hero]]es, aspects are just facts about the hero. Stuff like "human", "female", "attractedToMen", "hunter", "missingLeftArm". Aspects can carry stat modifiers and Effects. Aspects are the workhorse of the dynamic content in the game, almost everything you need to know about a hero, site, anything really, can be accessed as an aspect (other than stat values). Aspects can be queried to find out almost anything about an entity (other than [[history]], but that applies aspects that can be queried).

	~~A special subcategory of aspects is [[hook]]s~~.		Aspects can be temporary, like status effects (poisoned) or combat modifiers (combatModifier_buff_courage), or more permanent, like theme pieces (themePiece_fire_leftArm) or class upgrade abilities (hunterDeck_quellingmoss).

	For ~~modding~~, see [[Aspect Parameters]]		''(For a more general overview of how aspects relate to other parts of Wildermyth, see the [[Data Format Overview]])''

			==Aspect Parameters==
			Aspects can be parameterized, which looks like this: "boss_knockbackMelee\|6\|6+1d3".

			Parameterized aspects work by literally doing a find/replace in the aspect json itself, so when creating a parameterized aspect, use a parameter name that's unique, and then define the parameter in the parameters section. You can then use that parameter value to pass the entity id to the effect, and the effect can read it using matchSpecial -> parameter1

			The pipe character \| delimits parameters for both effects and aspects, parameters need to be defined for aspects in order to be passed on, but they don't need to be explicitly defined for effects.

			Aspect parameters can be used to store a relationship with a particular entity. In this case the entity's id will be used as the parameter content, and be passed down to effects as well. Effects can also target based on aspect relationships.

			==Hooks==
			[[Hook]]s are a special subcategory of aspects, which are usually designated when a hero is first generated, and are used to trigger hook quests.

	[[Category:Character]]		[[Category:Character]]
	[[Category:Modding]]		[[Category:Modding]]
			[[Category:Modding Reference]]

Croald at 05:14, 5 December 2019

2019-12-05T05:14:23Z

← Older revision		Revision as of 05:14, 5 December 2019
Line 8:		Line 8:

	[[Category:Character]]		[[Category:Character]]
			[[Category:Modding]]