Warera Build Tool

How this tool works

What it does

The build tool finds character builds that maximize daily damage (or cases) while minimizing daily net cost, given your level, rank/battle bonuses, company engines, and any gear or skill pins you set. Rather than recommending a single "best" build, it gives the highest damage builds for each net cost tier (0, 0.05, 0.1, etc).

The optimization algorithm

The optimizer is NSGA-II (Non-dominated Sorting Genetic Algorithm II), a well-established multi-objective evolutionary algorithm. It works by evolving a population of candidate builds through selection, crossover and mutation.

A separate single-objective run identifies the highest-damage skill allocation for the highest gear tier, which becomes the gold-bordered "highest damage" card appended to results.

How daily net cost is calculated

Net cost = gear durability cost + consumables (ammo, food, pill) − scrap resale from used gear − expected case income − estimated loot rewards − company engine income. All gear cost figures are durability-weighted: a piece that lasts two days costs half as much per day as one that breaks. The "net cost per 1K damage" efficiency figure divides net cost by daily damage, and acts as our primary comparison metric across builds.

Corners cut for performance (and why results vary slightly between runs)

• Gear is evaluated per tier, not per individual roll. During optimization each tier is assigned a single representative stat profile (the market value-quality stats, or midpoint if data is sparse). The optimizer cannot see individual rolls — it only chooses tiers. The per-roll recommendation shown in tooltips is computed afterwards, not during search.
• NSGA-II is heuristic, not exhaustive. It searches a sample of the build space, so re-runs with different random seeds may find marginally different results. Results are deterministic for the max-damage pass but vary for the main runs.
• Skill tables are cached per gear combination. Because skill marginal values depend on gear baseline, the optimizer pre-computes skill contribution tables once per unique gear set seen and reuses them. This is the main speed optimization.
• Market analysis uses sampled transactions. Gear stat ranges, value-quality points, and price curves are derived from up to 500 recent market transactions per item (filtered for outliers).

Gear recommendations — Optimal vs Value

Each gear tooltip shows up to three rows:

• Roll range — the full min–max stat range for that slot and tier, from game data.
• Optimal (most efficient for build) — the specific stat roll that maximises total-build-damage divided by price, evaluated against your exact build context (skills, other gear, ammo, food). This is build-aware: it can in principle differ between cards. The price shown is the expected market price at that quality level, interpolated from the observed transaction price curve.
• Value (best stat to price ratio) — the knee of the price-vs-quality curve for this item: the quality percentile at which paying more stops being worth it relative to the stat gain. This is a market-level property, not build-specific.

Why does the same tier show identical gear stats across all build cards? The "Optimal" recommendation is build-aware, but for most armor slots the optimal quality band is robust — the damage-per-price argmax lands on the same point whether the overall build costs 0.15 or 0.25 per 1K damage, because the marginal contribution of, say, pants armor to total damage is small relative to the price curve shape. The 0.15-vs-0.25 difference between cards comes from choosing different tier combinations and skill distributions, not from buying different rolls of the same item. Weapons are the exception — the Optimal recommendation there sweeps a 5x5 ATK/CritC quality grid and is more sensitive to build context.

Prices and live data

The tool needs a Warera API token to fetch live market prices, stat ranges, and transaction history. Without one it falls back to built-in defaults, which may be stale. Token is stored locally in your browser and is never sent anywhere except the Warera API. If you see "Default prices" in the header, click the token prompt that appears after optimizing to enter yours.