User:Mindtheblob/notes

2022-02-10T12:49:48Z

Mindtheblob: Created page with "I'm sorry you feel that way. I think everybody involved here sees the value of having a bot update the game data for the wiki. The issue seems to be more with the presentation..."

I'm sorry you feel that way. I think everybody involved here sees the value of having a bot update the game data for the wiki. The issue seems to be more with the presentation of said data. And to a lesser extent, some underlying differences in views on the wikis purpose.

I started writing some thoughts on this yesterday.

Theme Pieces

I think a sub section for every theme piece has merit and consistency, but admittedly, the scrolling through of repetition of related abilities will not please the reader, as has been discussed here. The difference to the game UI being, that instead of clicking on information one by one, the information is displayed in its entirety without reader choice, control, or filtering.

Perhaps there could still be some way of finding a middle ground?

Has separating effects (abilities) given by themePiece aspects into its own section of a theme page below theme pieces been discussed? There, they could be displayed once by effect id, requirements, and the current tool tips, which I feel are perfectly excellent.

Since these theme related abilities are effects of aspects, first given with theme pieces, then targeted with theme piece aspects, I wouldn't see it breaking the logic of the code to have a) a separate sections for abilities and b) some disclosure for dependent theme piece combinations. If and when any given effect requires [x, y, z, å] theme piece aspects. An effect like bearHug is given in either arm, but it won't be enabled until the aspect requirements of the effect are met in the effect's targets.

Non-existent upgrades

In my opinion, the foreseeable more confusing matter has to do with non-existent upgrades.
Showing a Thorn Lash+ when there isn't such a thing in the game files is confusing to the reader, as well as any future wiki contributor.

So take the botanical upgrades, since there is no ability upgrade aspect along the lines of theme_vine_upgrade nor is there any hint towards anything of the sort present or being planned for in the formulae of the theme's abilities, I don't quite see the case for it to exist in the wiki presentation, except for anticipating it based on a pattern.

But anticipating based on patterns in current presentation doesn't feel like the purpose of a game wiki. A case can be made to guard for future changes, but even this relies on the assumption that patterns will not be broken. Take the one-upgrade-per-theme -pattern. There is nothing restricting other theme piece related abilities and their upgrades to being added.

It's perfectly possible to add a leap ability for bear legs, and have a separate upgrade for it alongside of the Bear Swipes+ (theme_bear_upgrade) upgrade (tried this out today just to be sure :snappingturtle:). But it's not something we're going to anticipate.

The best possible scenario would be for the automated code to know how to validate an upgrade aspect as related to a theme piece's ability effect, and thus be worthy of an upgrade mention and tooltip. For common and class skills this won't be a problem because the upgraded ability is already specified in the upgrade aspect .json under "upgradeForAbility", which the theme upgrades lack.

But could there be a workaround? For example, since we know upgrade aspect id's appear in ability effects as part of formulae, could this knowledge be applied as something of the sort to be used to validate that an upgrade aspect does in fact modify an effect? (There might be exceptions where this does not apply?)

But if that is difficult to implement, I think a better scenario is to not present non-existent upgrades, whether that is done by commenting out or other means.

I agree it is beneficial to the reader to know there is no upgrade, but displaying these non-upgrades, to my eye at least, dilutes the purpose. It's more akin to showing non-facts than hiding facts. That being said, if a bot is able to find a new upgrade and implement it accordingly, well that's just awesome.

Targets and Scoring Guide

2022-02-04T07:26:03Z

Mindtheblob: /* Theme Eligibility */

This is an overview to help understand an [[event]]'s targets requirements, and why the event might occur (or fail). For more technical details, see [[Effects#Targets|Effects]] or [[Story Inputs and Outputs]].

==A Note on Role Names==
''A frequent source of confusion in understanding the wiki's event targeting arises when '''role names''' are confused with '''hero stats or aspects''':

[[File:RoleTutorial1.png|650px]]

[[File:RoleTutorial2.png|650px]]

''A role name is just a name.''

==Company and Chapter Targeting==

The most common requirement for the default '''company''' target is a '''chapter threshold.'''

Chapter is stored as an aspect called chapterNumber in company. All aspects have value.

The value for chapter is equal to the chapter of the game.

=====Examples of Company and Chapter Targeting=====
:'''Target (role): company'''
::'''Aspects:''' chapterNumber >= 2
::''This [[aspect]] threshold requires the aspect called chapterNumber to be greater than or equal to 2.''
::''An event with this requirement will only trigger in Chapter 2 or above.''

:'''Target (role): company'''
::'''Forbidden Aspects:''' seenEvent|encounter_heroesArriveAtSite_answertoAusterity
::''This forbidden aspect list forbids the aspect seenEvent|encounter_heroesArriveAtSite_answertoAusterity. The seenEvent aspects are gained upon encountering events.''
::''This particular aspect refers to the event [[Answer to Austerity]].
::''If the company has seen the event, the '''company''' target role can not be matched, and the event will not be able to trigger.''

==Overland Tile Biome and Site Targeting==

====Biome Targeting====

Events may have requirements for the overland [[tile]]. The most common requirement for an overland tile is a certain type of [[biome]]. By default, these are targeted in a required role called '''overlandTile''', but there can be exceptions.

=====Example of Biome Targeting=====
:'''Target (role): overlandTile'''
::'''Biome:''' swamp, forestDeciduous, forestConiferous
::''An event with this target role will require the overland tile to be a swamp, broadleaf forest, or pine forest.''

====Site targeting====

Sites are towns and [[station]]s on the [[overland map]] tiles. By default, a role named '''site''' is targeted in [[hostile site]] encounters.

'''Site targeting''' can have additional requirements, such as the type of station, and other aspects of the site.

Note that events can also target sites that are not on the tile the current party is on (see example '''B''' below).

=====Examples of Site Targeting=====
:'''A) Target (role): site'''
::'''Station:''' tannery
::''An event with this target role will require the event to take place on a site with a tannery station.''

:'''B) Target (role): site'''
::'''Aspects:''' town, VISIBLE_TILE
::''This is an example from the [[Star Dance]] event. The event is a wilderness scouting event, where, by default, site roles (these are called injected roles, because they are injected into the event) are not targeted.''
::''In this example, the role '''site''' targets one random town that is on a tile that is visible to the player. In this specific example, the '''site''' target role is an event mechanic used in the event's outcomes.''
::''For the event to be able to trigger, the company must have at least one town visible on the overland map.''

==Enemy and Dead Enemy Targeting==

Similarly to biomes and sites, events can also target specific factions of enemies. Mission victory or mission defeat events may target defeated enemy units from a target role of '''deadFoe'''.

=====Examples of Enemy Targeting=====
:'''Target (role): foes'''
::'''Aspects:''' drauven
::''An event with this target role requires the enemy at a hostile site to be drauven.''

:'''Target (role): deadFoe'''
::'''Aspects:''' drauven_skysinger
::''A mission victory/defeat event with this target role requires an enemy with the drauven_skysinger aspect (Deeven) to have been defeated in the previous mission.''

==Hero Targeting==
Almost all events require heroes to be targeted for roles. Furthermore, many events require heroes to match roles with specific criteria.
There are three main types of roles to consider:
#'''Required Roles'''
#'''Optional Roles'''
#'''Forbidden Roles'''
'''Required roles''' are mandatory. If no hero matches a particular required role, the event targeting will fail, and the event will not be in the pool of possible events for the encounter. '''Optional roles''' are not mandatory. An event may trigger even if an '''optional role''' is not matched. '''Forbidden roles''' are forbidden. If a forbidden role is matched to a hero, the event targeting will fail, and the event will not be in the pool of possible events for the encounter.

Note, to make matters more complicated, '''required roles''' may have optional targeting preferences, and '''optional roles''' may have required score thresholds.

This guide attempts to show both (required) and (optional) roles in the examples. They do, however, operate on the exact same principles. [[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Case Studies]] in the final section showcase some interesting examples.

For current purposes, the sub-sections in this section will briefly explain '''hero scoring''', '''aspects''', '''tests''', and '''theme eligibility'''.

====Hero Scoring====

'''Required''' and '''optional roles''' are the most common roles to come across in hero targeting. They typically choose their matches by the hero scoring the highest score of a '''score function'''.

''Note! There do exist other choosing methods for targets (for example, '''one random''', but for the sake of clarity, this guide will discuss the '''by score''' method as default).''

A '''score function''' is a function of criteria and their values for the role. These score functions may include, for example, '''[[personality]]''' or '''experience stats''', specific '''[[relationship]]s''' between heroes, and aspects such as '''hooks''' or '''items'''.

=====Examples of Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. For a hero to match this role, they must have a LEADER stat of 50 or above.''

:'''Role: hero''' (optional)
::'''Score Function:''' LEADER+HOTHEAD >= 100
::''This score function targets the sum of the LEADER and HOTHEAD stats of a hero, and has a score threshold of 100 or above. For a hero to match this role, the sum of their LEADER and HOTHEAD stats must be 100 or above.''
::''Note that this role is (optional). Even if no hero is matched to this role, the event can still trigger.''
::''Why would this role be optional? The event might use it for specific dialogue, or to enable extra choices, for example.''

:'''Role: hero''' (required)
::'''Score Function:''' ((30*hunter) + (30*hook_weird)) + LEADER
::''This slightly more complicated score function uses both aspects and stats. All aspects have value. The most common aspects in hero targeting include class aspects and hook aspects.''
::''For heroes with the hunter aspect (hunter class) the value of the aspect is 1, for others, the value is 0. For heroes with the hook weird, the value of the hook_weird aspect is 1.''
::''For example, for a hunter hero who does not have the WEIRD hook, the scoring would read ((30*1) + (30*0)) + LEADER''
::''The score function lacks a score threshold. This role will target a hero with the highest score of the sum of the aspect parentheses and the LEADER stat. That is to say, the hunter and hook aspects are not required, but will add to the score.''
::''Note! There are aspects that may have more value than 1.''

====Hero Aspects====

Another common requirement in hero targeting is the listing of '''Required''' or '''Forbidden Aspects'''. Listed '''Aspects''' are required for a hero to match the target role, whereas '''Forbidden Aspects''' make a hero with those [[aspect]]s ineligible for the role.

A less common variant of '''Aspects''' is '''Aspects (One of)'''. This variant requires the target to have at least one of the listed aspects.

Continuing with our previous example, lets add a '''Required''' and '''Forbidden Aspect''' to the role.

=====Example of Aspects and Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Forbidden Aspects:''' mystic
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required aspect called theme_crow (the aspect for the crow transformation). The Forbidden Aspects lists an aspect called mystic (the hero class). Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and not be a mystic.''

::''Note! A similar effect to the Forbidden Aspects example above could be achieved with a Aspects (One of): hunter, warrior.''

====Hero Tests====

A less common requirement is '''Tests'''. They are primarily used, when two stats do not want to be mixed in score functions.

=====Example of Test, Aspect, and Score Function=====
:'''Role: hero''' (optional)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Test:''' AGE <= 35
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required Aspect called theme_crow (the aspect for the crow transformation). The Test requires the hero's age to be less than or equal to 35. Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and be 35 years of age or younger.''
::''Note that this '''hero''' role is now (optional), an event can trigger even if this role is not matched to a hero.

====Theme Eligibility====

'''Theme Eligibility''' is ubiquitous in almost any event where a [[theme]] (transformation, pet) is given. '''Theme eligibility''' imposes the following requirements:

*No member of the company may have the same theme.
*The hero must not have [[Theme conflicts guide|conflicting themes]].
*The hero must have an empty slot for a theme piece.

This means there are quite a few checks to pass when an '''Eligible for Theme''' is present in hero targeting.

'''Important!''' No member of the company may have the theme that is tested for in '''Eligible for Theme'''.

=====Conflicting Themes=====
{{Main|Theme conflicts guide}}
Perhaps the trickiest feature is that there is no way of telling which [[theme]]s conflict with each other. For example, themes may conflict because of defined [[Theme conflicts guide#Detailed Discussion: Forbid Combine With|forbidden combinations]] in the game files. Or themes may be in practical conflict because events target the same theme slots. See the [[Theme conflicts guide|theme conflicts guide]] for further information.

Unlike [[aspect]]s, [[stat]]s, and [[relationship]]s, '''theme eligibility''' does not appear in '''score functions'''. It does appear along side of '''score functions''', similar to lists of aspects discussed above.

=====Example of Hero Theme Eligibility=====

:'''Role: target''' (required)
::'''Eligible for Theme:''' bear
::'''Eligible for Theme Piece:''' tattoo
::''For a hero to match this target role, no hero in the company must have the bear theme. The hero must not have conflicting themes with the bear theme, the hero must be eligible for a head slot theme piece. A list of coded and practical conflicts for the bear theme: ({{Theme conflicts|bear}})''

====Forbidden Roles====

'''Forbidden roles''' are far less common. If a '''forbidden role''' is matched, the event will not be in the pool of eligible encounter events triggered.

=====Example of a Forbidden Role=====
:'''Role: hero''' (required)
:'''Forbidden Role: hero2'''
:''This event would fail to trigger if the '''hero2''' was matched, in this case, we might assume the event is only available to a one hero party.''

====Role Names====

'''Important!''' When reading event targets, the name of a '''role''' is just a '''name'''. How the role is defined with '''scoring''', '''aspects''', '''tests''', and '''theme eligibility''', introduced above, determines if a hero can be matched to the role. Typical '''role names''' for heroes used in event targets include '''hero''', '''hero2''', personality names ('''goofball''', '''healer''', etc.), '''hook''', '''rival''', '''lover''', '''volunteer''', and so forth.

With this in mind, a role named '''rival''' may well only require a certain ''personality threshold'', or alternatively, it may not have ''any specific requirements at all''. Consider the following quiz:

=====Quiz: Roles Named Rival=====
:'''Role name: hero''' (required)
:''Let's first assume this role named '''hero''' will match any hero.''
::'''Question:''' ''Which One of the Roles Named Rival Requires a Rival?''
:::'''A) Role name: rival''' (required)
::::'''Aspects:''' mystic
:::'''B) Role name: rival''' (required)
::::'''Score Function:''' GOOFBALL >= 80
:::'''C) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero
:::'''D) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''Answer:''' '''D.''' The '''score function''' in '''C.''' does not specify a '''score threshold.''' This means the role will prefer to target a rival of '''hero''', but it is not mandatory.

====Special Cases of Hero Targeting====

In straightforward encounter events, a hero is selected for a single role from the party that triggered the event.

However, there are various special cases, where heroes may be targeted for more than one role, as well as cases, where heroes may be targeted from outside the party.

These special cases are typically used for selecting specific heroes for event choice panels, dialogue, and enabling special choices for heroes with specific requirements. An example of the latter, many transformations have unique choices in certain events, and these are targeted with an optional role, that may well target a hero already matched to another role.

'''Important!''' This may result in confusion when interpreting hero targeting. There may be more '''required roles''', than there are '''required heroes'''.

Is it possible for an event to '''require more heroes''' than there are '''required roles'''? Yes. Circumstantially. ([[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Here is a Case Study]])

Why is this? There are simply more mechanics involved to hero targeting. At the time of writing, the Wiki event targets do not account for definitions such as '''fromRoles''', '''notAlreadyMatchedAs''', and '''alreadyMatchedAs''' in Event Targeting, or the method by which a role chooses its target.

The '''fromRoles''' definition defines from which roles the role is drawn. The '''MatchedAs''' definitions are used to make sure that the same entity is either matched or not matched in another role.

These definitions can currently only be found in the Content Editor. Below, an example is given of what a special case might look like:

=====Example of a Special Case=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero'''

:'''Role: hero2''' (required)
::'''Forbidden Aspects:''' mystic
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero, rival'''

