About BrokenBuilds

What we do

BrokenBuilds is an interactive build calculator platform for niche games with complex character systems. We build the tools that the big gaming sites skip over: damage calculators with real formulas, skill tree planners that let you theorycraft offline, breeding simulators that show actual probabilities, and tier lists that update with every patch.

Static build guides go stale the week a patch drops. We think interactive tools that let you experiment, compare, and share are a better way to optimize your builds. Every calculator on this site runs on community-verified math, not guesswork.

Covered games

Our tools

• Build calculators -- input your gear, skills, and stats. See real DPS, EHP, and damage breakdowns using formulas pulled from datamined sources.
• Skill tree planners -- allocate points, check prerequisites, and compare different paths before committing in-game.
• Tier lists -- community-sourced rankings that update with each patch. Dual-view grid and sortable table modes.
• Guides -- opinionated build guides that explain the math behind each recommendation, not just the final loadout.

Data integrity

Every formula, stat table, and tier ranking on this site is sourced from community wikis, datamining databases, official patch notes, or verified community testing. We cite our sources and declare confidence levels. When we do not have verified data, we say so -- we never fill gaps with made-up numbers.

Research methodology

Each game hub starts with a structured profile (genre, mechanics, entity list, demand-driven content plan) that we maintain in the open-source `wiki/[game]/` tree. Entities -- weapons, classes, mutations, cards -- are captured from primary sources: datamined exports, community wikis, and official patch notes. Every wiki page declares a confidence level (high, medium, low) and cites its sources in YAML frontmatter so a reader can audit the chain from formula back to source.

Published content (guides, tier lists, patch notes, best-builds) is written against that wiki, not against our own memory. Build data fields are validated against a per-game schema at write time: every weapon or class slug in a build has to resolve to a real entity in the database of the declared type, or the admin API rejects the write. That check is what keeps guides from drifting into fabricated stats or fake entities.

Update cadence

Tier lists are re-reviewed each patch cycle (roughly every one to two weeks per game) and re-ranked when community consensus shifts. Patch-notes pages ship within a day of the official patch release and carry the release date, not our publish date, in their metadata. Build pages track the game version they were validated against -- the `v1.02.00` style chip on every build detail page is the canonical signal. When a game’s content pipeline detects that a published page’s data is stale, the page surfaces a “last reviewed” timestamp rather than pretending to be current.

Citations

Where a number, formula, or ranking comes from a specific datamined source or community test, the wiki page carrying that entry links to the source in its frontmatter. Readers who want to trace a claim back to its origin can open `wiki/[game]/` on GitHub and follow the citation. This is slower than linking every stat inline, but it keeps the published pages readable while still giving domain experts a paper trail.

Contact

Found a bug in a calculator? Have data corrections? Reach us at contact@brokenbuilds.gg.