Mistfall Hunter Affixes Guide – What Is Confirmed
Updated 2026-08-02
On this page
Mistfall Hunter uses affixes as one part of its build system. The official store confirms dozens of rare gem affixes alongside talent trees, active skills, gear, and weapon stances. Official launch material also confirms Holy Weapons with exclusive gameplay affixes. What the approved sources do not provide is a complete current affix table, exact scaling values, a wine table, or a universal best-in-slot list.
Where Affixes Fit in a Build
Affixes are not the whole build. They sit beside the class's talent tree, selected active skills, equipped gear, and weapon stance. That matters when comparing recommendations: an affix choice shown for one class and weapon setup should not automatically be copied to another setup.
The official store establishes that rare gem affixes are numerous, but it does not publish the complete pool in the material used for this page. This guide therefore does not assign undocumented effects to individual affix names or reproduce an unverified numeric table.
Holy Weapons and Exclusive Affixes
The official launch announcement introduced Holy Weapons and their exclusive gameplay affixes. A pre-launch developer update says Holy Weapons can reshape skill mechanics. That wording supports a meaningful interaction between the weapon, its affix, and a skill; it does not identify every affected skill or specify whether the change concerns damage, range, cooldown, cost, or another property.
For a real item decision, read the current in-game description and compare it with the skill and stance you actually use. Do not assume that a Holy Weapon is better for a particular build solely because it belongs to this special category.
One Dated Creator Build Example
A creator video uploaded July 31, 2026 recommends Vitality, Elusive, and Valor for one Withered Knight Polearm and Shield solo build. This is an attributed, build-specific recommendation from the video's creator. It is not an official priority list and does not establish the effects of those three affixes for this page.
The useful takeaway is the scope of the example: one class, one weapon setup, one creator's solo-build goal, and one captured balance period. Players using another class, stance, or objective need current evidence from their own tooltips rather than treating those names as universal choices.
How to Evaluate an Affix Safely
Use a narrow checklist when the current client presents an affix:
- Confirm the exact wording in the current item or gem tooltip.
- Identify the class, stance, and active skill the build actually uses.
- Separate an official mechanic description from a creator's build recommendation.
- Check the date and patch context before copying exact values or priorities.
- Omit any claimed interaction that the current tooltip or a direct source does not state.
This approach is less convenient than a permanent tier list, but it avoids turning a dated build video or an affix name into a mechanic the sources never confirmed.
When two recommendations disagree, compare their class, weapon stance, intended activity, upload date, and cited game version before comparing the affix names themselves. A recommendation for one solo Polearm and Shield setup is evidence about that creator's build, not evidence that every character should pursue the same three modifiers.
The same boundary applies to exact numbers. A percentage or level table should identify the current item, tooltip, data source, and game version. Without those details, a precise-looking table can be less reliable than a shorter guide that states only what the official and dated sources establish.
What Remains Unconfirmed Here
The approved evidence for this page does not support a complete affix catalog, exact level-by-level scaling, exact wine effects, or best-in-slot rankings for every role. Those details require current tooltip captures or a versioned database with direct item evidence. Until that evidence enters the page's source contract, they should remain outside the guide.
This boundary also prevents accidental patch drift: a dated build example remains useful when its author, setup, and date stay visible, while an unattributed “best affix” claim can become misleading after one balance update.