:'''Role: greedy''' (required)
::'''Score Function:''' max(GREEDY, SNARK)
::'''fromRoles: hero, hero2'''

::This example shows four required roles, but, in fact, only requires three heroes. As we have learned, '''hero''' requires a LEADER stat threshold, '''rival''' is required to be a rival of '''hero''', and '''hero2''' is required to not be a mystic. Unlike the previous three roles, the '''greedy''' role is drawn '''fromRoles: hero, hero2''' and does not have a '''notAlreadyMatchedAs''' definition. The score function in '''greedy''' role will target the hero with the highest GREEDY or SNARK stat, but only from the roles '''hero''' and '''hero2'''.

===Further Targeting Examples===

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| This section will further examine hero targeting by looking at examples.
|-
|
====Scoring Thresholds vs. No Scoring Thresholds====

First, let's consider the difference between a '''score function''' with a '''threshold''', and a '''score function''' '''without a threshold:'''

:'''Example:'''
:'''A) Role: bookish''' (optional)
::'''Score Function:''' BOOKISH >= 80

:'''B) Role: bookish''' (required)
::'''Score Function:''' BOOKISH

Lets assume these roles choose a target '''by score.''' Example '''A)''' requires a BOOKISH score of greater than or equal to 80, and will target the hero with the highest BOOKISH stat. Example '''B)''' will target the hero with the highest BOOKISH stat.

Note that the role in example '''A''' is (optional). This means that the event can trigger even if no hero is matched to it.

====The Max Scoring Function====

The '''max(x,y,z)''' '''function''' is the most common '''function''' (see [[Expressions]]) used in hero targeting '''score functions'''. It returns the highest value of a set of parameters.

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY)

Here, the '''max()''' function will target the hero with the highest CHARISMA or TENACITY stat.

The '''max()''' function can be used with thresholds:

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY) >= 20

Here, the '''max()''' function requires a hero with CHARISMA or TENACITY stat greater than or equal to 20, and will target the hero with the highest CHARISMA or TENACITY stat.

====Complex Scoring Functions and Thresholds====

So far we've entertained fairly simple '''score functions'''. But hero targeting may well look like the example below:

:'''Example:'''
:'''Role: statPotency''' (required)
::'''Score Function:''' (1000*mystic)+((10*max(BOOKISH,POET,SNARK))+POTENCY) >= 1000

This is an example from the [[Entanglement]] event. Here, the role requires a hero to pass a score threshold of 1000. The '''score function''' uses STATS as well as an ASPECT (mystic).

All aspects have value. For mystic aspect, the value is 1.

The parentheses on the left are then (1000*1) or (1000*0) depending on whether the hero is of the mystic class. In practice, this target will ''almost'' exclusively target a hero of the mystic class with the highest stat in BOOKISH, POET, or SNARK (and throw in a little potency for marginal cases).

Note, it is still ''theoretically'' possible for the role to target a hero who is not a mystic but has a very high (100) BOOKISH, POET, or SNARK stat, or a hero with a POET (99) stat and POTENCY (10) stat, for example. For the latter case, the parentheses on the right would read ''(10*99+10) = 1000''.

====Relationship Scoring====

One of the most common hero targeting functions are relationship scoring functions. Like aspects, '''relationships have value'''.

For '''relationships''', the value is between 1 and 5 (a value of 1 being a '''level one''' ''one heart (lover)/lightning (rival)/pawn (friend)'' relationship and 5 being a fully maxed relationship.

Relationship scoring operates on the same principles already discussed: They may be required (have '''thresholds''') or preferred (lack '''thresholds''').

'''Important!''' In '''relationship scoring''', pay attention to the '''.rolename''' suffix in the function. This determines the previously targeted role that is the target of the relationship.

:'''Examples:'''
:'''A) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 1

Here, any LOVER relationship is required with the role '''hero'''.

:'''B) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 5

Here, a maxed LOVER relationship is required with the role '''hero'''.

:'''C) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero

Here, a LOVER relationship is preferred, but not mandatory, with '''hero''' because the '''score threshold''' is missing.

:'''D) Role: hero2''' (required)
::'''Score Function:''' SHIP_WITH.hero >= 3

Here, any RELATIONSHIP (Friend, Rival, Lover) greater than of equal to level three is required.

:'''E) Role: hero2''' (required)
::'''Score Function:''' PARENT_OF.hero >= 1

Here, '''hero2''' must be a parent of '''hero'''.

====Case Study: The Wolf Price====
''Now let's look at an interesting case study of hero targeting for the wilderness scouting [[The Wolf Price]].''

''It is one of the rare examples where circumstances arise, where more heroes may be required than there are required roles.''

''To understand why, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions are added.

:'''Role: hook''' (optional)
::'''Score Function:''' hook_Wildheart + hook_Mysterious >= 1
::'''Eligible for Theme:''' wolf
:::'''fromRoles:''' party

:'''Role: volunteer''' (required)
::'''Score Function:''' ((30*hunter)+(10*warrior))+LONER
::'''Eligible for Theme:''' wolf
::'''Eligible for Theme Piece:''' head
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook

:'''Role: coward''' (required)
::'''Score Function:''' COWARD
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook, volunteer

::''The '''hook''' role is an (optional) role, for a hero to match the role, the sum of the score of their hook_Wildheart (Wildheart hook) and hook_Mysterious (Mysterious hook) aspects must be greater than or equal to 1. Because the role is optional, the event can trigger without a hero being matched to it, but more on that later.
::''The '''hook''' role must be eligible for the theme wolf. No other hero in the company may have the wolf transformation. The hero may not have conflicting themes with the theme [[Wolftouched]]. A full list of themes that conflict with [[Wolftouched]] in unmodded games: ({{Theme conflicts|wolf}}).
::''The role '''volunteer''' is the first (required) role. The '''score function''' lacks a '''score threshold''' so the function will choose the highest scoring hero for the function. Note that for a hero with the class aspects hunter or warrior, a bonus of (30*1) or (10*1) is added to the sum with the LONER stat, respectively.
::''A hero matched to the role of '''volunteer''' must be eligible for the wolf theme (discussed above in the '''hook''' role). The hero matched to the '''volunteer''' role must also have a free head theme slot.
::''The role '''coward''' matches a hero with the highest COWARD stat, who is not already matched as the roles '''hook''', or '''volunteer'''.
::''Why is this event worthy of a case study? Because of the ordering of the roles and the '''notAlreadyMatchedAs''' definitions.
::''The (optional) '''hook''' role is targeted first. If a hero is matched to this role, it means that the next two roles must be separate heroes. This is because the '''notAlreadyMatchedAs''' definitions for the '''volunteer''' and '''coward''' roles both define the '''hook''' role as an impossible match (a hero can't be matched to both a '''hook''' and '''coward''' role, for example.'')
::''This means that even though there are only two required roles ('''volunteer''' and '''coward'''). There are instances where this event will require three heroes, if one of the heroes matches as the '''hook''' role.
::''Confused? Let's consider a starting party of three heroes with the following hooks:''
::''Hero John ('''mysterious''', lucky, distant), Hero Jane (brash, integrity, lucky), Hero Jin (brash, lucky, distant)
::''Now, if we send Hero Jane and Hero Jin to scout a wilderness tile, they will be able to trigger the event, because neither of them can match the '''hook''' role.''
::''But if we send John and Jin, John will match the '''hook''' role, because they have the hook_Mysterious aspect. The event will then not be able to find a match for the (required) '''coward''' role, and will not be able to trigger.''
::''If we send the whole party, they will be able to trigger the event.''
::''If we send John and Jin together, but John has the '''bear''' or '''skeleton''' theme, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' wolf, because of the conflicting theme.)''
::''Similarly, if we send John and Jin together, but John has the full celestial theme, for example, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' because they are not eligible for a theme piece of the theme.) Note! John doesn't need a tail slot theme filled, even though a tail for the wolf theme exists.''

====Case Study: Drifters====
::''Putting it all together. Let's look at a complete case of hero targeting for the [[Drifters]] event.''

::For sake of clarity, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions, briefly discussed in the previous section, are added.

:'''Role: coward''' (required)
::'''Score:''' max(COWARD, BOOKISH, LONER) >= 80
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score:''' RIVAL_WITH.coward >= 1
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward

:'''Role: leader''' (required)
::'''Score:''' LEADER
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward , rival

:'''Role: hero''' (required)
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' leader

The '''coward''' role requires a hero with one of the stats of COWARD, BOOKISH, or LONER to be greater than or equal to 80. No one in the company may have the theme green ([[Sylvan]]). The hero must not have conflicting themes. A full list of themes that conflict with [[Sylvan]] in an unmodded game: ({{Theme conflicts|sylvan}}). The hero must have an open head theme slot.

The requirements for the '''rival''' role are exactly the same, but instead of a STAT requirement, the '''rival''' role requires a hero that is the rival of the '''coward''' role (notice the '''score threshold''').

The '''leader''' role prefers a hero with a high LEADER stat (notice the lack of a '''score threshold''').

The '''hero''' role has no requirements. Notice that the '''notAlreadyMatchedAs''' definition only defines the '''leader''' role. This means that the '''hero''' role may match with the same hero that is matched in the '''coward''' or '''rival''' roles, meaning that the event can actually be triggered with only three heroes.

====Case Study: The Heirloom Spring====
''Finally, let's look at a complete targeting for the wilderness scouting event [[The Heirloom Spring]]:

:'''Role: overlandTile'''
::'''Biome:''' swamp

:'''Role: romantic''' (required)
::'''Score:''' ROMANTIC
::'''Eligible for Theme:''' petDuck
::'''Eligible for Theme Piece:''' duck
:::'''fromRoles:''' party

:'''Role: ship''' (required)
::'''Score:''' SHIP_WITH.romantic
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic

:'''Role: volunteer''' (optional)
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic, ship

:'''Role: lover''' (optional)
::'''Score:''' LOVER_WITH.romantic >= 1

:'''Role: rival''' (optional)
::'''Score:''' RIVAL_WITH.romantic >= 1

::''First, the '''overlandTile''' role requires the biome of the tile to be a swamp.''
::''The '''romantic''' role has a '''score function''' without a '''score threshold'''. This will target the hero with the highest score in the ROMANTIC stat.''
::''The '''romantic''' role must be eligible for the theme petDuck (duck). No other member in the company may have a pet duck. The hero must not have another pet in the pet theme slot (ground pets).''
::''Note! If the highest scoring hero in the ROMANTIC stat '''score function''' has a pet, the event can still target a hero with the second/third/etc highest ROMANTIC stat and a free pet theme slot.''
::''The '''ship''' role is a required role. The SHIP_WITH.romantic '''score function''' has no '''score threshold''', so it will target the hero with the highest level relationship with the '''romantic''' role in the party. If there are no relationships, the role will still match a hero, because there is no '''score threshold'''.
::''The '''volunteer''' is an optional role drawn from the party. The event will trigger even if the role is not matched to a hero. This means the minimum number of heroes for the event is 2.''
::''The '''lover''' and '''rival''' roles are optional roles with a '''score function''' and a '''score threshold'''. Note that these roles do not draw '''fromRoles:''' party. This means they will target any hero in the company who is a lover or rival of the '''romantic''' role. In this specific example, these two optional roles are only used in dialogue of the event, so comic panels will know the names of the lover and rival of the hero matched in the '''romantic''' role.''
|}

==Campaign Specific Event Blocks==

Some campaigns block events. Most notably, the [[Troygan the Enchanger|event]] for [[Mortificial Enhancements]] is blocked in [[The Enduring War| the Enduring War]] campaign.

Below is a list of campaign specific blocked events.

=====All the Bones of Summer=====
* [[The Abandoned]]
* [[Terms of Endearment]]

=====Eluna and the Moth=====
* [[Peripheral Views]]
* [[Necessary Evil]]
* [[What May Hatch]]

=====Monarchs Under the Mountain=====
* [[By Hoof and Horn]]
*[[Misgivings]]

=====The Enduring War=====
*[[Troygan the Enchanger]]
*[[Threshing Machine]]
*[[Mark of the Times]]
*[[The Clockwork Tower]]
*[[Pursuit Of Knowledge]]

== Checking Event Failures ==

If an event does not seem to ever occur even though you think it should, you can enable [[Testing|dev mode]] and the Pick Events cheat, then scroll down in the list of events to see why a particular event failed.

[[File:ArriveAtHostileSiteFailedEvent.PNG]]

In that case, no eligible hero had a (required) bookish score of at least 80.

