Methodology

How The Guidance Is Built

The site combines static game reference data with editorial notes intended to help visitors evaluate deck direction, card roles, and relic implications in a more structured way.

Framework

Four Questions Behind Each Build

How does the deck survive early fights?

A build needs enough frontloaded defense or damage to reach the turns where synergy matters. Early act consistency is weighted heavily.

What resource is it scaling?

Each character wins through a different resource pattern such as Strength, Poison, Stars, Souls, or Orb sequencing. Build notes should identify that resource clearly.

What turns actually win the combat?

Decks are judged by their most important turns: setup turns, payoff turns, recovery turns, and boss-kill turns.

What bloat makes the plan worse?

Cards that look individually acceptable can still weaken a deck by diluting draw quality and delaying payoff turns.

Data Handling

Reference Data And Editorial Copy

Card and relic records are presented as reference material, but the surrounding summaries, category framing, and site copy are written to make the information easier to use. The editorial goal is to add value through explanation, selection, and context instead of repeating thin database text.

When game terminology changes, the site should be updated so that both the raw labels and the explanatory guidance stay usable. Accuracy matters because reference pages lose trust quickly when players cannot map an in-game label to a site entry.

Updates

What Gets Revised Over Time

Character Summaries

Updated when identity, pacing, or build incentives shift enough that old primers no longer help decision-making.

Reference Tables

Updated when cards, relics, names, or localization strings change in a way that affects browsing or searchability.

Policy Pages

Updated when site practices, analytics, or advertising behavior changes so visitors can understand what the project is doing.