Practical user guide

From a character search to a useful build comparison

This guide explains the intended workflow and the common interpretation mistakes that can make a technically correct number misleading.

1. Find the right character

  1. Select Cain or Sirocco for a character-name search.
  2. Use ExplorerName when you want characters attached to an Explorer Club name.
  3. Enable Exact Match when a short or common name returns too many results.
  4. Confirm the server, class, and Explorer Club on the result before comparing it.

A character can be temporarily missing if it was renamed, transferred, deleted, or has not yet appeared in the upstream data used by the lookup.

2. Separate fame from score

Fame is the in-game progression value supplied with the character data. DFO Gang Score is a modeled result produced from supported equipment and class inputs. Sort by fame when you want progression order; sort by score when you want the site's modeled performance order.

The safest comparison is two current characters of the same advanced class under the same calculation version. A dealer score should not be compared directly with Buff Score.

3. Read a character page in layers

  • Start with class, fame, rank, set, and update state.
  • Inspect equipment reinforcement and enchants, then review Oath contributions separately.
  • Use score detail to identify which group of effects explains a difference.
  • Check fame and equipment history before assuming a snapshot represents a long-term build.

“N/A” or a calculating state is not a zero. It normally means an input, mapping, or calculation result is unavailable and should not be used for ranking a build by hand.

4. Use rankings as a comparison set

Choose the advanced class first, then the relevant score or fame sort. The first page is useful for discovering high-performing examples, while later pages provide a broader comparison. Check the report's character count and update date before drawing a conclusion.

One top-ranked character is an example, not a build recommendation by itself. Open several profiles and look for repeated equipment patterns before treating a choice as a trend.

5. Interpret statistics percentages

Equipment-set share describes the eligible characters using that set. Oath and Crystal shares are grouped by slot. VP or enhancement type percentages may use the characters selecting that skill as their denominator, while overall usage uses the class sample. Read the labels and sample size together.

A popular option can be accessible, old, or easy to use rather than mathematically best. Statistics describe observed choices; they do not establish causation.

6. Treat the simulator as an estimate

The equipment simulator reuses the supported scoring pipeline with selected replacements. It is useful for isolating the modeled effect of a gear change before committing resources. It cannot reproduce player execution, a full party, every encounter rule, or an effect the parser does not yet support.

Compare the original and simulated state with the same options, change one decision at a time, and verify unusually large swings against the item description and methodology.

When a result looks wrong

  1. Refresh the profile and confirm the game data itself is current.
  2. Check whether the item or skill was introduced or changed in a recent patch.
  3. Record the character, server, item or skill, selected mode, displayed result, and expected behavior.
  4. Report the smallest reproducible example through the community.

A detailed correction report improves the model for every affected character; a screenshot with no character, item, or expected calculation usually cannot be verified.