A few other reasons why an event might fail or not occur are:
* Wrong [[Event#Event types|event type]]. The event you're trying to trigger is an 'Arrive at hostile site' type, but your party is 'Wilderness scouting.' (You wouldn't find a hostile site event in the wilderness scouting Pick Events list.)
* Event only occurs once per campaign. (The event already happened in the current campaign. Pick Events will show that reason for the event failure.)
* Eligible for theme failure. The event won't happen if you already have a hero with that theme in your company (or your existing theme conflicts with your desired theme). (You can wait to recruit another hero with that theme, until your current hero gets the desired theme.)

Theme

2022-02-04T07:20:06Z

Mindtheblob: /* Theme conflicts */

As your [[hero]]es participate in certain specific events, some event outcomes will modify a hero's appearance, abilities, and/or stats. An example of a common theme, also called a '''transformation''', is [[Flamesoul]], where one or more of the hero's limbs can be replaced with fire limbs.

A theme can modify the appearance of (one or more of) a hero's theme slots, possibly through [[Hero#Death_and_Maiming|maiming]]. A hero can have more than one theme (such as Flamesoul, and a [[pet]]), as long as the themes don't conflict with each other.

== Theme slots ==

Theme modifications can include replacing the hero's head, left arm, right arm, left leg, right leg, or torso. In addition, the hero can gain wings, a tail, or a pet.
Transformation body parts will be randomly offered at chapter intervals or forcibly added if a hero gets [[maim|maimed]].

== Theme skins ==

Some themes have cosmetic variants (which can be unlocked by completing theme-related [[achievement]]s). Once unlocked, they can be chosen in the customize section in the character sheet.

== Theme conflicts ==
{{Main|Theme conflicts guide}}
{{See also|Theme order conflicts guide}}

A hero can have multiple themes as long as the themes do not conflict with each other (see [[Theme conflicts guide]]).

Incompatible themes may be coded, or include transformations that affect the same body part. For example a hero cannot be [[Sylvan]] '''and''' [[Crystalline]], as the facial sylvan tattoo is incompatible with the gem eye. However, a hero could be Sylvan '''and''' [[Spell Touched]], with a Sylvan tattoo and blue skin.

If you recruit a [[legacy]] hero who already has a particular theme, that theme event will not occur in the campaign even if other heroes would be eligible for it. If you wish to have two party members with the same theme, wait to recruit legacy heroes until after your other hero receives the theme.

== List of themes ==

{| class="wikitable sortable"
|-
! ID
! Name
! Blurb
! Effect
! [[Theme conflicts guide|Is Blocked By]]
! Acquisition
! Theme skin
|-
| bear
| [[Beartouched]]
| Hero contains the soul of an old bear
| +1 Health, -0.5 Speed, [[Beartouched/Bear Hug|Bear Hug]], [[Beartouched/Swipes|Swipes]]
| {{Theme conflicts|bear}}
| [[The Shape Of Things To Come]]
| Ghost
|-
| crow
| [[Crowtouched]]
| Hero's inner crow is showing
| +1 Speed, +10 Dodge, Crow Peck, Crow Scratch, Scratch and Claw
| {{Theme conflicts|crow}}
| [[Company of Crows]]
| White
|-
| deepist
| [[Mark of the Horn]]
| Hero is marked with Deepist symbols
| +5 Charisma, +10 Tenacity, +0.5 Warding
| {{Theme conflicts|deepist}}
| [[Into The Underworld]]
| ---
|-
| deepistMole
| [[Deepist Spy]]
| Hero spent time blending in among the Deepists
| ---
| {{Theme conflicts|deepistMole}}
| [[Monarchs Under the Mountain]]
| ---
|-
| drauvenWings
| [[Drauven Wings]]
| Looted off a dead Drauven and repurposed
| +1.4 Speed
| {{Theme conflicts|drauvenWings}}
| [[Featherless Flight]]
| ---
|-
| fire
| [[Flamesoul]]
| Fire twists inside Hero, just barely contained
| +1 Warding, -0.1 Speed, Cone of Fire, Flame Strike
| {{Theme conflicts|fire}}
| [[Stories of Fire]]
| Lava
|-
| foothill
| [[Child of the Hills]]
| Hero carries the hills in their very bones
| +1 Armor, -0.8 Speed, immune to knockback, Crush, Stonewall
| {{Theme conflicts|foothill}}
| [[The Offering]]
| Canyon
|-
| fox
| [[Foxish]]
| Hero has a bit of a fox's flash
| +4 Stunt, +4 Dodge, +0.4 Speed
| {{Theme conflicts|fox}}
| [[The Merchant]]
| ---
|-
| frog
| [[Frogtouched]]
| Hero has been transformed into a bit of a frog
| Tongue Whip
| {{Theme conflicts|frog}}
| [[Jigsaw]]
| ---
|-
| frost
| [[Frost]]
| Winterlock's warning to the firewatching world
| +10 Charisma
| {{Theme conflicts|frost}}
| [[Out of the Rain]]
| ---
|-
| gem
| [[Crystalline]]
| Shine on, you crazy diamond
| +6 Stunt, +5 Block, -0.3 Speed, Shield, Crystal Sword
| {{Theme conflicts|gem}}
| [[Heart of Stone]]
| Knight
|-
| gorgon
| [[Gorgonoid]]
| Hero is infected with a Gorgon seed
| Hook gouge
| {{Theme conflicts|gorgon}}
| [[Age of Ulstryx]]
| ---
|-
| gorgonStone
| [[Petrified]]
| Turned to stone by a Gorgon curse
| -0.7 Speed, +0.2 Armor, Stone Claw
| {{Theme conflicts|gorgonStone}}
| [[True Gorgon]]
| ---
|-
| green
| [[Sylvan]]
| Marked with green after sleeping in a spirit's clearing
| +5 Retirement age, -5 Tenacity, -5 Block, +0.8 Speed, Invigoration, Witherbolt
| {{Theme conflicts|green}}
| [[Drifters]]
| Knot
|-
| hawk
| [[Hawksoul]]
| Hero's inner hawk is showing
| +1.4 Speed
| {{Theme conflicts|hawk}}
| [[Dreams of Icarus]]
| ---
|-
| morthagi
| [[Mortificial Enhancements]]
| Hero has replaced and augmented parts of their body with mortificial components
| +0.3 Speed, -3 Dodge, +0.3 Speed, Wrist Bolt, Hammer
| {{Theme conflicts|morthagi}}
| [[Troygan the Enchanger]]
| Steel
|-
| mothWings
| [[Mothly]]
| Hero's satiny wings can unfold to cast a shroud over those hero wishes to hide from sight
| ---
| {{Theme conflicts|mothWings}}
| [[Eluna and the Moth]]
| ---
|-
| rat
| [[Ratlike]]
| Hero has a certain ratlike spirit about them
| ---
| {{Theme conflicts|rat}}
| [[The Offering]]
| ---
|-
| scorpion
| [[Scorpioid]]
| Hero has a wicked, segmented aspect
| Tail Stab
| {{Theme conflicts|scorpion}}
| [[The Merchant]]
| ---
|-
| shadow
| [[Shadow]]
| Something that had been sleeping inside you is now waking up
| +1 Speed, Harvest, Dread Harvest
| {{Theme conflicts|shadow}}
| [[The Inhabitant]]
| Wild
|-
| skeleton
| [[Skeletal]]
| Hero is cursed by the dagger of the Oldwane mystics
| +0.3 Speed, +2 Spell Damage, +2 Potency, +2 Warding, +1000 Retirement Age, No Relationships, Inscrutable Stare, Bitter Scratch, Dagger Strike
| {{Theme conflicts|skeleton}}
| [[To Humble Ends]]
| Monster
|-
| skunk
| [[Skunkish]]
| Hero has a foreboding odor
| Tail Spray
| {{Theme conflicts|skunk}}
| [[The Merchant]]
| ---
|-
| spellTouched
| [[Spell Touched]]
| Hero touched a raw primal node, and has been marked
| -0.5 Physical Damage, +2 Potency, +5 Recovery rate, +10 retirement age
| {{Theme conflicts|spellTouched}}
| [[Worlds Apart]]
| ---
|-
| star
| [[Celestial]]
| An ethereal sparkle emanates from Hero
| Blinding Attacks, Shooting Star, Falling Stars, +0.2 Speed, -0.4 Armor, Celestial Path
| {{Theme conflicts|star}}
| [[Star Dance]]
| Gold
|-
| storm
| [[Stormtouched]]
| Hero contains the coiled power of a storm
| Stormgaze, -5 Block, Static Shock, Jumpjolt, Chain Lightning, Thunder Stomp
| {{Theme conflicts|storm}}
| [[Distant Thunder]]
| Sea
|-
| tinyWings
| [[Teeny Wings]]
| Frankly, these are useless
| ---
| {{Theme conflicts|tinyWings}}
| [[Dreams of Icarus]]
| ---
|-
| tree
| [[Elmsoul]]
| There's an ancient, Elmish soul inside Hero's heart
| +10 Recovery rate, +0.6 Armor, -0.8 Speed, Bash, Splinterskin (Full transformation)
| {{Theme conflicts|tree}}
| [[Splinter]]
| Autumn
|-
| vine
| [[Botanical]]
| Hero's blood runs a little green
| +10 Recovery rate, +5 Dodge, -0.3 Speed, Thorn Lash, Entangle
| {{Theme conflicts|vine}}
| [[The Strider]]
| Mythical
|-
| vultureAcolyte
| [[Vulture Acolyte]]
| Hero serves the Vulture Lord
| ---
| {{Theme conflicts|vultureAcolyte}}
| [[The Lonely Cost]]
| ---
|-
| wolf
| [[Wolftouched]]
| Hero accepted the blessing of the Wolf God
| -4 Block, +0.5 Speed, Wolf Bite, Wolf Claw, Frenzy
| {{Theme conflicts|wolf}}
| [[The Wolf Price]]
| Dire
|}

=== List of pet themes ===

All pets conflict with each other, except the Drauven Bird which sits on the Hero's shoulder rather than on the ground.

{| class="wikitable sortable"
|-
! ID
! Name
! Image
! Blurb
! Effect
! Acquisition
|-
| petBirdDrauven
| [[Drauven Bird]]
| [[File:DrauvenStormthroat bird.png|center|100x50px]]
| Hero healed the bird's injury and apparently earned some loyalty
| +5 Melee accuracy, +5 Range accuracy
| [[One Small Life]]
|-
| petCritter
| [[Critter]]
| [[File:CritterStand.png|center|100x50px]]
| Hero had made friends with a critter
| +15 Melee Accuracy
| [[Sneakthief]]
|-
| petDuck
| [[Duck]]
| [[File:DuckM.png|center|100x50px]]
| This duck has decided that you are the love of its life, and nothing will convince it otherwise
| +7 Dodge, +7 Block
| [[The Heirloom Spring]]
|-
| petFireChicken
| [[Fire Chicken]]
| [[File:Animal fireChicken.png|center|100x50px]]
| Hero has taken on a pet Fire Chicken
| Hero's Pet can light a fire on an adjacent tile, once every three turns.
| [[Fire Eagles]]
|-
| petPineCone
| [[Pinecone]]
| [[File:PineconePet.png|center|100x50px]]
| Hero has taken on a pet pinecone-spirit-creature-thing
| Hero can [[Walling|wall]] with trees.
| [[Silver and Shadows]]
|-
| petRabbit
| [[Golden Rabbit]]
| [[File:Animal RabbitAvenger.png|center|100x50px]]
| Hero is now bonded to a glowing rabbit
| +1 [[Stat#Bonus Damage|Bonus Damage]]
| [[Avenger]]
|-
| petRat
| [[Rat]]
| [[File:RatStand.png|center|100x50px]]
| Hero has taken on a pet Rat
| +5 Dodge
| [[Curiosity and Cats]]
|-
|}

[[Category:Theme]]
[[Category:Pet]]

Theme

2022-02-04T07:14:46Z

Mindtheblob: /* List of themes */

As your [[hero]]es participate in certain specific events, some event outcomes will modify a hero's appearance, abilities, and/or stats. An example of a common theme, also called a '''transformation''', is [[Flamesoul]], where one or more of the hero's limbs can be replaced with fire limbs.

A theme can modify the appearance of (one or more of) a hero's theme slots, possibly through [[Hero#Death_and_Maiming|maiming]]. A hero can have more than one theme (such as Flamesoul, and a [[pet]]), as long as the themes don't conflict with each other.

== Theme slots ==

Theme modifications can include replacing the hero's head, left arm, right arm, left leg, right leg, or torso. In addition, the hero can gain wings, a tail, or a pet.
Transformation body parts will be randomly offered at chapter intervals or forcibly added if a hero gets [[maim|maimed]].

== Theme skins ==

Some themes have cosmetic variants (which can be unlocked by completing theme-related [[achievement]]s). Once unlocked, they can be chosen in the customize section in the character sheet.

== Theme conflicts ==
{{Main|Theme conflicts guide}}
{{See also|Theme order conflicts guide}}

A hero can have multiple themes as long as the themes do not conflict with each other.

Incompatible themes include transformations that affect the same body part. For example a hero cannot be [[Beartouched]] '''and''' [[Wolftouched]], as the facial bear tattoo is incompatible with a wolf head. However, a hero could be Wolftouched '''and''' [[Spell Touched]], with a wolf head and blue skin.

If you recruit a [[legacy]] hero who already has a particular theme, that theme event will not occur in the campaign even if other heroes would be eligible for it. If you wish to have two party members with the same theme, wait to recruit legacy heroes until after your other hero receives the theme.

== List of themes ==

{| class="wikitable sortable"
|-
! ID
! Name
! Blurb
! Effect
! [[Theme conflicts guide|Is Blocked By]]
! Acquisition
! Theme skin
|-
| bear
| [[Beartouched]]
| Hero contains the soul of an old bear
| +1 Health, -0.5 Speed, [[Beartouched/Bear Hug|Bear Hug]], [[Beartouched/Swipes|Swipes]]
| {{Theme conflicts|bear}}
| [[The Shape Of Things To Come]]
| Ghost
|-
| crow
| [[Crowtouched]]
| Hero's inner crow is showing
| +1 Speed, +10 Dodge, Crow Peck, Crow Scratch, Scratch and Claw
| {{Theme conflicts|crow}}
| [[Company of Crows]]
| White
|-
| deepist
| [[Mark of the Horn]]
| Hero is marked with Deepist symbols
| +5 Charisma, +10 Tenacity, +0.5 Warding
| {{Theme conflicts|deepist}}
| [[Into The Underworld]]
| ---
|-
| deepistMole
| [[Deepist Spy]]
| Hero spent time blending in among the Deepists
| ---
| {{Theme conflicts|deepistMole}}
| [[Monarchs Under the Mountain]]
| ---
|-
| drauvenWings
| [[Drauven Wings]]
| Looted off a dead Drauven and repurposed
| +1.4 Speed
| {{Theme conflicts|drauvenWings}}
| [[Featherless Flight]]
| ---
|-
| fire
| [[Flamesoul]]
| Fire twists inside Hero, just barely contained
| +1 Warding, -0.1 Speed, Cone of Fire, Flame Strike
| {{Theme conflicts|fire}}
| [[Stories of Fire]]
| Lava
|-
| foothill
| [[Child of the Hills]]
| Hero carries the hills in their very bones
| +1 Armor, -0.8 Speed, immune to knockback, Crush, Stonewall
| {{Theme conflicts|foothill}}
| [[The Offering]]
| Canyon
|-
| fox
| [[Foxish]]
| Hero has a bit of a fox's flash
| +4 Stunt, +4 Dodge, +0.4 Speed
| {{Theme conflicts|fox}}
| [[The Merchant]]
| ---
|-
| frog
| [[Frogtouched]]
| Hero has been transformed into a bit of a frog
| Tongue Whip
| {{Theme conflicts|frog}}
| [[Jigsaw]]
| ---
|-
| frost
| [[Frost]]
| Winterlock's warning to the firewatching world
| +10 Charisma
| {{Theme conflicts|frost}}
| [[Out of the Rain]]
| ---
|-
| gem
| [[Crystalline]]
| Shine on, you crazy diamond
| +6 Stunt, +5 Block, -0.3 Speed, Shield, Crystal Sword
| {{Theme conflicts|gem}}
| [[Heart of Stone]]
| Knight
|-
| gorgon
| [[Gorgonoid]]
| Hero is infected with a Gorgon seed
| Hook gouge
| {{Theme conflicts|gorgon}}
| [[Age of Ulstryx]]
| ---
|-
| gorgonStone
| [[Petrified]]
| Turned to stone by a Gorgon curse
| -0.7 Speed, +0.2 Armor, Stone Claw
| {{Theme conflicts|gorgonStone}}
| [[True Gorgon]]
| ---
|-
| green
| [[Sylvan]]
| Marked with green after sleeping in a spirit's clearing
| +5 Retirement age, -5 Tenacity, -5 Block, +0.8 Speed, Invigoration, Witherbolt
| {{Theme conflicts|green}}
| [[Drifters]]
| Knot
|-
| hawk
| [[Hawksoul]]
| Hero's inner hawk is showing
| +1.4 Speed
| {{Theme conflicts|hawk}}
| [[Dreams of Icarus]]
| ---
|-
| morthagi
| [[Mortificial Enhancements]]
| Hero has replaced and augmented parts of their body with mortificial components
| +0.3 Speed, -3 Dodge, +0.3 Speed, Wrist Bolt, Hammer
| {{Theme conflicts|morthagi}}
| [[Troygan the Enchanger]]
| Steel
|-
| mothWings
| [[Mothly]]
| Hero's satiny wings can unfold to cast a shroud over those hero wishes to hide from sight
| ---
| {{Theme conflicts|mothWings}}
| [[Eluna and the Moth]]
| ---
|-
| rat
| [[Ratlike]]
| Hero has a certain ratlike spirit about them
| ---
| {{Theme conflicts|rat}}
| [[The Offering]]
| ---
|-
| scorpion
| [[Scorpioid]]
| Hero has a wicked, segmented aspect
| Tail Stab
| {{Theme conflicts|scorpion}}
| [[The Merchant]]
| ---
|-
| shadow
| [[Shadow]]
| Something that had been sleeping inside you is now waking up
| +1 Speed, Harvest, Dread Harvest
| {{Theme conflicts|shadow}}
| [[The Inhabitant]]
| Wild
|-
| skeleton
| [[Skeletal]]
| Hero is cursed by the dagger of the Oldwane mystics
| +0.3 Speed, +2 Spell Damage, +2 Potency, +2 Warding, +1000 Retirement Age, No Relationships, Inscrutable Stare, Bitter Scratch, Dagger Strike
| {{Theme conflicts|skeleton}}
| [[To Humble Ends]]
| Monster
|-
| skunk
| [[Skunkish]]
| Hero has a foreboding odor
| Tail Spray
| {{Theme conflicts|skunk}}
| [[The Merchant]]
| ---
|-
| spellTouched
| [[Spell Touched]]
| Hero touched a raw primal node, and has been marked
| -0.5 Physical Damage, +2 Potency, +5 Recovery rate, +10 retirement age
| {{Theme conflicts|spellTouched}}
| [[Worlds Apart]]
| ---
|-
| star
| [[Celestial]]
| An ethereal sparkle emanates from Hero
| Blinding Attacks, Shooting Star, Falling Stars, +0.2 Speed, -0.4 Armor, Celestial Path
| {{Theme conflicts|star}}
| [[Star Dance]]
| Gold
|-
| storm
| [[Stormtouched]]
| Hero contains the coiled power of a storm
| Stormgaze, -5 Block, Static Shock, Jumpjolt, Chain Lightning, Thunder Stomp
| {{Theme conflicts|storm}}
| [[Distant Thunder]]
| Sea
|-
| tinyWings
| [[Teeny Wings]]
| Frankly, these are useless
| ---
| {{Theme conflicts|tinyWings}}
| [[Dreams of Icarus]]
| ---
|-
| tree
| [[Elmsoul]]
| There's an ancient, Elmish soul inside Hero's heart
| +10 Recovery rate, +0.6 Armor, -0.8 Speed, Bash, Splinterskin (Full transformation)
| {{Theme conflicts|tree}}
| [[Splinter]]
| Autumn
|-
| vine
| [[Botanical]]
| Hero's blood runs a little green
| +10 Recovery rate, +5 Dodge, -0.3 Speed, Thorn Lash, Entangle
| {{Theme conflicts|vine}}
| [[The Strider]]
| Mythical
|-
| vultureAcolyte
| [[Vulture Acolyte]]
| Hero serves the Vulture Lord
| ---
| {{Theme conflicts|vultureAcolyte}}
| [[The Lonely Cost]]
| ---
|-
| wolf
| [[Wolftouched]]
| Hero accepted the blessing of the Wolf God
| -4 Block, +0.5 Speed, Wolf Bite, Wolf Claw, Frenzy
| {{Theme conflicts|wolf}}
| [[The Wolf Price]]
| Dire
|}

=== List of pet themes ===

All pets conflict with each other, except the Drauven Bird which sits on the Hero's shoulder rather than on the ground.

{| class="wikitable sortable"
|-
! ID
! Name
! Image
! Blurb
! Effect
! Acquisition
|-
| petBirdDrauven
| [[Drauven Bird]]
| [[File:DrauvenStormthroat bird.png|center|100x50px]]
| Hero healed the bird's injury and apparently earned some loyalty
| +5 Melee accuracy, +5 Range accuracy
| [[One Small Life]]
|-
| petCritter
| [[Critter]]
| [[File:CritterStand.png|center|100x50px]]
| Hero had made friends with a critter
| +15 Melee Accuracy
| [[Sneakthief]]
|-
| petDuck
| [[Duck]]
| [[File:DuckM.png|center|100x50px]]
| This duck has decided that you are the love of its life, and nothing will convince it otherwise
| +7 Dodge, +7 Block
| [[The Heirloom Spring]]
|-
| petFireChicken
| [[Fire Chicken]]
| [[File:Animal fireChicken.png|center|100x50px]]
| Hero has taken on a pet Fire Chicken
| Hero's Pet can light a fire on an adjacent tile, once every three turns.
| [[Fire Eagles]]
|-
| petPineCone
| [[Pinecone]]
| [[File:PineconePet.png|center|100x50px]]
| Hero has taken on a pet pinecone-spirit-creature-thing
| Hero can [[Walling|wall]] with trees.
| [[Silver and Shadows]]
|-
| petRabbit
| [[Golden Rabbit]]
| [[File:Animal RabbitAvenger.png|center|100x50px]]
| Hero is now bonded to a glowing rabbit
| +1 [[Stat#Bonus Damage|Bonus Damage]]
| [[Avenger]]
|-
| petRat
| [[Rat]]
| [[File:RatStand.png|center|100x50px]]
| Hero has taken on a pet Rat
| +5 Dodge
| [[Curiosity and Cats]]
|-
|}

[[Category:Theme]]
[[Category:Pet]]

Misgivings

2022-02-03T07:44:14Z

Mindtheblob:

{{Infobox event
| event = Misgivings
| image = Deepist_shrineLeather.png
| author = Heather Albano
| type = Mission victory
}}

A brief event with no choices. One of the party has misgivings after a [[battle]] with [[deepists]].

== Trivia ==

This event is not possible to trigger in the [[Monarchs Under the Mountain]] campaign.

== Images ==

[[File:Misgivings.PNG]]

[[Category:Event]]

By Hoof and Horn

2022-02-03T07:43:36Z

Mindtheblob:

{{Infobox event
| event = By Hoof and Horn
| image = Byhoofandhorn1.png
| author = Shae Rossi
| type = Arrive at hostile site
}}

In a forest, the heroes find someone who has lost their spouse to the [[deepist]] cult.

== Choices ==

''1. "Join us. We'll do this task together."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| The NPC joins the battle against the deepists.
|}
''2. "Let us handle this. You shouldn't have to be involved."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| The party battles the deepists.
|}

== Trivia ==

Regardless of the choice, the party is given the option to recruit the NPC for 2 legacy points, who begins with the following line in their history:

''<q><Hero> once knew a great love, until their their beloved fell to the sway of the Deepists. Unable to save them, <Hero> joined <Company> to help keep others from falling to false promises.

This event is not possible to trigger in the [[Monarchs Under the Mountain]] campaign.

== Images ==

<gallery mode=packed heights=150px>

</gallery>

{{Targets2
| page = Targets encounter heroesArriveAtSite byHoofAndHorn
}}

[[Category:Event]]

What May Hatch

2022-02-03T07:42:22Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = What May Hatch
| image = Thrixl_chrysallis.png
| author = Shae Rossi
| type = Mission victory
}}

After a [[battle]] the party find an unhatched [[Dream Chrysalis|Thrixl egg]].

== Choices ==

''1. "We should destroy it! One less monster in the world."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Destroy the egg.
|}
''2. "Who are we to deny something its birth? It could choose a path for good. We should let it have that chance."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Leave the egg.
|}

== Trivia ==

This event occurs after a battle with [[Thrixl]].

A different tiding occurs at the end of the chapter depending on the choice made.

This event is not possible to trigger in the [[Eluna and the Moth]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:Whatmayhatch1.png
</gallery>

[[Category:Event]]

Necessary Evil

2022-02-03T07:41:55Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = Necessary Evil
| image = Necessaryevil2.PNG
| author = Jeremy Bernstein
| type = Arrive at hostile site
}}

The party encounter a [[Seeker|Thrixl]] who communicates telepathically with one of the heroes.

== Choices ==

''1. "It's in their mind? Let's take it out!"''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Destroy the Thrixl and begin the battle as normal.
|}
''2. "Wait! If it's telling the truth, this could be an opportunity to get to better understand the Thrixl."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Accept their offer of help: the Thrixl will join the party for the next battle. After combat, add a Thrixl calamity card. The following is added to the possessed hero's history:
''<q>A Thrixl inhabited <Hero>'s mind for a time, and <Hero>'s companions oft worried that malign effects might still be lurking in the deep recesses of their mind.</q>''
|}

== Trivia ==

This event is not possible to trigger in the [[Eluna and the Moth]] campaign.

== Images ==
<gallery mode=packed heights=150px>
File:Necessaryevil1.PNG| Thrixl surprise
</gallery>
[[Category:Event]]

Peripheral Views

2022-02-03T07:41:35Z

Mindtheblob:

{{Infobox event
| event = Peripheral Views
| image = Peripheralviews2.PNG
| author = Shae Rossi
| type = Arrive at hostile site
}}

The party arrive at some ruins full of lurking [[Thrixl]].

== Choices ==

''1. <q>No one should suffer what these creatures can do.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Start the battle as normal.
|}
''2. <q><Hero>, try to focus. You're making the rest of us skittish now.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| '''Success''': Start the battle as normal. '''Failure''': Start the battle with {{Nausea}}.
|}

== Trivia ==

This event is not possible to trigger in the [[Eluna and the Moth]] campaign.

== Images ==

<gallery mode=packed heights=150px>
Peripheralviews1.PNG
Peripheralviews2.PNG
</gallery>

[[Category:Event]]

Terms of Endearment

2022-02-03T07:39:54Z

Mindtheblob:

{{Infobox event
| event = Terms of Endearment
| image = Termsofendearment2.png
| author = Anne Austin
| type = Mission victory
}}

A parent and child have a discussion after a [[battle]].

== Choices ==

No choices.

== Trivia ==

The nickname and dialogue for the pair depends on their personality.

This event is not possible to trigger in [[All the Bones of Summer]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:Termsofendearment3.png|
</gallery>

[[Category:Event]]

The Abandoned

2022-02-03T07:39:16Z

Mindtheblob:

{{Infobox event
| event = The Abandoned
| image = Theabandoned3.png
| author = Jeremy Bernstein
| type = Wilderness scouting
}}

The party hears the cry of a wounded animal... which turns out to be an injured [[Drauven]] child.

== Choices ==

''1. "Ugh. Fine. We'll camp here and "help" it."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| '''Success''': One Drauven calamity card is removed. '''Failure''': No effect.
|}
''2. "We can't waste our time on this. We have to move on."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| No effect.
|}
''3. "Who said anything about "letting" it die?"''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| '''Success''': No effect. '''Failure''': The two heroes become rivals.
|}

== Trivia ==
The party must contain a hero with a <code>healer >=60</code> and another with <code>hothead+coward >=60</code> for this event to trigger.

This event is not possible to trigger in [[All the Bones of Summer]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:The_abandoned.PNG|
File:The_abandoned_2.PNG|
</gallery>

[[Category:Event]]

Pursuit Of Knowledge

2022-02-03T07:37:37Z

Mindtheblob:

{{Infobox event
| event = Pursuit Of Knowledge
| image = Morthagi_wardrobe.png ‎
| author = Shae Rossi
| type = Mission victory
}}

After a [[battle]] with [[Morthagi]], the party finds a human hiding in a wardrobe.

== Choices ==

''1. "Another person to split loot with? I don't think so."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Turn them away.
|}
''2. "Our company would be stronger with you."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| A new hero is recruited for '''2 legacy points''' (more if the party is already large). The following is added to the new hero's history:
<q>The pursuit of knowledge left <Hero> huddled and hiding in a Morthagi wardrobe while their companions fell to the vile mechanicals. They decided the best way to continue their research was to join <Company> and hide no more.</q>
|}

== Trivia ==

If you don't have 2 legacy points, you'll just spend what you have; you cannot go below 0. You will not be able to choose their [[class]].

This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:Pursuitofknowledge1.PNG
</gallery>

[[Category:Event]]

Targets and Scoring Guide

2022-02-03T07:28:46Z

Mindtheblob:

This is an overview to help understand an [[event]]'s targets requirements, and why the event might occur (or fail). For more technical details, see [[Effects#Targets|Effects]] or [[Story Inputs and Outputs]].

==A Note on Role Names==
''A frequent source of confusion in understanding the wiki's event targeting arises when '''role names''' are confused with '''hero stats or aspects''':

[[File:RoleTutorial1.png|650px]]

[[File:RoleTutorial2.png|650px]]

''A role name is just a name.''

==Company and Chapter Targeting==

The most common requirement for the default '''company''' target is a '''chapter threshold.'''

Chapter is stored as an aspect called chapterNumber in company. All aspects have value.

The value for chapter is equal to the chapter of the game.

=====Examples of Company and Chapter Targeting=====
:'''Target (role): company'''
::'''Aspects:''' chapterNumber >= 2
::''This [[aspect]] threshold requires the aspect called chapterNumber to be greater than or equal to 2.''
::''An event with this requirement will only trigger in Chapter 2 or above.''

:'''Target (role): company'''
::'''Forbidden Aspects:''' seenEvent|encounter_heroesArriveAtSite_answertoAusterity
::''This forbidden aspect list forbids the aspect seenEvent|encounter_heroesArriveAtSite_answertoAusterity. The seenEvent aspects are gained upon encountering events.''
::''This particular aspect refers to the event [[Answer to Austerity]].
::''If the company has seen the event, the '''company''' target role can not be matched, and the event will not be able to trigger.''

==Overland Tile Biome and Site Targeting==

====Biome Targeting====

Events may have requirements for the overland [[tile]]. The most common requirement for an overland tile is a certain type of [[biome]]. By default, these are targeted in a required role called '''overlandTile''', but there can be exceptions.

=====Example of Biome Targeting=====
:'''Target (role): overlandTile'''
::'''Biome:''' swamp, forestDeciduous, forestConiferous
::''An event with this target role will require the overland tile to be a swamp, broadleaf forest, or pine forest.''

====Site targeting====

Sites are towns and [[station]]s on the [[overland map]] tiles. By default, a role named '''site''' is targeted in [[hostile site]] encounters.

'''Site targeting''' can have additional requirements, such as the type of station, and other aspects of the site.

Note that events can also target sites that are not on the tile the current party is on (see example '''B''' below).

=====Examples of Site Targeting=====
:'''A) Target (role): site'''
::'''Station:''' tannery
::''An event with this target role will require the event to take place on a site with a tannery station.''

:'''B) Target (role): site'''
::'''Aspects:''' town, VISIBLE_TILE
::''This is an example from the [[Star Dance]] event. The event is a wilderness scouting event, where, by default, site roles (these are called injected roles, because they are injected into the event) are not targeted.''
::''In this example, the role '''site''' targets one random town that is on a tile that is visible to the player. In this specific example, the '''site''' target role is an event mechanic used in the event's outcomes.''
::''For the event to be able to trigger, the company must have at least one town visible on the overland map.''

==Enemy and Dead Enemy Targeting==

Similarly to biomes and sites, events can also target specific factions of enemies. Mission victory or mission defeat events may target defeated enemy units from a target role of '''deadFoe'''.

=====Examples of Enemy Targeting=====
:'''Target (role): foes'''
::'''Aspects:''' drauven
::''An event with this target role requires the enemy at a hostile site to be drauven.''

:'''Target (role): deadFoe'''
::'''Aspects:''' drauven_skysinger
::''A mission victory/defeat event with this target role requires an enemy with the drauven_skysinger aspect (Deeven) to have been defeated in the previous mission.''

==Hero Targeting==
Almost all events require heroes to be targeted for roles. Furthermore, many events require heroes to match roles with specific criteria.
There are three main types of roles to consider:
#'''Required Roles'''
#'''Optional Roles'''
#'''Forbidden Roles'''
'''Required roles''' are mandatory. If no hero matches a particular required role, the event targeting will fail, and the event will not be in the pool of possible events for the encounter. '''Optional roles''' are not mandatory. An event may trigger even if an '''optional role''' is not matched. '''Forbidden roles''' are forbidden. If a forbidden role is matched to a hero, the event targeting will fail, and the event will not be in the pool of possible events for the encounter.

Note, to make matters more complicated, '''required roles''' may have optional targeting preferences, and '''optional roles''' may have required score thresholds.

This guide attempts to show both (required) and (optional) roles in the examples. They do, however, operate on the exact same principles. [[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Case Studies]] in the final section showcase some interesting examples.

For current purposes, the sub-sections in this section will briefly explain '''hero scoring''', '''aspects''', '''tests''', and '''theme eligibility'''.

====Hero Scoring====

'''Required''' and '''optional roles''' are the most common roles to come across in hero targeting. They typically choose their matches by the hero scoring the highest score of a '''score function'''.

''Note! There do exist other choosing methods for targets (for example, '''one random''', but for the sake of clarity, this guide will discuss the '''by score''' method as default).''

A '''score function''' is a function of criteria and their values for the role. These score functions may include, for example, '''[[personality]]''' or '''experience stats''', specific '''[[relationship]]s''' between heroes, and aspects such as '''hooks''' or '''items'''.

=====Examples of Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. For a hero to match this role, they must have a LEADER stat of 50 or above.''

:'''Role: hero''' (optional)
::'''Score Function:''' LEADER+HOTHEAD >= 100
::''This score function targets the sum of the LEADER and HOTHEAD stats of a hero, and has a score threshold of 100 or above. For a hero to match this role, the sum of their LEADER and HOTHEAD stats must be 100 or above.''
::''Note that this role is (optional). Even if no hero is matched to this role, the event can still trigger.''
::''Why would this role be optional? The event might use it for specific dialogue, or to enable extra choices, for example.''

:'''Role: hero''' (required)
::'''Score Function:''' ((30*hunter) + (30*hook_weird)) + LEADER
::''This slightly more complicated score function uses both aspects and stats. All aspects have value. The most common aspects in hero targeting include class aspects and hook aspects.''
::''For heroes with the hunter aspect (hunter class) the value of the aspect is 1, for others, the value is 0. For heroes with the hook weird, the value of the hook_weird aspect is 1.''
::''For example, for a hunter hero who does not have the WEIRD hook, the scoring would read ((30*1) + (30*0)) + LEADER''
::''The score function lacks a score threshold. This role will target a hero with the highest score of the sum of the aspect parentheses and the LEADER stat. That is to say, the hunter and hook aspects are not required, but will add to the score.''
::''Note! There are aspects that may have more value than 1.''

====Hero Aspects====

Another common requirement in hero targeting is the listing of '''Required''' or '''Forbidden Aspects'''. Listed '''Aspects''' are required for a hero to match the target role, whereas '''Forbidden Aspects''' make a hero with those [[aspect]]s ineligible for the role.

A less common variant of '''Aspects''' is '''Aspects (One of)'''. This variant requires the target to have at least one of the listed aspects.

Continuing with our previous example, lets add a '''Required''' and '''Forbidden Aspect''' to the role.

=====Example of Aspects and Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Forbidden Aspects:''' mystic
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required aspect called theme_crow (the aspect for the crow transformation). The Forbidden Aspects lists an aspect called mystic (the hero class). Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and not be a mystic.''

