1
formula rows
Build math audit
PVE Stat Formula Notes
A forum-style number desk for Where Winds Meet PVE claims: formula sources, stat priority, affix rows, tuning material risk, Mystic Skill damage share, and the proof needed before spending.
PVE statsFormula auditAffix priorityNo rankings
Maintained byHeavenskiss
Pinned number questions
Treat every formula as a claim that needs a witness.
The useful English page is not a copied formula wall. It is a filter: what does the source claim, which system owns it, how risky is it, and what would prove it for Global.
Can I copy the Chinese PVE damage formula into my Global build?
Use it as an audit lead, not final advice. The page keeps the formula row as source evidence, then asks for Global tooltip screenshots, practice tests, patch date, and mode context before publishing numbers.
Which stat or affix should I stack first?
Do not start with a single stat. Start with role, mode, weapon pair, Mystic Skill share, qi-exhausted burst plan, and whether the source row is about the same activity you are playing.
Why does the site avoid publishing exact percentages?
Because numeric pages rot fast. A percentage can be old, CN-only, tooltip-only, bug-affected, or mode-specific. The useful page says how to verify it before spending.
Should Mystic Skills change how I read weapon rankings?
Yes. If a source says a large share of damage comes from Mystic Skill or qi-exhausted burst windows, weapon rankings need a mode and rotation test before they mean anything.
Where should I go after this page?
Use Beginner Build Checklist for spending, Inner Ways Primer for 心法 claims, Mystic Skill Evidence Checklist for skill damage rows, and No-Ranking Build Method for stale tier lists.
7
support rows
0
public formulas
audit
proof state
A number is not a guide
Formula rows are useful for asking better questions. They do not become stat priority or upgrade advice until current Global behavior is checked.
Name the mode first
A stat line can matter differently in story bosses, Bloodbath, five-player content, ten-player content, or daily farming.
Separate tooltip from test
The source itself warns that displayed multipliers can be wrong. Treat tooltip math and practice-dummy output as two different rows.
Spend after the audit
If the claim asks for tuning stones, gear rolls, Inner Ways, or weapon commitment, route it through a proof checklist first.
Source desk
These Chinese rows are useful, but each has a different job.
Formula, attribute, tuning, affix, power-growth, and recycle rows should not collapse into one recommendation. The first job is routing and proof state.
- Useful for
- Damage-formula structure, DOT/direct-damage split, defense and resistance cautions, Mystic Skill damage-share leads, qi-exhausted burst-window claims, Inner Way notes, and weapon-test prompts.
- Safe use now
- Turn it into an audit board: what type of number is being claimed, what activity it belongs to, and what proof would make it publishable.
- Hold
- No copied current formula, coefficient, percentage, stat priority, boss-defense value, burst-window timer, or weapon ranking without Global testing.
- Useful for
- Basic attribute names, stat vocabulary, and the question a new player has when gear rolls or character panels start showing many labels.
- Safe use now
- Use as glossary and routing material before a stat page claims which line is strongest.
- Hold
- Final Global labels, UI order, hidden scaling, and value priority need screenshot proof.
- Useful for
- Separating tuning, transfer, gear-change, and reroll questions before a player spends materials.
- Safe use now
- Route into a tuning checklist and resource-risk warning.
- Hold
- Exact material names, transfer limits, reroll costs, and current UI flow need Global screenshots.
- Useful for
- Tuning-stone usage intent and where material-spend warnings belong.
- Safe use now
- Use as a spend-gate row connected to Resource Spending and Beginner Build Checklist.
- Hold
- Prices, sources, stock limits, item names, and best use cases need current proof.
- Useful for
- Mode-specific affix language: daily content and Baiye War should not be mixed with universal build advice.
- Safe use now
- Use as a mode-label example and affix-proof queue.
- Hold
- Exact priority order, current mode values, and weapon-specific conclusions need testing.
- Useful for
- Nameless-weapon affix demand, search aliases, and a warning that weapon-specific rows must not become universal rows.
- Safe use now
- Route to Weapon Feel Primer or a future Nameless weapon page after proof exists.
- Hold
- Final stat priority, suffix translations, damage values, and weapon-loop assumptions need Global proof.
- Useful for
- Investment language: when a number claim turns into upgrade, gear, Inner Way, or resource advice.
- Safe use now
- Use as a build-audit prompt, not as an upgrade order.
- Hold
- Upgrade order, material paths, power thresholds, and catch-up values need current evidence.
- Useful for
- Recovery and recycle-risk warnings before a player deletes or converts gear.
- Safe use now
- Send players to a reversible-action checklist before trusting any stat formula.
- Hold
- Recycle rules, recovery windows, item names, return values, and irreversible warnings need screenshots.
| Source row | Useful for | Safe use now | Hold |
|---|---|---|---|
Formula source PVE數值系統與傷害公式解析 | Damage-formula structure, DOT/direct-damage split, defense and resistance cautions, Mystic Skill damage-share leads, qi-exhausted burst-window claims, Inner Way notes, and weapon-test prompts. | Turn it into an audit board: what type of number is being claimed, what activity it belongs to, and what proof would make it publishable. | No copied current formula, coefficient, percentage, stat priority, boss-defense value, burst-window timer, or weapon ranking without Global testing. |
Term source 基礎屬性講解 | Basic attribute names, stat vocabulary, and the question a new player has when gear rolls or character panels start showing many labels. | Use as glossary and routing material before a stat page claims which line is strongest. | Final Global labels, UI order, hidden scaling, and value priority need screenshot proof. |
Tuning source 調律與轉律入門指南 | Separating tuning, transfer, gear-change, and reroll questions before a player spends materials. | Route into a tuning checklist and resource-risk warning. | Exact material names, transfer limits, reroll costs, and current UI flow need Global screenshots. |
Material source 調律石使用方式 | Tuning-stone usage intent and where material-spend warnings belong. | Use as a spend-gate row connected to Resource Spending and Beginner Build Checklist. | Prices, sources, stock limits, item names, and best use cases need current proof. |
Affix source 日常及百業戰無名詞條優先順序 | Mode-specific affix language: daily content and Baiye War should not be mixed with universal build advice. | Use as a mode-label example and affix-proof queue. | Exact priority order, current mode values, and weapon-specific conclusions need testing. |
Weapon-affix source 無名詞條優先順序 | Nameless-weapon affix demand, search aliases, and a warning that weapon-specific rows must not become universal rows. | Route to Weapon Feel Primer or a future Nameless weapon page after proof exists. | Final stat priority, suffix translations, damage values, and weapon-loop assumptions need Global proof. |
Power-growth source 戰力養成建議 | Investment language: when a number claim turns into upgrade, gear, Inner Way, or resource advice. | Use as a build-audit prompt, not as an upgrade order. | Upgrade order, material paths, power thresholds, and catch-up values need current evidence. |
Gear-risk source 裝備回收建議 | Recovery and recycle-risk warnings before a player deletes or converts gear. | Send players to a reversible-action checklist before trusting any stat formula. | Recycle rules, recovery windows, item names, return values, and irreversible warnings need screenshots. |
Number audit board
Put each numeric claim in the right box.
This is the page value: it keeps formula claims, DOT logic, Mystic Skill damage, boss-window advice, and affix priority from being mixed into one shaky recommendation.
Damage formula or coefficient
Source use
Use the row to identify which terms the source thinks matter: attack, defense, penetration, attribute attack, bonuses, critical math, and special multipliers.
Proof needed
Current Global tooltip, controlled practice test, patch date, activity mode, and raw result sheet.
Owner
This page + Beginner Build Checklist
DOT versus direct-damage split
Source use
Use as a Mystic Skill and weapon-loop audit. Do not mix damage-over-time behavior into ordinary direct-hit advice.
Proof needed
Skill tooltip, test clip, target state, and whether the effect overwrites or stacks in team play.
Owner
Mystic Skill Evidence Checklist
Defense, resistance, or penetration value
Source use
Use as a warning against overvaluing ignore-defense or resistance claims without inspecting the actual enemy.
Proof needed
Enemy inspection screen, boss type, difficulty, and before/after damage comparison.
Owner
Boss Mechanics Ledger
Mystic Skill damage share
Source use
Use to explain why weapon rankings can be misleading when a large share of output comes from skill timing or burst windows.
Proof needed
Combat parse, rotation clip, skill cooldown/resource state, and activity-specific window length.
Owner
Mystic Skills + Builds
Qi-exhausted burst window
Source use
Use as a practice concept: burst timing may matter more than a static weapon score.
Proof needed
Boss-state timer, team-size context, skill sequence, and whether the window is extended by support effects.
Owner
Bloodbath Field Notes
Affix or stat priority
Source use
Use to decide what needs testing, not what to roll immediately.
Proof needed
Gear UI, affix translation, comparable stat budget, mode label, and a fallback if the roll is wrong.
Owner
Weapon Feel + Build Checklist
Proof state board
A number only becomes advice after it moves through states.
Searchable lead
The Chinese title proves a player question exists. It does not prove the answer is current.
Math needs witness
A source describes formula logic, values, or percentages. Publish only the audit frame until tested.
UI captured
A Global screenshot confirms wording, but the number still needs controlled behavior testing.
Behavior checked
A controlled test supports the claim for one mode, patch, target type, and build setup.
Still narrow
Even a proven row should name the mode, patch, cost, fallback, and what it does not cover.
Claim routing board
Send the claim to the page that can actually prove it.
Beginner Build Checklist
Spending advice needs role, source confidence, gear risk, and fallback before numbers matter.
Open owner pageNo-Ranking Build Method
Rankings must name mode, patch, source label, role, cost, and fallback.
Open owner pageInner Ways Primer
Inner Way values, pairings, upgrade levels, and boxes need their own proof route.
Open owner pageMystic Skills Index
Skill damage, DOT behavior, resource use, cooldowns, and team overwrites need separate testing.
Open owner pageBloodbath Field Notes
Boss state, phase, pressure, recovery window, and team context can change the value of a stat.
Open owner pagePatch Reading Checklist
Timed tuning, patch notes, old CN rows, and seasonal values need a dated lane before advice.
Open owner pageHold board
These rows stay unpublished as advice.
Current Global damage formulaExact stat priorityBest affix orderBoss defense or resistance valuesMystic Skill damage shareQi-exhausted window timingInner Way percentage gainsWeapon ranking from math alone
Next routes
Where the reader should go after the math check.
Beginner Build Checklist
Use before spending materials, rerolling gear, or trusting a stat recommendation.
OpenInner Ways Primer
Use for 心法 pairings, box routes, gold Inner Ways, and upgrade-proof questions.
OpenMystic Skills Index
Use when the number claim depends on Mystic Skill damage, cooldown, DOT, or resource behavior.
OpenNo-Ranking Build Method
Use when a formula row is being turned into a tier list too quickly.
OpenSource boundary
Good math pages protect players from bad spending.
The source article is valuable because it reveals how experienced players reason about formulas, DOTs, burst windows, and stat lines. The English page should preserve that reasoning while refusing to publish untested current numbers.