Learning goals
- Understand forced status procs.
- Understand weapon, stance, ability, and mechanic sources.
- Understand why forced procs can bypass low status chance.
- Learn how forced Slash or other forced statuses change builds.
- Avoid relying on nonexistent forced procs.
Explanation
A forced status proc is a status effect applied by a specific attack, stance, ability, or mechanic instead of only normal status chance. Forced procs can come from melee stance attacks, heavy attacks, weapon special mechanics, ability effects, mods, augments, Incarnon or variant mechanics, or content-specific interactions. A low-status weapon can still be powerful if it has a reliable forced proc.
What should I do?
When a build mentions forced procs, identify the exact source, confirm whether the proc is actually forced, learn the input or condition, test whether you can trigger it consistently, and build around it only if it fits your playstyle.
Common mistakes
Avoid these status mistakes before spending Forma, Rivens, arcanes, or expensive mod upgrades.
- Assuming high damage means forced status.
- Assuming a stance forces Slash without checking.
- Building around a forced proc you rarely trigger.
- Ignoring ability-forced statuses.
- Confusing status chance procs with forced procs.
- Copying builds that rely on hidden mechanics you do not use.
Key Takeaways
- Forced procs can define a build. Verify the source before building around them.
Practical task
Forced procs can define a build, but only if you can actually trigger them.
- Pick one weapon, stance, or ability that is said to force a status.
- Identify the exact attack or condition.
- Test it on enemies if possible.
- Confirm which status appears.
- Decide whether the forced proc is practical for your build.
You can explain what triggers the forced proc.