← Back to projects
Independent Product · Product Design + Implementation

WWM Build Lab

A gear and combat calculator for Where Winds Meet Global. I treated it as a product problem first: make complex build data understandable, keep calculations reproducible and expose uncertainty instead of presenting every number with the same confidence.

ProfileGlobal 2.0 · Tier 96
FocusBuild comparison
StackTypeScript
DeliveryCloudflare
WWM Build Lab calculator interface
Local screenshot from the deployed independent product.
Problem

A calculator is only useful if the data behind it can be trusted.

The game exposes interacting stats, caps, weapon types, buffs and combat rules. A polished interface would still be misleading if constants from different versions or regions were mixed together without an evidence state.

My role

Product structure, information design and implementation workflow.

I shaped the calculation experience, source-priority rules, uncertainty states and deployment checks, then iterated the interface around real build configuration and comparison tasks rather than a static dashboard mockup.

Product logic

The interface is organized around decisions, not raw formulas.

The useful loop is configure → compare → understand. Data provenance and confidence stay attached to that loop so a player can tell when a result is a supported calculation and when the source is incomplete.

01 / CONFIGUREBuild inputs

Choose gear and combat inputs in a structure that mirrors the decisions a player is actually making.

02 / CALCULATERules stay explicit

Caps, direct critical, Precision, Affinity and per-skill outcome eligibility are kept as distinct rules rather than flattened together.

03 / COMPARESee the build consequence

The UI emphasizes the effect of a build choice instead of exposing a wall of disconnected constants.

04 / VERIFYEvidence state

Current Global evidence outranks older workbook or community references when sources disagree.

05 / REPRODUCEBuild provenance

Production output includes build information so the served commit and data version can be checked.

Evidence hierarchy

Uncertainty is part of the interface model.

The data policy is deliberately ordered. That makes source conflicts visible and prevents lower-confidence references from silently overriding the current Global client.

01 / SOURCECurrent Global client

Current English Global screenshots are the highest-priority source.

02 / SOURCEOfficial patch notes

Official Global changes are used before workbook or community references.

03 / SOURCEWorkbook constants

The Lv100 Upper / 100上 profile supplies constants that are cross-checked against Global.

04 / SOURCEObserved fixtures

Player or dummy observations can validate behavior when they are clearly scoped.

05 / SOURCECommunity / CN

Reference material remains lower priority and is not applied automatically when it conflicts with Global.

NO FAKE PRECISION
Unknown is a valid product state.

A complete current Global T96 Relaid Modulating cap table has not been verified. Relaid roll quality therefore displays N/A instead of being compared against standard Tier 96 caps as if the missing table were known.

Shipping & verification

A live calculator needs a verifiable production state.

The project is deployed to Cloudflare Pages and every production build emits a build-info file containing commit, branch, build time and data version.

PRODUCTION PROVENANCE

The UI and the data version can be checked together.

This turns deployment verification into part of the product workflow instead of relying on a visual spot-check after release.

commitbranchbuild timedata versionGlobal 2.0 profileCloudflare Pages
What this demonstrates

Product design that survives contact with messy data.

Product UI & information architectureEvidence-aware data designUncertainty statesCalculation-system thinkingTypeScript implementationProduction provenanceCloudflare delivery