Low critical consistency
Test Critical Rate before adding more Critical Damage.
Use several runs because short tests are sensitive to luck.Strategy guide
Increase real encounter damage by protecting attack uptime, balancing critical stats, creating useful skill casts, and testing Forge changes without invented DPS formulas.
Best for: Players who already survive their target route but clear it too slowly
Quick Answer
High damage starts with uptime: stay alive, remain in range, and complete the attacks the build is designed around. Then add attack, critical balance, cooldown, or ultimate charge only when a controlled run shows another useful hit or cast. A larger menu number is not automatically higher encounter damage.
Decision 1
A build cannot benefit from offensive stats while repositioning, recovering, or defeated. Watch how much of the encounter is spent attacking and identify the exact reason damage stops. Movement, health, or safer weapon timing can raise real damage when those changes preserve more attack windows.
Decision 2
Attack provides a broad comparison point, while Critical Rate affects consistency and Critical Damage affects the size of critical events. A high-damage build needs the two critical fields to work together across the whole route. Do not treat a rare large critical hit as proof that the average encounter improved.
Test Critical Rate before adding more Critical Damage.
Use several runs because short tests are sensitive to luck.Test Critical Damage against the current attack option.
Keep the change only when the full clear improves.Use a broad attack test and track normal versus skill windows.
A specialized bonus may not affect the entire rotation.Decision 3
Cooldown Reduction and Ultimate Charge increase damage only when their timing changes. Count whether the build gains another safe cast before the enemy dies or the phase ends. If the ability becomes ready during forced movement or after the decisive window, the stat is not producing useful damage in that route.
Decision 4
Use the result preview to compare attack, critical, cooldown, movement, and supporting survival affixes. Higher quality and a stronger displayed multiplier can be useful signals for the current attempt, but no verified source establishes a universal conversion formula. Reject results that look larger but weaken the uptime required by the rotation.
Decision 5
Tower damage decisions are made inside a longer survival context. Take an offensive scroll when the run already survives but cannot finish efficiently; take healing or durability when another hit would end the run. A rare offensive choice has no value if the run ends before it can produce more rewards.
Decision 6
Run the same boss, wave, or Tower segment with one change. Compare time spent attacking, useful casts, deaths, and clear consistency. Keep the upgrade only when the improvement appears across several attempts. This avoids a false conclusion from enemy movement, critical luck, or a different encounter pattern.
The video shows attack, critical, cooldown, health, movement, and ultimate-related fields used in live gear decisions. It does not provide a verified DPS formula, so this guide uses observable encounter outcomes instead.
Source notes
Official records establish public experience data and destination names. Community sources support visible mechanics and decision categories. Unstable rates, formulas, gates, and reward totals are excluded or clearly limited to an observation.
FAQ
First protect attack uptime, then test one relevant stat family on the same encounter. Keep attack, critical, cooldown, or ultimate changes only when they create more useful damage across the full run.
Neither is always better. Critical Damage needs enough critical events, while Critical Rate needs meaningful damage behind those events. Test their balance across multiple runs.
No. It increases real damage only when the shorter cooldown creates another safe and useful cast during the encounter.
No. Health or movement can increase real damage when they prevent interruptions or deaths that remove attack uptime.
Change one layer, repeat the same encounter several times, and compare useful casts, attack uptime, deaths, and clear consistency rather than one peak hit.
Continue
More guides