::''Note! A similar effect to the Forbidden Aspects example above could be achieved with a Aspects (One of): hunter, warrior.''

====Hero Tests====

A less common requirement is '''Tests'''. They are primarily used, when two stats do not want to be mixed in score functions.

=====Example of Test, Aspect, and Score Function=====
:'''Role: hero''' (optional)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Test:''' AGE <= 35
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required Aspect called theme_crow (the aspect for the crow transformation). The Test requires the hero's age to be less than or equal to 35. Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and be 35 years of age or younger.''
::''Note that this '''hero''' role is now (optional), an event can trigger even if this role is not matched to a hero.

====Theme Eligibility====

'''Theme Eligibility''' is ubiquitous in almost any event where a [[theme]] (transformation, pet) is given. '''Theme eligibility''' is quirky. The Content Editor blurb states:

''Must be able to get the given theme (doesn't already have the theme, no conflicting themes, has an available slot for one of the theme pieces to go in, and no other heroes already have that theme).''

This means there are quite a few checks to pass when an '''Eligible for Theme''' is present in hero targeting.

'''Important!''' No member of the company may have the theme that is tested for in '''Eligible for Theme'''.

=====Conflicting Themes=====
{{Main|Theme conflicts guide}}
Perhaps the trickiest feature is that there is no way of telling which [[theme]]s conflict with each other. For example, themes may conflict because of defined [[Theme conflicts guide#Detailed Discussion: Forbid Combine With|forbidden combinations]] in the game files. Or themes may be in practical conflict because events target the same theme slots. See the [[Theme conflicts guide|theme conflicts guide]] for further information.

Unlike [[aspect]]s, [[stat]]s, and [[relationship]]s, '''theme eligibility''' does not appear in '''score functions'''. It does appear along side of '''score functions''', similar to lists of aspects discussed above.

=====Example of Hero Theme Eligibility=====

:'''Role: target''' (required)
::'''Eligible for Theme:''' bear
::'''Eligible for Theme Piece:''' tattoo
::''For a hero to match this target role, no hero in the company must have the bear theme. The hero must not have conflicting themes with the bear theme (wolf), the hero must be eligible for a head slot theme piece.''

====Forbidden Roles====

'''Forbidden roles''' are far less common. If a '''forbidden role''' is matched, the event will not be in the pool of eligible encounter events triggered.

=====Example of a Forbidden Role=====
:'''Role: hero''' (required)
:'''Forbidden Role: hero2'''
:''This event would fail to trigger if the '''hero2''' was matched, in this case, we might assume the event is only available to a one hero party.''

====Role Names====

'''Important!''' When reading event targets, the name of a '''role''' is just a '''name'''. How the role is defined with '''scoring''', '''aspects''', '''tests''', and '''theme eligibility''', introduced above, determines if a hero can be matched to the role. Typical '''role names''' for heroes used in event targets include '''hero''', '''hero2''', personality names ('''goofball''', '''healer''', etc.), '''hook''', '''rival''', '''lover''', '''volunteer''', and so forth.

With this in mind, a role named '''rival''' may well only require a certain ''personality threshold'', or alternatively, it may not have ''any specific requirements at all''. Consider the following quiz:

=====Quiz: Roles Named Rival=====
:'''Role name: hero''' (required)
:''Let's first assume this role named '''hero''' will match any hero.''
::'''Question:''' ''Which One of the Roles Named Rival Requires a Rival?''
:::'''A) Role name: rival''' (required)
::::'''Aspects:''' mystic
:::'''B) Role name: rival''' (required)
::::'''Score Function:''' GOOFBALL >= 80
:::'''C) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero
:::'''D) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''Answer:''' '''D.''' The '''score function''' in '''C.''' does not specify a '''score threshold.''' This means the role will prefer to target a rival of '''hero''', but it is not mandatory.

