Players changing weapons
Skills and Weapon Compatibility Guide
Build a legal skill bar by starting with class and weapon requirements, then checking slots, energy, conditions, and the affixes that actually affect those skills.
Updated 2026-08-016 min readA skill belongs to a loadout context
Mistfall Hunter's skill interface separates basic and weapon skills and shows assigned input slots, requirements, descriptions, and previews. The same class can support different weapon families, but the skill set for one family should not be assumed legal for the other. Select class, weapon, and stance before filling the bar.
The current weapon screens contain 79 named skills that can be equipped, plus 17 follow-up actions triggered or modified by related skills. A follow-up action is not automatically another skill-slot choice, so check whether the game lets you equip it directly or activates it through another action.
Check legality before power
For each slot, confirm the required weapon family, any mutually exclusive skill, and the specialization rules shown by the current interface. Some specializations can change how many skill slots are available. A copied bar is not valid merely because every name exists in the game; the complete set must fit the selected weapon and the current slot rules.
If the game refuses to equip a skill, remove assumptions in order: verify the active weapon, verify the selected specialization or branch, remove a conflicting skill, and check whether the slot itself is available. Do not solve a rules problem by repeatedly clicking or by treating a controller issue as intended incompatibility.
Map each skill to a job
A functional bar normally needs answers for approach, pressure, defense or escape, and recovery or utility. One skill can cover more than one job, but every slot should have a reason. If all skills require the same opening, the loadout can collapse when terrain, another team, or a missed attack removes that opening.
Read energy-charge and condition language carefully. A preview video shows animation and intended use, but it does not prove exact range, damage, cooldown, or interaction order. The launch known-issue list specifically notes a mismatch between Flameblade's visual effect and damage range, demonstrating why visuals alone cannot define a numeric hit area.
Connect affixes only after the bar is final
Affix value depends on what you actually use. Identify which equipped skill or repeated action an affix can affect, then decide whether the condition occurs often enough. Players have specifically requested clearer affected-skill visibility because generic labels can make a bonus look broader than it is.
Avoid adding percentages from different categories until the game's calculation order and rounding are reproduced. Base values, additive modifiers, multiplicative modifiers, conversions, conditions, stacks, and final display rounding may not share one step. A trustworthy comparison can show compatibility before it claims an exact final number.
Test one complete loop
In a low-risk run, execute the intended sequence against ordinary pressure: approach, use the primary damage or control action, respond when it fails, and disengage. Note which skill was unavailable, too slow for the position, or competing for the same resource. Replace the weak link rather than changing the entire bar.
Finally, test the same loop while moving toward extraction. A skill set that wins a stationary fight but cannot create space to leave may be wrong for an extraction objective. Route survival is part of skill compatibility in practice, even though it is not a weapon requirement in the menu.