Learning goals
- Build a status decision workflow.
- Choose statuses by target and weapon role.
- Understand when to stack, prime, or ignore status.
- Know when to test.
- Prepare for advanced faction and Steel Path courses.
Explanation
A good status decision starts with the target and weapon. Identify the enemy problem, check whether the weapon can apply status reliably, decide whether the status supports this weapon or another damage source, choose a status that solves the problem, check stack usefulness, check enemy immunity or resistance, verify final mod order in the Arsenal, and test before expensive investment.
What should I do?
Use configs: Config A for general status setup, Config B for armor/status setup, and Config C for boss or primer setup. Invest only after testing the status against the target problem.
Common mistakes
Avoid these status mistakes before spending Forma, Rivens, arcanes, or expensive mod upgrades.
- Choosing status before identifying the target problem.
- Ignoring whether the weapon can apply the status.
- Ignoring stack caps.
- Ignoring immunity.
- Over-investing before testing.
- Assuming all enemies behave like Simulacrum test targets.
Key Takeaways
- Good status builds are intentional: target problem, application method, stacking behavior, enemy rules, then investment.
Practical task
A status plan prevents blind build copying.
- Pick one weapon you actually use.
- Pick one target content type.
- Identify the enemy problem.
- Choose one status effect that solves it.
- Check whether your weapon applies it reliably.
- Check whether it stacks usefully.
- Test the setup.
- Write one sentence explaining the status, source, and enemy problem.
You can justify a status choice without copying a build.