====Special Cases of Hero Targeting====

In straightforward encounter events, a hero is selected for a single role from the party that triggered the event.

However, there are various special cases, where heroes may be targeted for more than one role, as well as cases, where heroes may be targeted from outside the party.

These special cases are typically used for selecting specific heroes for event choice panels, dialogue, and enabling special choices for heroes with specific requirements. An example of the latter, many transformations have unique choices in certain events, and these are targeted with an optional role, that may well target a hero already matched to another role.

'''Important!''' This may result in confusion when interpreting hero targeting. There may be more '''required roles''', than there are '''required heroes'''.

Is it possible for an event to '''require more heroes''' than there are '''required roles'''? Yes. Circumstantially. ([[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Here is a Case Study]])

Why is this? There are simply more mechanics involved to hero targeting. At the time of writing, the Wiki event targets do not account for definitions such as '''fromRoles''', '''notAlreadyMatchedAs''', and '''alreadyMatchedAs''' in Event Targeting, or the method by which a role chooses its target.

The '''fromRoles''' definition defines from which roles the role is drawn. The '''MatchedAs''' definitions are used to make sure that the same entity is either matched or not matched in another role.

These definitions can currently only be found in the Content Editor. Below, an example is given of what a special case might look like:

=====Example of a Special Case=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero'''

:'''Role: hero2''' (required)
::'''Forbidden Aspects:''' mystic
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero, rival'''

:'''Role: greedy''' (required)
::'''Score Function:''' max(GREEDY, SNARK)
::'''fromRoles: hero, hero2'''

::This example shows four required roles, but, in fact, only requires three heroes. As we have learned, '''hero''' requires a LEADER stat threshold, '''rival''' is required to be a rival of '''hero''', and '''hero2''' is required to not be a mystic. Unlike the previous three roles, the '''greedy''' role is drawn '''fromRoles: hero, hero2''' and does not have a '''notAlreadyMatchedAs''' definition. The score function in '''greedy''' role will target the hero with the highest GREEDY or SNARK stat, but only from the roles '''hero''' and '''hero2'''.

===Further Targeting Examples===

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| This section will further examine hero targeting by looking at examples.
|-
|
====Scoring Thresholds vs. No Scoring Thresholds====

First, let's consider the difference between a '''score function''' with a '''threshold''', and a '''score function''' '''without a threshold:'''

:'''Example:'''
:'''A) Role: bookish''' (optional)
::'''Score Function:''' BOOKISH >= 80

:'''B) Role: bookish''' (required)
::'''Score Function:''' BOOKISH

Lets assume these roles choose a target '''by score.''' Example '''A)''' requires a BOOKISH score of greater than or equal to 80, and will target the hero with the highest BOOKISH stat. Example '''B)''' will target the hero with the highest BOOKISH stat.

Note that the role in example '''A''' is (optional). This means that the event can trigger even if no hero is matched to it.

====The Max Scoring Function====

The '''max(x,y,z)''' '''function''' is the most common '''function''' (see [[Expressions]]) used in hero targeting '''score functions'''. It returns the highest value of a set of parameters.

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY)

Here, the '''max()''' function will target the hero with the highest CHARISMA or TENACITY stat.

The '''max()''' function can be used with thresholds:

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY) >= 20

Here, the '''max()''' function requires a hero with CHARISMA or TENACITY stat greater than or equal to 20, and will target the hero with the highest CHARISMA or TENACITY stat.

====Complex Scoring Functions and Thresholds====

So far we've entertained fairly simple '''score functions'''. But hero targeting may well look like the example below:

:'''Example:'''
:'''Role: statPotency''' (required)
::'''Score Function:''' (1000*mystic)+((10*max(BOOKISH,POET,SNARK))+POTENCY) >= 1000

This is an example from the [[Entanglement]] event. Here, the role requires a hero to pass a score threshold of 1000. The '''score function''' uses STATS as well as an ASPECT (mystic).

All aspects have value. For mystic aspect, the value is 1.

The parentheses on the left are then (1000*1) or (1000*0) depending on whether the hero is of the mystic class. In practice, this target will ''almost'' exclusively target a hero of the mystic class with the highest stat in BOOKISH, POET, or SNARK (and throw in a little potency for marginal cases).

Note, it is still ''theoretically'' possible for the role to target a hero who is not a mystic but has a very high (100) BOOKISH, POET, or SNARK stat, or a hero with a POET (99) stat and POTENCY (10) stat, for example. For the latter case, the parentheses on the right would read ''(10*99+10) = 1000''.

====Relationship Scoring====

One of the most common hero targeting functions are relationship scoring functions. Like aspects, '''relationships have value'''.

For '''relationships''', the value is between 1 and 5 (a value of 1 being a '''level one''' ''one heart (lover)/lightning (rival)/pawn (friend)'' relationship and 5 being a fully maxed relationship.

Relationship scoring operates on the same principles already discussed: They may be required (have '''thresholds''') or preferred (lack '''thresholds''').

'''Important!''' In '''relationship scoring''', pay attention to the '''.rolename''' suffix in the function. This determines the previously targeted role that is the target of the relationship.

:'''Examples:'''
:'''A) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 1

Here, any LOVER relationship is required with the role '''hero'''.

:'''B) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 5

Here, a maxed LOVER relationship is required with the role '''hero'''.

:'''C) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero

Here, a LOVER relationship is preferred, but not mandatory, with '''hero''' because the '''score threshold''' is missing.

:'''D) Role: hero2''' (required)
::'''Score Function:''' SHIP_WITH.hero >= 3

Here, any RELATIONSHIP (Friend, Rival, Lover) greater than of equal to level three is required.

:'''E) Role: hero2''' (required)
::'''Score Function:''' PARENT_OF.hero >= 1

Here, '''hero2''' must be a parent of '''hero'''.

====Case Study: The Wolf Price====
''Now let's look at an interesting case study of hero targeting for the wilderness scouting [[The Wolf Price]].''

''It is one of the rare examples where circumstances arise, where more heroes may be required than there are required roles.''

''To understand why, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions are added.

:'''Role: hook''' (optional)
::'''Score Function:''' hook_Wildheart + hook_Mysterious >= 1
::'''Eligible for Theme:''' wolf
:::'''fromRoles:''' party

:'''Role: volunteer''' (required)
::'''Score Function:''' ((30*hunter)+(10*warrior))+LONER
::'''Eligible for Theme:''' wolf
::'''Eligible for Theme Piece:''' head
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook

:'''Role: coward''' (required)
::'''Score Function:''' COWARD
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook, volunteer

::''The '''hook''' role is an (optional) role, for a hero to match the role, the sum of the score of their hook_Wildheart (Wildheart hook) and hook_Mysterious (Mysterious hook) aspects must be greater than or equal to 1. Because the role is optional, the event can trigger without a hero being matched to it, but more on that later.
::''The '''hook''' role must be eligible for the theme wolf. No other hero in the company may have the wolf transformation. The hero may not have conflicting themes with the theme [[Wolftouched]]. A full list of themes that conflict with [[Wolftouched]] in unmodded games: ({{Theme conflicts|wolf}}).
::''The role '''volunteer''' is the first (required) role. The '''score function''' lacks a '''score threshold''' so the function will choose the highest scoring hero for the function. Note that for a hero with the class aspects hunter or warrior, a bonus of (30*1) or (10*1) is added to the sum with the LONER stat, respectively.
::''A hero matched to the role of '''volunteer''' must be eligible for the wolf theme (discussed above in the '''hook''' role). The hero matched to the '''volunteer''' role must also have a free head theme slot.
::''The role '''coward''' matches a hero with the highest COWARD stat, who is not already matched as the roles '''hook''', or '''volunteer'''.
::''Why is this event worthy of a case study? Because of the ordering of the roles and the '''notAlreadyMatchedAs''' definitions.
::''The (optional) '''hook''' role is targeted first. If a hero is matched to this role, it means that the next two roles must be separate heroes. This is because the '''notAlreadyMatchedAs''' definitions for the '''volunteer''' and '''coward''' roles both define the '''hook''' role as an impossible match (a hero can't be matched to both a '''hook''' and '''coward''' role, for example.'')
::''This means that even though there are only two required roles ('''volunteer''' and '''coward'''). There are instances where this event will require three heroes, if one of the heroes matches as the '''hook''' role.
::''Confused? Let's consider a starting party of three heroes with the following hooks:''
::''Hero John ('''mysterious''', lucky, distant), Hero Jane (brash, integrity, lucky), Hero Jin (brash, lucky, distant)
::''Now, if we send Hero Jane and Hero Jin to scout a wilderness tile, they will be able to trigger the event, because neither of them can match the '''hook''' role.''
::''But if we send John and Jin, John will match the '''hook''' role, because they have the hook_Mysterious aspect. The event will then not be able to find a match for the (required) '''coward''' role, and will not be able to trigger.''
::''If we send the whole party, they will be able to trigger the event.''
::''If we send John and Jin together, but John has the '''bear''' or '''skeleton''' theme, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' wolf, because of the conflicting theme.)''
::''Similarly, if we send John and Jin together, but John has the full celestial theme, for example, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' because they are not eligible for a theme piece of the theme.) Note! John doesn't need a tail slot theme filled, even though a tail for the wolf theme exists.''

====Case Study: Drifters====
::''Putting it all together. Let's look at a complete case of hero targeting for the [[Drifters]] event.''

::For sake of clarity, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions, briefly discussed in the previous section, are added.

:'''Role: coward''' (required)
::'''Score:''' max(COWARD, BOOKISH, LONER) >= 80
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score:''' RIVAL_WITH.coward >= 1
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward

:'''Role: leader''' (required)
::'''Score:''' LEADER
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward , rival

:'''Role: hero''' (required)
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' leader

The '''coward''' role requires a hero with one of the stats of COWARD, BOOKISH, or LONER to be greater than or equal to 80. No one in the company may have the theme green ([[Sylvan]]). The hero must not have conflicting themes. A full list of themes that conflict with [[Sylvan]] in an unmodded game: ({{Theme conflicts|sylvan}}). The hero must have an open head theme slot.

The requirements for the '''rival''' role are exactly the same, but instead of a STAT requirement, the '''rival''' role requires a hero that is the rival of the '''coward''' role (notice the '''score threshold''').

The '''leader''' role prefers a hero with a high LEADER stat (notice the lack of a '''score threshold''').

The '''hero''' role has no requirements. Notice that the '''notAlreadyMatchedAs''' definition only defines the '''leader''' role. This means that the '''hero''' role may match with the same hero that is matched in the '''coward''' or '''rival''' roles, meaning that the event can actually be triggered with only three heroes.

====Case Study: The Heirloom Spring====
''Finally, let's look at a complete targeting for the wilderness scouting event [[The Heirloom Spring]]:

:'''Role: overlandTile'''
::'''Biome:''' swamp

:'''Role: romantic''' (required)
::'''Score:''' ROMANTIC
::'''Eligible for Theme:''' petDuck
::'''Eligible for Theme Piece:''' duck
:::'''fromRoles:''' party

:'''Role: ship''' (required)
::'''Score:''' SHIP_WITH.romantic
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic

:'''Role: volunteer''' (optional)
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic, ship

:'''Role: lover''' (optional)
::'''Score:''' LOVER_WITH.romantic >= 1

:'''Role: rival''' (optional)
::'''Score:''' RIVAL_WITH.romantic >= 1

::''First, the '''overlandTile''' role requires the biome of the tile to be a swamp.''
::''The '''romantic''' role has a '''score function''' without a '''score threshold'''. This will target the hero with the highest score in the ROMANTIC stat.''
::''The '''romantic''' role must be eligible for the theme petDuck (duck). No other member in the company may have a pet duck. The hero must not have another pet in the pet theme slot (ground pets).''
::''Note! If the highest scoring hero in the ROMANTIC stat '''score function''' has a pet, the event can still target a hero with the second/third/etc highest ROMANTIC stat and a free pet theme slot.''
::''The '''ship''' role is a required role. The SHIP_WITH.romantic '''score function''' has no '''score threshold''', so it will target the hero with the highest level relationship with the '''romantic''' role in the party. If there are no relationships, the role will still match a hero, because there is no '''score threshold'''.
::''The '''volunteer''' is an optional role drawn from the party. The event will trigger even if the role is not matched to a hero. This means the minimum number of heroes for the event is 2.''
::''The '''lover''' and '''rival''' roles are optional roles with a '''score function''' and a '''score threshold'''. Note that these roles do not draw '''fromRoles:''' party. This means they will target any hero in the company who is a lover or rival of the '''romantic''' role. In this specific example, these two optional roles are only used in dialogue of the event, so comic panels will know the names of the lover and rival of the hero matched in the '''romantic''' role.''
|}

