The key decision
Choose a combat goal, check the next useful breakpoint in your client, and test one change before committing more resources.
Check your ruleset first
NC announced five Stigma slots on 25 March 2026 and a Stigma cap of 25 in July's KR Chapter 1. Do not transfer those limits automatically to another region.
Record your region, patch date and class alongside the build. Compare available slots and skill descriptions against your client. This site's builder currently has four Stigma slots, so it cannot represent the complete configuration described by that KR update.
Give each skill a job
Choose one goal: clearing packs faster, handling a boss consistently, or supporting your group more effectively. List the skills you actually use and when you use them.
Assign jobs: setup, main damage, resource recovery, defense or party support. If two buttons appear to serve the same purpose, compare their conditions and availability. Do not discard a defensive option merely because it does not increase the damage number on screen.
Plan the next useful breakpoint
Here, a breakpoint means a level where the skill description grants an effect you need. Copy the current level, next relevant effect, requirements and total cost from your client. Record bonuses shown on equipment and other systems separately.
Compare two investments by their full cost to reach the intended result. The cheaper individual level need not be the better choice. Before replacing equipment, recheck the skill panel; preserving the required effect matters more than increasing an isolated item number.
- Current levelRead it in your client
- Required effectCheck the breakpoint and full cost
- Try one changeCompare similar encounters
Breakpoints depend on the skill and game version. Take the numbers from the current in-game description.
Build combos around conditions
Taiwan's Gladiator guide describes attacks requiring a knocked-down target and effects triggered by blocking. That demonstrates dependencies, not a universal rotation.
Write your own sequence as condition, setup, opportunity attack and return to a safe position. For each step, add a fallback for when the condition fails. Practice interruption by enemy movement as well. Do not assume a control-immune target behaves like an ordinary monster, or keep pressing a follow-up that never becomes available.
Test your input rhythm
The KR update of 28 January 2026 described cancelling basic attacks with left or right mouse clicks. Confirm the behavior in your client.
Begin with a slow, manual execution of a short sequence. Check that the attack lands, resources behave as expected and the next skill activates. Only then increase the pace. If faster inputs lose attacks, return to the previous rhythm. A simple sequence performed reliably produces a clearer result than a long sequence whose failures you cannot identify.
Invest in a function you use
Before upgrading a Stigma, identify the problem it should solve. Do you need damage during a safe opportunity, an answer to an attack, or support for an ally? Read the cost and reset rules in-game instead of assuming a full refund.
Test the chosen configuration in the intended activity. Do not judge an emergency tool solely through a calm trial without danger. If it remains unused, check its keybind and your reaction timing before deciding that the skill is ineffective.
Before your next upgrade
Keep a short note after each change. Record failures too; they help distinguish a poor choice from a harder attempt. These checks form a testing plan, not a promise of a particular DPS result.
- Confirm region, available slots and descriptions in your client.
- Calculate the full cost of the next effect you need.
- Practice the combo and its fallback when a condition fails.
- Change one thing and compare similar encounters.
