to show a certain parameter to the player.

In aspect and effect names, blurbs, and formulas, you can use $param0, $param1, etc. 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 to allow showing the character sheets for non heroes.

matching 'loverWith*' would match any unit with a 'loverWith|ENTITY' aspect. If you're making an effect and want to check if an entity has a parameterized aspect without knowing what the parameter is, you can use the star (*) character. Effects can also target based on aspect relationships. In this case the entity's id will be used as the parameter content, and be passed down to effects as well. 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.Īspect parameters can be used to store a relationship with a particular entity. You can then use that parameter value to pass the entity id to the effect, and the effect can read it using matchSpecial -> parameter1 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. Aspects can be parameterized, which looks like this: 'boss_knockbackMelee|6|6+1d3'.

Wildermyth hooks