==Campaign Specific Event Blocks==

Some campaigns block events. Most notably, the [[Troygan the Enchanger|event]] for [[Mortificial Enhancements]] is blocked in [[The Enduring War| the Enduring War]] campaign.

Below is a list of campaign specific blocked events.

=====All the Bones of Summer=====
* [[The Abandoned]]
* [[Terms of Endearment]]

=====Eluna and the Moth=====
* [[Peripheral Views]]
* [[Necessary Evil]]
* [[What May Hatch]]

=====Monarchs Under the Mountain=====
* [[By Hoof and Horn]]
*[[Misgivings]]

=====The Enduring War=====
*[[Troygan the Enchanger]]
*[[Threshing Machine]]
*[[Mark of the Times]]
*[[The Clockwork Tower]]
*[[Pursuit Of Knowledge]]

== Checking Event Failures ==

If an event does not seem to ever occur even though you think it should, you can enable [[Testing|dev mode]] and the Pick Events cheat, then scroll down in the list of events to see why a particular event failed.

[[File:ArriveAtHostileSiteFailedEvent.PNG]]

In that case, no eligible hero had a (required) bookish score of at least 80.

A few other reasons why an event might fail or not occur are:
* Wrong [[Event#Event types|event type]]. The event you're trying to trigger is an 'Arrive at hostile site' type, but your party is 'Wilderness scouting.' (You wouldn't find a hostile site event in the wilderness scouting Pick Events list.)
* Event only occurs once per campaign. (The event already happened in the current campaign. Pick Events will show that reason for the event failure.)
* Eligible for theme failure. The event won't happen if you already have a hero with that theme in your company (or your existing theme conflicts with your desired theme). (You can wait to recruit another hero with that theme, until your current hero gets the desired theme.)

Mark of the Times

2022-02-03T07:08:27Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = Mark of the Times
| image = Markofthetimes1.png
| author = Shae Rossi & Douglas Austin
| type = Arrive at hostile site
}}

The party comes across a mill that has been ransacked by the Morthagi.

== Choices ==

''1. <q>I hate to say it. You should go. Now. While you can.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Battle the Morthagi. Afterwards, gain '''+1d2+1 hides OR fabrics''' and '''+1d2+1 ingots OR heartwoods'''.
|}
''2. <q>Keep your home. Rebuild. You're under our protection now.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Battle the Morthagi. Afterwards, gain '''+1d2 legacy points''' and remove one Morthagi calamity card.
|}

== Trivia ==
Before patch 0.13+109 Darrel Trace this event was named '''Clockwork Thieves'''.

This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:Markofthetimes2.png
</gallery>

[[Category:Event]]

Threshing Machine

2022-02-03T07:07:55Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = Threshing Machine
| image = Threshingmachine1.png
| author = Heather Albano
| type = Arrive at hostile site
}}

Before attacking a [[Morthagi]] site, a hero thinks about harvest time and the threshing machine they saw as a kid.

== Choices ==

''1. <q>The thing they called the "mouth" of the separator? It did look like a mouth. A huge, hungry mouth. With teeth.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Start the battle with {{Courage}}.
|}
''2. <q>....it was a miracle. Think what we could do if we had more machines like that. Think how wonderful the world could be.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Remove a Morthagi calamity card from the deck, and battle begins as normal.
|}

== Trivia ==
This event is triggered by a tile infested by [[Morthagi]].

This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
</gallery>

[[Category:Event]]

Threshing Machine

2022-02-03T07:07:39Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = Threshing Machine
| image = Threshingmachine1.png
| author = Heather Albano
| type = Arrive at hostile site
}}

Before attacking a [[Morthagi]] site, a hero thinks about harvest time and the threshing machine they saw as a kid.

== Choices ==

''1. <q>The thing they called the "mouth" of the separator? It did look like a mouth. A huge, hungry mouth. With teeth.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Start the battle with {{Courage}}.
|}
''2. <q>....it was a miracle. Think what we could do if we had more machines like that. Think how wonderful the world could be.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Remove a Morthagi calamity card from the deck, and battle begins as normal.
|}

== Trivia ==
This event is triggered by a tile infested by [[Morthagi]].
This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
</gallery>

[[Category:Event]]

The Clockwork Tower

2022-02-03T07:07:13Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = The Clockwork Tower
| image = ClockworkTower.png
| author = Shae Rossi
| type = Wilderness scouting
}}

The Heroes find a village full of people and [[Morthagi]] living peacefully side by side.

== Choices ==

''1. <q>This is wrong. We have to free them.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Begin battle with the Morthagi.
|}
''2. <q>They chose this. It's not up to us to interfere.</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| The party leaves without a fight. No consequences.
|}
''3. <q>We'll come back later and destroy it!</q>''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| '''Success''': The tower is deactivated. '''Failure''': Begin battle with the Morthagi. Start the battle with {{Dismay}}.
|}

== Trivia ==
This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:Theclockworktower1.PNG
</gallery>

[[Category:Event]]

Troygan the Enchanger

2022-02-03T07:05:27Z

Mindtheblob: /* Trivia */

{{Infobox event
| event = Troygan the Enchanger
| image = Troygan3.png
| author = Douglas Austin
| type = Arrive at hostile site
}}

A two-part event in a tower occupied by [[Morthagi]].

== Choices ==

''1. "Could this be the fabled Mortificial Enchanger?"''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Battle some [[Morthagi]].
|}
''2. "This... is... a... skelebox"''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Battle some [[Morthagi]].
|}

After the battle:

''1. "I am curious and I couldn't forgive myself if I threw this chance away on account of fear."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| The maimed hero is out of play for 60 days, after which their maimed limb receives [[Mortificial Enhancements]].
|}
''2. "I am curious but I can't let that open the door to evil."''
:{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| Outcome
|-
| Turn down the offer.
|}

== Trivia ==
The person getting the [[Mortificial Enhancements]] cannot be the same person with the bookish personality.

This event is not possible to trigger in [[The Enduring War]] campaign.

== Images ==

<gallery mode=packed heights=150px>
File:troygan1.PNG
File:Troygan2.PNG
</gallery>

{{Targets2
| page = Targets encounter heroesArriveAtSite troyganTheEnchanger part1
}}
__NOTOC__
[[Category:Event]]

Targets and Scoring Guide

2022-02-02T20:50:35Z

Mindtheblob: /* Conflicting Themes */

This is an overview to help understand an [[event]]'s targets requirements, and why the event might occur (or fail). For more technical details, see [[Effects#Targets|Effects]] or [[Story Inputs and Outputs]].

==A Note on Role Names==
''A frequent source of confusion in understanding the wiki's event targeting arises when '''role names''' are confused with '''hero stats or aspects''':

[[File:RoleTutorial1.png|650px]]

[[File:RoleTutorial2.png|650px]]

''A role name is just a name.''

==Company and Chapter Targeting==

The most common requirement for the default '''company''' target is a '''chapter threshold.'''

Chapter is stored as an aspect called chapterNumber in company. All aspects have value.

The value for chapter is equal to the chapter of the game.

=====Examples of Company and Chapter Targeting=====
:'''Target (role): company'''
::'''Aspects:''' chapterNumber >= 2
::''This [[aspect]] threshold requires the aspect called chapterNumber to be greater than or equal to 2.''
::''An event with this requirement will only trigger in Chapter 2 or above.''

:'''Target (role): company'''
::'''Forbidden Aspects:''' seenEvent|encounter_heroesArriveAtSite_answertoAusterity
::''This forbidden aspect list forbids the aspect seenEvent|encounter_heroesArriveAtSite_answertoAusterity. The seenEvent aspects are gained upon encountering events.''
::''This particular aspect refers to the event [[Answer to Austerity]].
::''If the company has seen the event, the '''company''' target role can not be matched, and the event will not be able to trigger.''

==Overland Tile Biome and Site Targeting==

====Biome Targeting====

Events may have requirements for the overland [[tile]]. The most common requirement for an overland tile is a certain type of [[biome]]. By default, these are targeted in a required role called '''overlandTile''', but there can be exceptions.

=====Example of Biome Targeting=====
:'''Target (role): overlandTile'''
::'''Biome:''' swamp, forestDeciduous, forestConiferous
::''An event with this target role will require the overland tile to be a swamp, broadleaf forest, or pine forest.''

====Site targeting====

Sites are towns and [[station]]s on the [[overland map]] tiles. By default, a role named '''site''' is targeted in [[hostile site]] encounters.

'''Site targeting''' can have additional requirements, such as the type of station, and other aspects of the site.

Note that events can also target sites that are not on the tile the current party is on (see example '''B''' below).

=====Examples of Site Targeting=====
:'''A) Target (role): site'''
::'''Station:''' tannery
::''An event with this target role will require the event to take place on a site with a tannery station.''

:'''B) Target (role): site'''
::'''Aspects:''' town, VISIBLE_TILE
::''This is an example from the [[Star Dance]] event. The event is a wilderness scouting event, where, by default, site roles (these are called injected roles, because they are injected into the event) are not targeted.''
::''In this example, the role '''site''' targets one random town that is on a tile that is visible to the player. In this specific example, the '''site''' target role is an event mechanic used in the event's outcomes.''
::''For the event to be able to trigger, the company must have at least one town visible on the overland map.''

==Enemy and Dead Enemy Targeting==

Similarly to biomes and sites, events can also target specific factions of enemies. Mission victory or mission defeat events may target defeated enemy units from a target role of '''deadFoe'''.

=====Examples of Enemy Targeting=====
:'''Target (role): foes'''
::'''Aspects:''' drauven
::''An event with this target role requires the enemy at a hostile site to be drauven.''

:'''Target (role): deadFoe'''
::'''Aspects:''' drauven_skysinger
::''A mission victory/defeat event with this target role requires an enemy with the drauven_skysinger aspect (Deeven) to have been defeated in the previous mission.''

==Hero Targeting==
Almost all events require heroes to be targeted for roles. Furthermore, many events require heroes to match roles with specific criteria.
There are three main types of roles to consider:
#'''Required Roles'''
#'''Optional Roles'''
#'''Forbidden Roles'''
'''Required roles''' are mandatory. If no hero matches a particular required role, the event targeting will fail, and the event will not be in the pool of possible events for the encounter. '''Optional roles''' are not mandatory. An event may trigger even if an '''optional role''' is not matched. '''Forbidden roles''' are forbidden. If a forbidden role is matched to a hero, the event targeting will fail, and the event will not be in the pool of possible events for the encounter.

Note, to make matters more complicated, '''required roles''' may have optional targeting preferences, and '''optional roles''' may have required score thresholds.

This guide attempts to show both (required) and (optional) roles in the examples. They do, however, operate on the exact same principles. [[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Case Studies]] in the final section showcase some interesting examples.

For current purposes, the sub-sections in this section will briefly explain '''hero scoring''', '''aspects''', '''tests''', and '''theme eligibility'''.

====Hero Scoring====

'''Required''' and '''optional roles''' are the most common roles to come across in hero targeting. They typically choose their matches by the hero scoring the highest score of a '''score function'''.

''Note! There do exist other choosing methods for targets (for example, '''one random''', but for the sake of clarity, this guide will discuss the '''by score''' method as default).''

A '''score function''' is a function of criteria and their values for the role. These score functions may include, for example, '''[[personality]]''' or '''experience stats''', specific '''[[relationship]]s''' between heroes, and aspects such as '''hooks''' or '''items'''.

=====Examples of Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. For a hero to match this role, they must have a LEADER stat of 50 or above.''

:'''Role: hero''' (optional)
::'''Score Function:''' LEADER+HOTHEAD >= 100
::''This score function targets the sum of the LEADER and HOTHEAD stats of a hero, and has a score threshold of 100 or above. For a hero to match this role, the sum of their LEADER and HOTHEAD stats must be 100 or above.''
::''Note that this role is (optional). Even if no hero is matched to this role, the event can still trigger.''
::''Why would this role be optional? The event might use it for specific dialogue, or to enable extra choices, for example.''

:'''Role: hero''' (required)
::'''Score Function:''' ((30*hunter) + (30*hook_weird)) + LEADER
::''This slightly more complicated score function uses both aspects and stats. All aspects have value. The most common aspects in hero targeting include class aspects and hook aspects.''
::''For heroes with the hunter aspect (hunter class) the value of the aspect is 1, for others, the value is 0. For heroes with the hook weird, the value of the hook_weird aspect is 1.''
::''For example, for a hunter hero who does not have the WEIRD hook, the scoring would read ((30*1) + (30*0)) + LEADER''
::''The score function lacks a score threshold. This role will target a hero with the highest score of the sum of the aspect parentheses and the LEADER stat. That is to say, the hunter and hook aspects are not required, but will add to the score.''
::''Note! There are aspects that may have more value than 1.''

====Hero Aspects====

Another common requirement in hero targeting is the listing of '''Required''' or '''Forbidden Aspects'''. Listed '''Aspects''' are required for a hero to match the target role, whereas '''Forbidden Aspects''' make a hero with those [[aspect]]s ineligible for the role.

A less common variant of '''Aspects''' is '''Aspects (One of)'''. This variant requires the target to have at least one of the listed aspects.

Continuing with our previous example, lets add a '''Required''' and '''Forbidden Aspect''' to the role.

=====Example of Aspects and Score Functions=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Forbidden Aspects:''' mystic
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required aspect called theme_crow (the aspect for the crow transformation). The Forbidden Aspects lists an aspect called mystic (the hero class). Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and not be a mystic.''

