Published formula tool
Estimate a documented fruit, sword, or fighting style skill. This is a planning estimate, not a promise of live in-game damage.
Attack type
Estimated skill damage
2,741
Formula: (5 + 0.3 x 2,400) x 3.0 x 1.20 x 1.05.
Your last inputs are saved automatically on this device.
What this tool does
The calculator is for the moment after you have a candidate in mind and want to see how the published formula reacts to your own inputs. Pick whether you are checking a fighting style, sword, or fruit skill; enter the relevant stat; select the rarity and skill slot; then add the fruit-specific or multi-hit settings only when they apply. The result gives you a clear, repeatable estimate instead of an unexplained number.
Every control maps to a visible part of the calculation. This page does not claim to recreate every condition in a live server, inspect a target, or read combat data from your game. Its value is that you can see the inputs, change one assumption at a time, and decide whether the published model is useful for the question in front of you.
Choose the skill slot you actually want to inspect rather than treating an entire fruit, sword, or style as one number. A strong-looking estimate for one selected skill is evidence about that selected setup only. It does not automatically describe the option's full combo, ease of use, route cost, availability, or fit for every player goal.
The calculator retains the current form in your browser so you can return to an unfinished check without rebuilding it from zero. Treat that saved state as a personal scratchpad: revisit the type, stat, skill, and toggles when your plan changes instead of assuming an older estimate still represents your current build.
Why calculate before committing
A calculated value is most useful when it answers a specific trade-off. You may be deciding whether a stat investment changes the estimate enough to matter, whether two skill slots behave differently under the same assumptions, or whether a fruit awakening setting belongs in the scenario you are planning. That is much more reliable than chasing the biggest output without checking what the number includes.
A raw number can make an uncertain plan feel settled. Here, the category, stat, rarity, skill, awakening choice, and multi-hit choice remain visible. If two estimates differ, you can identify which selected input created that difference. That makes the calculation useful for discussion with teammates and for revisiting a decision after your available data improves.
Keep shared assumptions stable when you compare two scenarios. Start with the same stat and rarity, change only the skill or option you are testing, and write down why a fruit awakening or multi-hit setting is included. If several inputs move at once, a larger result tells you very little about which change actually mattered.
The calculator deliberately does not fill gaps with made-up DPS, drop chances, mastery requirements, prices, cooldowns, or secret modifiers. A clean estimate cannot prove a live outcome when those conditions are unknown. Use it as a route check alongside documented tier, wiki, and acquisition information instead of turning it into a universal winner label.
How to use the calculator
The fastest way to get a useful answer is to set the stable information first and add conditional inputs last. This keeps a formula estimate connected to the decision you are actually making and reduces the chance of accidentally comparing two unrelated scenarios.
Start with a small question: for example, whether one selected sword skill changes at your current stat, or how a chosen fruit skill looks before and after the awakening setting you intend to use. If you are still choosing among several weapons or styles, open the relevant comparison page first so route and evidence quality are part of the decision.
Select the combat category that matches the scenario, enter the stat value you want to model, and choose the applicable rarity multiplier. These are the shared baseline inputs. When comparing two cases, keep them identical unless the point of the test is specifically to understand how one of those values affects the formula.
Pick the listed skill you want to estimate. The calculator uses the documented multiplier assigned to that selected slot, so the output should be read as that skill's formula estimate. Do not use a result for one slot as a claim about every move in a kit; repeat the check for each skill that matters to your route.
Fruit awakening stages are relevant only when the selected category is Fruit. Multi-hit is optional and belongs only in the scenario where you are intentionally testing that calculator setting. Leave conditional controls at their neutral state when they do not apply. A smaller, honest estimate is more useful than a larger number built from incompatible assumptions.
Save the result with the choices that created it, then test the one alternative you care about. If a calculation would change a larger resource decision, cross-check the candidate's tier entry, wiki information, and route requirements. If those sources do not provide enough verified evidence, keep the conclusion tentative rather than forcing a recommendation.
Formula and evidence limits
The calculator exposes the documented arithmetic so you can audit the result. It begins with a base of 5 + 0.3 × selected stat. It then uses the selected skill multiplier and rarity multiplier. Fruit inputs can apply the selected awakening stages, while the multi-hit control applies only when you choose that explicit scenario. The order is handled by the tool; you do not need to reverse-engineer it from the output.
The model uses the values exposed by the form: combat category, entered stat, rarity selection, listed skill slot, fruit awakening stages when the category is Fruit, and the optional multi-hit setting. This is the complete basis for the displayed result. Changing a field changes the formula scenario; it does not fetch a new undocumented game statistic.
The result does not certify live damage after hidden modifiers, target conditions, hit timing, server state, or any value absent from the published formula. It also does not manufacture DPS, skill multipliers beyond the listed slots, prices, drop probabilities, mastery requirements, materials, or movement values. Missing evidence stays missing.
Read the output as “this is what this documented model returns for these selected inputs.” That wording is intentionally narrower than “this is what will happen in every live encounter.” It gives you a dependable way to compare the model's scenarios while preserving the uncertainty that matters in actual play and progression planning.
Data status: Formula-based estimate. If a live outcome depends on information not represented in the controls, treat the result as reference only and verify the missing condition through the supporting tier or wiki data before spending scarce resources.
Damage calculator FAQ
These answers define the scope of the estimator so you can use it quickly without confusing a transparent formula check with a complete combat simulator.
It evaluates the calculator's documented formula from the values you choose: combat category, stat, rarity multiplier, skill slot, fruit awakening stages when applicable, and the optional multi-hit toggle. The result is a planning estimate for that formula, not a combat-log reading or a guarantee of live damage.
Use the comparison tools to narrow a real decision first, then use this calculator to inspect a specific candidate and setup. A single estimated hit cannot decide whether an option is easier to obtain, better for your route, or supported by enough verified data.
The visible formula starts with 5 + 0.3 multiplied by the selected stat. The calculator applies the selected skill multiplier and rarity multiplier, then applies fruit awakening only for fruit inputs. If the multi-hit setting belongs to the skill you are checking, the optional multi-hit multiplier is also applied.
Only turn it on when you are intentionally checking the calculator's multi-hit scenario for that skill. It is not a general damage bonus and should not be enabled just because it produces a larger result. Keep it off when you need the single-hit estimate shown by the documented calculation.
Yes. The tool keeps its current inputs in your browser's local storage so a normal return to the page can preserve your working setup. That convenience does not upload a build or make the result more authoritative; review the values again before using the estimate for a route decision.