::''Note! A similar effect to the Forbidden Aspects example above could be achieved with a Aspects (One of): hunter, warrior.''

====Hero Tests====

A less common requirement is '''Tests'''. They are primarily used, when two stats do not want to be mixed in score functions.

=====Example of Test, Aspect, and Score Function=====
:'''Role: hero''' (optional)
::'''Score Function:''' LEADER >= 50
::'''Aspects:''' theme_crow
::'''Test:''' AGE <= 35
::''This score function only targets the LEADER stat, and has a score threshold of 50 or above. The Aspects lists a required Aspect called theme_crow (the aspect for the crow transformation). The Test requires the hero's age to be less than or equal to 35. Now, for a hero to match this role, they must have a LEADER stat of 50 or above, have the crow transformation, and be 35 years of age or younger.''
::''Note that this '''hero''' role is now (optional), an event can trigger even if this role is not matched to a hero.

====Theme Eligibility====

'''Theme Eligibility''' is ubiquitous in almost any event where a [[theme]] (transformation, pet) is given. '''Theme eligibility''' is quirky. The Content Editor blurb states:

''Must be able to get the given theme (doesn't already have the theme, no conflicting themes, has an available slot for one of the theme pieces to go in, and no other heroes already have that theme).''

This means there are quite a few checks to pass when an '''Eligible for Theme''' is present in hero targeting.

'''Important!''' No member of the company may have the theme that is tested for in '''Eligible for Theme'''.

=====Conflicting Themes=====
{{Main|Theme conflicts guide}}
Perhaps the trickiest feature is that there is no way of telling which [[theme]]s conflict with each other. For example, themes may conflict because of defined [[Theme conflicts guide#Detailed Discussion: Forbid Combine With|forbidden combinations]] in the game files. Or themes may be in practical conflict because events target the same theme slots. See the [[Theme conflicts guide|theme conflicts guide]] for further information.

Unlike [[aspect]]s, [[stat]]s, and [[relationship]]s, '''theme eligibility''' does not appear in '''score functions'''. It does appear along side of '''score functions''', similar to lists of aspects discussed above.

=====Example of Hero Theme Eligibility=====

:'''Role: target''' (required)
::'''Eligible for Theme:''' bear
::'''Eligible for Theme Piece:''' tattoo
::''For a hero to match this target role, no hero in the company must have the bear theme. The hero must not have conflicting themes with the bear theme (wolf), the hero must be eligible for a head slot theme piece.''

====Forbidden Roles====

'''Forbidden roles''' are far less common. If a '''forbidden role''' is matched, the event will not be in the pool of eligible encounter events triggered.

=====Example of a Forbidden Role=====
:'''Role: hero''' (required)
:'''Forbidden Role: hero2'''
:''This event would fail to trigger if the '''hero2''' was matched, in this case, we might assume the event is only available to a one hero party.''

====Role Names====

'''Important!''' When reading event targets, the name of a '''role''' is just a '''name'''. How the role is defined with '''scoring''', '''aspects''', '''tests''', and '''theme eligibility''', introduced above, determines if a hero can be matched to the role. Typical '''role names''' for heroes used in event targets include '''hero''', '''hero2''', personality names ('''goofball''', '''healer''', etc.), '''hook''', '''rival''', '''lover''', '''volunteer''', and so forth.

With this in mind, a role named '''rival''' may well only require a certain ''personality threshold'', or alternatively, it may not have ''any specific requirements at all''. Consider the following quiz:

=====Quiz: Roles Named Rival=====
:'''Role name: hero''' (required)
:''Let's first assume this role named '''hero''' will match any hero.''
::'''Question:''' ''Which One of the Roles Named Rival Requires a Rival?''
:::'''A) Role name: rival''' (required)
::::'''Aspects:''' mystic
:::'''B) Role name: rival''' (required)
::::'''Score Function:''' GOOFBALL >= 80
:::'''C) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero
:::'''D) Role name: rival''' (required)
::::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''Answer:''' '''D.''' The '''score function''' in '''C.''' does not specify a '''score threshold.''' This means the role will prefer to target a rival of '''hero''', but it is not mandatory.

====Special Cases of Hero Targeting====

In straightforward encounter events, a hero is selected for a single role from the party that triggered the event.

However, there are various special cases, where heroes may be targeted for more than one role, as well as cases, where heroes may be targeted from outside the party.

These special cases are typically used for selecting specific heroes for event choice panels, dialogue, and enabling special choices for heroes with specific requirements. An example of the latter, many transformations have unique choices in certain events, and these are targeted with an optional role, that may well target a hero already matched to another role.

'''Important!''' This may result in confusion when interpreting hero targeting. There may be more '''required roles''', than there are '''required heroes'''.

Is it possible for an event to '''require more heroes''' than there are '''required roles'''? Yes. Circumstantially. ([[Targets_and_Scoring_Guide#Case_Study:_The_Wolf_Price|Here is a Case Study]])

Why is this? There are simply more mechanics involved to hero targeting. At the time of writing, the Wiki event targets do not account for definitions such as '''fromRoles''', '''notAlreadyMatchedAs''', and '''alreadyMatchedAs''' in Event Targeting, or the method by which a role chooses its target.

The '''fromRoles''' definition defines from which roles the role is drawn. The '''MatchedAs''' definitions are used to make sure that the same entity is either matched or not matched in another role.

These definitions can currently only be found in the Content Editor. Below, an example is given of what a special case might look like:

=====Example of a Special Case=====
:'''Role: hero''' (required)
::'''Score Function:''' LEADER >= 50
::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score Function:''' RIVAL_WITH.hero >= 1
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero'''

:'''Role: hero2''' (required)
::'''Forbidden Aspects:''' mystic
::'''fromRoles: party'''
::'''notAlreadyMatchedAs: hero, rival'''

:'''Role: greedy''' (required)
::'''Score Function:''' max(GREEDY, SNARK)
::'''fromRoles: hero, hero2'''

::This example shows four required roles, but, in fact, only requires three heroes. As we have learned, '''hero''' requires a LEADER stat threshold, '''rival''' is required to be a rival of '''hero''', and '''hero2''' is required to not be a mystic. Unlike the previous three roles, the '''greedy''' role is drawn '''fromRoles: hero, hero2''' and does not have a '''notAlreadyMatchedAs''' definition. The score function in '''greedy''' role will target the hero with the highest GREEDY or SNARK stat, but only from the roles '''hero''' and '''hero2'''.

===Further Targeting Examples===

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| This section will further examine hero targeting by looking at examples.
|-
|
====Scoring Thresholds vs. No Scoring Thresholds====

First, let's consider the difference between a '''score function''' with a '''threshold''', and a '''score function''' '''without a threshold:'''

:'''Example:'''
:'''A) Role: bookish''' (optional)
::'''Score Function:''' BOOKISH >= 80

:'''B) Role: bookish''' (required)
::'''Score Function:''' BOOKISH

Lets assume these roles choose a target '''by score.''' Example '''A)''' requires a BOOKISH score of greater than or equal to 80, and will target the hero with the highest BOOKISH stat. Example '''B)''' will target the hero with the highest BOOKISH stat.

Note that the role in example '''A''' is (optional). This means that the event can trigger even if no hero is matched to it.

====The Max Scoring Function====

The '''max(x,y,z)''' '''function''' is the most common '''function''' (see [[Expressions]]) used in hero targeting '''score functions'''. It returns the highest value of a set of parameters.

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY)

Here, the '''max()''' function will target the hero with the highest CHARISMA or TENACITY stat.

The '''max()''' function can be used with thresholds:

:'''Example:'''
:'''A) Role: volunteer''' (required)
::'''Score Function:''' max(CHARISMA, TENACITY) >= 20

Here, the '''max()''' function requires a hero with CHARISMA or TENACITY stat greater than or equal to 20, and will target the hero with the highest CHARISMA or TENACITY stat.

====Complex Scoring Functions and Thresholds====

So far we've entertained fairly simple '''score functions'''. But hero targeting may well look like the example below:

:'''Example:'''
:'''Role: statPotency''' (required)
::'''Score Function:''' (1000*mystic)+((10*max(BOOKISH,POET,SNARK))+POTENCY) >= 1000

This is an example from the [[Entanglement]] event. Here, the role requires a hero to pass a score threshold of 1000. The '''score function''' uses STATS as well as an ASPECT (mystic).

All aspects have value. For mystic aspect, the value is 1.

The parentheses on the left are then (1000*1) or (1000*0) depending on whether the hero is of the mystic class. In practice, this target will ''almost'' exclusively target a hero of the mystic class with the highest stat in BOOKISH, POET, or SNARK (and throw in a little potency for marginal cases).

Note, it is still ''theoretically'' possible for the role to target a hero who is not a mystic but has a very high (100) BOOKISH, POET, or SNARK stat, or a hero with a POET (99) stat and POTENCY (10) stat, for example. For the latter case, the parentheses on the right would read ''(10*99+10) = 1000''.

====Relationship Scoring====

One of the most common hero targeting functions are relationship scoring functions. Like aspects, '''relationships have value'''.

For '''relationships''', the value is between 1 and 5 (a value of 1 being a '''level one''' ''one heart (lover)/lightning (rival)/pawn (friend)'' relationship and 5 being a fully maxed relationship.

Relationship scoring operates on the same principles already discussed: They may be required (have '''thresholds''') or preferred (lack '''thresholds''').

'''Important!''' In '''relationship scoring''', pay attention to the '''.rolename''' suffix in the function. This determines the previously targeted role that is the target of the relationship.

:'''Examples:'''
:'''A) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 1

Here, any LOVER relationship is required with the role '''hero'''.

:'''B) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero >= 5

Here, a maxed LOVER relationship is required with the role '''hero'''.

:'''C) Role: lover''' (required)
::'''Score Function:''' LOVER_WITH.hero

Here, a LOVER relationship is preferred, but not mandatory, with '''hero''' because the '''score threshold''' is missing.

:'''D) Role: hero2''' (required)
::'''Score Function:''' SHIP_WITH.hero >= 3

Here, any RELATIONSHIP (Friend, Rival, Lover) greater than of equal to level three is required.

:'''E) Role: hero2''' (required)
::'''Score Function:''' PARENT_OF.hero >= 1

Here, '''hero2''' must be a parent of '''hero'''.

====Case Study: The Wolf Price====
''Now let's look at an interesting case study of hero targeting for the wilderness scouting [[The Wolf Price]].''

''It is one of the rare examples where circumstances arise, where more heroes may be required than there are required roles.''

''To understand why, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions are added.

:'''Role: hook''' (optional)
::'''Score Function:''' hook_Wildheart + hook_Mysterious >= 1
::'''Eligible for Theme:''' wolf
:::'''fromRoles:''' party

:'''Role: volunteer''' (required)
::'''Score Function:''' ((30*hunter)+(10*warrior))+LONER
::'''Eligible for Theme:''' wolf
::'''Eligible for Theme Piece:''' head
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook

:'''Role: coward''' (required)
::'''Score Function:''' COWARD
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' hook, volunteer

::''The '''hook''' role is an (optional) role, for a hero to match the role, the sum of the score of their hook_Wildheart (Wildheart hook) and hook_Mysterious (Mysterious hook) aspects must be greater than or equal to 1. Because the role is optional, the event can trigger without a hero being matched to it, but more on that later.
::''The '''hook''' role must be eligible for the theme wolf. No other hero in the company may have the wolf transformation. The hero may not have conflicting themes with the theme [[Wolftouched]]. A full list of themes that conflict with [[Wolftouched]] in unmodded games: ({{Theme conflicts|wolf}}).
::''The role '''volunteer''' is the first (required) role. The '''score function''' lacks a '''score threshold''' so the function will choose the highest scoring hero for the function. Note that for a hero with the class aspects hunter or warrior, a bonus of (30*1) or (10*1) is added to the sum with the LONER stat, respectively.
::''A hero matched to the role of '''volunteer''' must be eligible for the wolf theme (discussed above in the '''hook''' role). The hero matched to the '''volunteer''' role must also have a free head theme slot.
::''The role '''coward''' matches a hero with the highest COWARD stat, who is not already matched as the roles '''hook''', or '''volunteer'''.
::''Why is this event worthy of a case study? Because of the ordering of the roles and the '''notAlreadyMatchedAs''' definitions.
::''The (optional) '''hook''' role is targeted first. If a hero is matched to this role, it means that the next two roles must be separate heroes. This is because the '''notAlreadyMatchedAs''' definitions for the '''volunteer''' and '''coward''' roles both define the '''hook''' role as an impossible match (a hero can't be matched to both a '''hook''' and '''coward''' role, for example.'')
::''This means that even though there are only two required roles ('''volunteer''' and '''coward'''). There are instances where this event will require three heroes, if one of the heroes matches as the '''hook''' role.
::''Confused? Let's consider a starting party of three heroes with the following hooks:''
::''Hero John ('''mysterious''', lucky, distant), Hero Jane (brash, integrity, lucky), Hero Jin (brash, lucky, distant)
::''Now, if we send Hero Jane and Hero Jin to scout a wilderness tile, they will be able to trigger the event, because neither of them can match the '''hook''' role.''
::''But if we send John and Jin, John will match the '''hook''' role, because they have the hook_Mysterious aspect. The event will then not be able to find a match for the (required) '''coward''' role, and will not be able to trigger.''
::''If we send the whole party, they will be able to trigger the event.''
::''If we send John and Jin together, but John has the '''bear''' or '''skeleton''' theme, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' wolf, because of the conflicting theme.)''
::''Similarly, if we send John and Jin together, but John has the full celestial theme, for example, they will be able to trigger the event, because John will not match the '''hook''' role (they would not be '''Eligible for Theme:''' because they are not eligible for a theme piece of the theme.) Note! John doesn't need a tail slot theme filled, even though a tail for the wolf theme exists.''

====Case Study: Drifters====
::''Putting it all together. Let's look at a complete case of hero targeting for the [[Drifters]] event.''

::For sake of clarity, '''fromRoles''' and '''notAlreadyMatchedAs''' definitions, briefly discussed in the previous section, are added.

:'''Role: coward''' (required)
::'''Score:''' max(COWARD, BOOKISH, LONER) >= 80
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''

:'''Role: rival''' (required)
::'''Score:''' RIVAL_WITH.coward >= 1
::'''Eligible for Theme:''' green
::'''Eligible for Theme Piece:''' tattoo
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward

:'''Role: leader''' (required)
::'''Score:''' LEADER
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' coward , rival

:'''Role: hero''' (required)
:::'''fromRoles: party'''
:::'''notAlreadyMatchedAs:''' leader

The '''coward''' role requires a hero with one of the stats of COWARD, BOOKISH, or LONER to be greater than or equal to 80. No one in the company may have the theme green ([[Sylvan]]). The hero must not have conflicting themes. A full list of themes that conflict with [[Sylvan]] in an unmodded game: ({{Theme conflicts|sylvan}}). The hero must have an open head theme slot.

The requirements for the '''rival''' role are exactly the same, but instead of a STAT requirement, the '''rival''' role requires a hero that is the rival of the '''coward''' role (notice the '''score threshold''').

The '''leader''' role prefers a hero with a high LEADER stat (notice the lack of a '''score threshold''').

The '''hero''' role has no requirements. Notice that the '''notAlreadyMatchedAs''' definition only defines the '''leader''' role. This means that the '''hero''' role may match with the same hero that is matched in the '''coward''' or '''rival''' roles, meaning that the event can actually be triggered with only three heroes.

====Case Study: The Heirloom Spring====
''Finally, let's look at a complete targeting for the wilderness scouting event [[The Heirloom Spring]]:

:'''Role: overlandTile'''
::'''Biome:''' swamp

:'''Role: romantic''' (required)
::'''Score:''' ROMANTIC
::'''Eligible for Theme:''' petDuck
::'''Eligible for Theme Piece:''' duck
:::'''fromRoles:''' party

:'''Role: ship''' (required)
::'''Score:''' SHIP_WITH.romantic
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic

:'''Role: volunteer''' (optional)
:::'''fromRoles:''' party
:::'''notAlreadyMatchedAs:''' romantic, ship

:'''Role: lover''' (optional)
::'''Score:''' LOVER_WITH.romantic >= 1

:'''Role: rival''' (optional)
::'''Score:''' RIVAL_WITH.romantic >= 1

::''First, the '''overlandTile''' role requires the biome of the tile to be a swamp.''
::''The '''romantic''' role has a '''score function''' without a '''score threshold'''. This will target the hero with the highest score in the ROMANTIC stat.''
::''The '''romantic''' role must be eligible for the theme petDuck (duck). No other member in the company may have a pet duck. The hero must not have another pet in the pet theme slot (ground pets).''
::''Note! If the highest scoring hero in the ROMANTIC stat '''score function''' has a pet, the event can still target a hero with the second/third/etc highest ROMANTIC stat and a free pet theme slot.''
::''The '''ship''' role is a required role. The SHIP_WITH.romantic '''score function''' has no '''score threshold''', so it will target the hero with the highest level relationship with the '''romantic''' role in the party. If there are no relationships, the role will still match a hero, because there is no '''score threshold'''.
::''The '''volunteer''' is an optional role drawn from the party. The event will trigger even if the role is not matched to a hero. This means the minimum number of heroes for the event is 2.''
::''The '''lover''' and '''rival''' roles are optional roles with a '''score function''' and a '''score threshold'''. Note that these roles do not draw '''fromRoles:''' party. This means they will target any hero in the company who is a lover or rival of the '''romantic''' role. In this specific example, these two optional roles are only used in dialogue of the event, so comic panels will know the names of the lover and rival of the hero matched in the '''romantic''' role.''
|}

== Checking Event Failures ==

If an event does not seem to ever occur even though you think it should, you can enable [[Testing|dev mode]] and the Pick Events cheat, then scroll down in the list of events to see why a particular event failed.

[[File:ArriveAtHostileSiteFailedEvent.PNG]]

In that case, no eligible hero had a (required) bookish score of at least 80.

A few other reasons why an event might fail or not occur are:
* Wrong [[Event#Event types|event type]]. The event you're trying to trigger is an 'Arrive at hostile site' type, but your party is 'Wilderness scouting.' (You wouldn't find a hostile site event in the wilderness scouting Pick Events list.)
* Event only occurs once per campaign. (The event already happened in the current campaign. Pick Events will show that reason for the event failure.)
* Eligible for theme failure. The event won't happen if you already have a hero with that theme in your company (or your existing theme conflicts with your desired theme). (You can wait to recruit another hero with that theme, until your current hero gets the desired theme.)

Theme conflicts guide

2022-02-02T20:35:37Z

Mindtheblob: /* List of Theme Conflicts */

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussion on the different types of conflicts, and a handful of [[Theme conflicts guide#Rules of Thumb|tips]].

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked from a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or [[Testing|cheats]], a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Further Reading: A Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:48:27Z

Mindtheblob: /* Theme Conflicts */

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussion on the different types of conflicts, and a handful of [[Theme conflicts guide#Rules of Thumb|tips]].

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or [[Testing|cheats]], a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Further Reading: A Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:44:20Z

Mindtheblob: /* Detailed Table of Theme Conflicts */

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussion on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or [[Testing|cheats]], a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Further Reading: A Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:42:29Z

Mindtheblob: /* Detailed Discussion: Eligible for Theme Piece */

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussion on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or [[Testing|cheats]], a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Detailed Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:33:31Z

Mindtheblob: /* Theme Conflicts */

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussion on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or cheats, a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Detailed Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:32:33Z

Mindtheblob:

This guide is designed to assist the player in understanding [[theme]] eligibility and conflicts.

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussions on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or cheats, a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Detailed Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

Theme conflicts guide

2022-02-02T19:29:46Z

Mindtheblob: Created page with "==Theme Conflicts== 650px 650px ''If only there was a guide to tell them..'' Not all themes are compatible with o..."

==Theme Conflicts==
[[File:ConflictIntro1.png|650px]]
[[File:ConflictIntro2.png|650px]]

''If only there was a guide to tell them..''

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

Forbidden theme combinations may be defined in the theme game files. Event targets may impose limitations by targeting the same [[Theme#theme slot|theme slots]].

Some theme requirements may impose even further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussions on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using [[Testing|cheats]] or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]].

'''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith":''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith:''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or cheats, a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden theme aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Stormtouched:'''
:: The [[stormtouched]] theme is unique in that it grants the option for a theme piece occupying the head, left arm, or left leg theme slot.
:: If a head or left arm is chosen, the theme will be in practical conflict with many other themes.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.
* If you wish to avoid further conflicts, the safest theme piece to start with [[stormtouched]] is the leg.

====Detailed Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]

[[Category:Theme]]

2022-02-02T18:42:21Z

Mindtheblob:

2022-02-02T09:51:05Z

Mindtheblob:

==Theme Conflicts==

Not all [[theme]]s are compatible with one another. There are a number of ways themes can be in conflict.

For example, forbidden combinations may be defined in the theme game files. Event targets may also impose further limitations by targeting the same [[Theme#theme slot|theme slots]] (head, torso, arms, legs, skin, wings, tail).

Some theme requirements may impose further restrictions. These are discussed in detail in further sections.

This article contains an exhaustive table of theme conflicts. The final sections include more detailed discussions on the different types of conflicts.

==== List of Theme Conflicts ====

This section displays an exhaustive list of all theme conflicts the player might encounter without using cheats or mods.

'''Two scenarios have been taken into consideration:'''

* What themes block a hero from receiving a given theme ('''Theme is Blocked by''').
* What themes are blocked by a hero who has a given theme ('''Theme Blocks''').

{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| '''List of Theme Conflicts'''
|-
|

{| class = "wikitable"
! Theme !! Theme is Blocked by !! Theme Blocks
|-
|[[Beartouched]]||{{Theme conflicts|bear}}||{{theme conflicts|bear|blocks}}
|-
|[[Botanical]]||{{Theme conflicts|vine}}||{{theme conflicts|vine|blocks}}
|-
|[[Celestial]]||{{Theme conflicts|star}}||{{theme conflicts|star|blocks}}
|-
|[[Child of the Hills]]||{{Theme conflicts|foothill}}||{{theme conflicts|foothill|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crowtouched]]||{{Theme conflicts|crow}}||{{theme conflicts|crow|blocks}}
|-
|[[Crystalline]]||{{Theme conflicts|gem}}||{{theme conflicts|gem|blocks}}
|-
|[[Deepist Spy]]||{{Theme conflicts|deepistmole}}||{{theme conflicts|deepistmole|blocks}}
|-
|[[Drauven Wings]]||{{Theme conflicts|drauvenwings}}||{{theme conflicts|drauvenwings|blocks}}
|-
|[[Elmsoul]]||{{Theme conflicts|tree}}||{{theme conflicts|tree|blocks}}
|-
|[[Flamesoul]]||{{Theme conflicts|fire}}||{{theme conflicts|fire|blocks}}
|-
|[[Foxish]]||{{Theme conflicts|fox}}||{{theme conflicts|fox|blocks}}
|-
|[[Frogtouched]]||{{Theme conflicts|frog}}||{{theme conflicts|frog|blocks}}
|-
|[[Frost]]||{{Theme conflicts|frost}}||{{theme conflicts|frost|blocks}}
|-
|[[Gorgonoid]]||{{Theme conflicts|gorgon}}||{{theme conflicts|gorgon|blocks}}
|-
|[[Hawksoul]]||{{Theme conflicts|hawk}}||{{theme conflicts|hawk|blocks}}
|-
|[[Mark of the Horn]]||{{Theme conflicts|deepist}}||{{theme conflicts|deepist|blocks}}
|-
|[[Mortificial Enhancements]]||{{Theme conflicts|morthagi}}||{{theme conflicts|morthagi|blocks}}
|-
|[[Mothly]]||{{Theme conflicts|mothwings}}||{{theme conflicts|mothwings|blocks}}
|-
|[[Petrified]]||{{Theme conflicts|gorgonstone}}||{{theme conflicts|gorgonstone|blocks}}
|-
|[[Ratlike]]||{{Theme conflicts|rat}}||{{theme conflicts|rat|blocks}}
|-
|[[Scorpioid]]||{{Theme conflicts|scorpion}}||{{theme conflicts|scorpion|blocks}}
|-
|[[Shadow]]||{{Theme conflicts|shadow}}||{{theme conflicts|shadow|blocks}}
|-
|[[Skeletal]]||{{Theme conflicts|skeleton}}||{{theme conflicts|skeleton|blocks}}
|-
|[[Skunkish]]||{{Theme conflicts|skunk}}||{{theme conflicts|skunk|blocks}}
|-
|[[Spell Touched]]||{{Theme conflicts|spelltouched}}||{{theme conflicts|spelltouched|blocks}}
|-
|[[Stormtouched]]||{{Theme conflicts|storm}}||{{theme conflicts|storm|blocks}}
|-
|[[Sylvan]]||{{Theme conflicts|green}}||{{theme conflicts|green|blocks}}
|-
|[[Teeny Wings]]||{{Theme conflicts|tinywings}}||{{theme conflicts|tinywings|blocks}}
|-
|[[Vulture Acolyte]]||{{Theme conflicts|vultureacolyte}}||{{theme conflicts|vultureacolyte|blocks}}
|-
|[[Wolftouched]]||{{Theme conflicts|wolf}}||{{theme conflicts|wolf|blocks}}
|-
|}
|}

====Detailed Discussion: Forbid Combine With====

Most events that grant themes have an '''Eligible for Theme:''' definition in the [[Targets and Scoring Guide#Theme Eligibility|event targeting]]. '''This target requirement makes sure that:'''

*No member of the company may have the same theme.
*The hero must not have '''conflicting themes'''.
*The hero must have an empty slot for a theme piece.

'''Conflicting themes''' are defined in the theme '''.json''' files with a '''"forbidCombineWith": []''' definition.

'''Important!''' A conflict between two themes occurs when the themes are defined with a '''forbidCombineWith: []''' in '''either''' of the theme '''.json''' files.

::'''Example:'''
::: '''gem:''' "forbidCombineWith": ["bear", "wolf", "tree", "fire", "skeleton"]
:::'''tree:''' "forbidCombineWith": ["bear", "wolf", "crow", "fire", "skeleton"]
:::''This is an example from the [[crystalline]] and [[elmsoul]] theme files.''
:::''Note that only the '''gem''' defines '''tree''' as a forbidden combination.''
:::''Nevertheless, a hero with the [[elmsoul]] theme is not eligible for the [[Heart of Stone|event]] that grants the [[crystalline]] theme.''
:::''Similarly, a hero with the [[crystalline]] theme is not eligible for the [[Splinter|event]] that grants the [[elmsoul]] theme.''

'''Note for modders!''' The '''"forbidCombineWith":''' definition also affects the '''ApplyTheme:''' outcome, which will not take effect when there is a '''forbidCombineWith''' conflict.

====Detailed Discussion: Eligible for Theme Piece====

Many event targets impose practical conflicts with [[theme]]s by targeting the same '''theme slot'''.

Events define an '''Eligible for Theme Piece:''' requirement for a role. Following, the event outcomes apply the theme piece to the hero that matched the role. Most theme pieces take up a '''theme slot'''.

'''Examples of Theme Slots and Pieces:'''
*'''Head:''' hair stars, head, tattoo, latent
*'''Torso:''' torso, latent
*'''Arms:''' left arm, right arm
*'''Legs:''' left leg, right leg
*'''Skin'''
*'''Wings'''
*'''Tail'''

Some theme pieces do not take slots. Exceptions include the [[elmsoul]] and [[frost]] hair streaks, for example.

Events that target the same '''theme slot''' for a theme piece are in practical conflict.

For example, without modding or cheats, a hero with the [[crystalline]] theme will not be eligible for the [[sylvan]] theme even though the theme files do not define a conflict. This is because both events target '''Eligible for Theme Piece:''' with the same '''theme slot''' (head).

====Detailed Discussion: Forbidden Theme Aspects====

The third main type of conflict includes events that define [[Targets and Scoring Guide#Hero Aspects|forbidden aspects]] for the '''role''' that is granted a theme in the event.

Similarly to the '''Eligible for Theme Piece''' conflict discussed above, they impose artificial restrictions (and practical conflict) to some theme combinations.

These are present in the [[Worlds Apart]] event that gives the [[Spell Touched]] theme, and the [[The Merchant|event]] that gives the [[Foxish]], [[Scorpioid]], or [[Skunkish]] themes.

::'''Example: Forbidden Theme Aspects for Worlds Apart (Spell Touched)'''
:::'''Forbidden Aspects:''' theme_bear, theme_crow, theme_deepist, theme_gem, theme_fire, theme_foothill, theme_shadow, theme_star
:::''A hero with the [[beartouched]], [[crowtouched]], [[Mark of the Horn|mark of the horn]], [[crystalline]], [[flamesoul]], [[Child of the Hills|child of the hills]], [[shadow]], or [[celestial]] themes is ineligible for the role that will be given the [[Spell Touched|spell touched]] theme.''
:::''Note! Receiving the [[Spell Touched|spell touched]] theme before receiving any of the themes above imposes no conflict on the themes.''

====Detailed Discussion: Other Practical Conflicts====

Finally, there are some special cases of theme conflicts.

'''Flamesoul:'''
:: The [[Stories of Fire|event]] that grants the [[Flamesoul]] theme targets the left arm slot, but grants theme pieces for both the left arm and head (tattoo) slots.
:: A hero with a head slot theme filled that is not in a '''Forbid Combine With''' conflict with the [[Flamesoul]] will receive the left arm, but not the head.

'''Mortificial Enhancements:'''
:: The [[Troygan the Enchanger|event]] for the [[Mortificial Enhancements]] theme requires a hero to have prosthetic limbs.
:: However, prosthetic limbs are replaced by theme limbs for a hero who receives any theme with limbs.

'''Events that Clear a Theme Slot:'''
:: While not a theme conflict, some events clear a theme slot before applying a piece, most notably [[The Merchant]] event. A hero with a wolf of crow tail for example, will have the tail removed before receiving another tail.

=====Rules of Thumb=====

Summing up, here are a few rules of thumb:

* If you desire a [[Spell Touched]] warrior, find the [[Worlds Apart]] event before taking other transformations (or inspect the forbidden theme aspects in detail beforehand).
* If you desire [[Mortificial Enhancements]], find the [[Troygan the Enchanger]] event before themes that have limbs.
* If you desire a [[Child of the Hills|child of the hills]], [[Frogtouched|frogtouched]], or [[Mark of the Horn|mark of the horn]] hero with [[flamesoul]], find the head theme piece for those themes first.

====Detailed Table of Theme Conflicts====

Finally, below is an external link to a (view only) Google Docs spreadsheet, with different types of theme conflicts numbered in detail.

Reading theme rows will show the themes that the theme is blocked by, and reading theme columns will show themes that the theme blocks.

External link: [https://docs.google.com/spreadsheets/d/1oSBj7QSQY5EE_slgd0TmyP6pG9JksHyDPrTVjsDvgAc/edit?usp=sharing Theme Conflict Guide]