Editorial methodology

Abyssus Builds separates verifiable game facts from editorial recommendations. A weapon name, unlock condition, or Blessing roster should be source-checkable; a tier placement is our practical judgement about how those systems fit together.

Source hierarchy

1. Official first. Patch scope, release timing, platform support, and newly added systems are checked against the developer’s Steam announcements and the official Steam store page.
2. Structured reference second. Names, rosters, enemy moves, and Logbook-style descriptions are cross-checked with the Abyssus community wiki. A wiki entry marked as a placeholder is not presented here as a finished guide.
3. Interpretation last. Pairings, routes, target priority, and tier positions are written by the Abyssus Builds editorial team from the documented mechanics. They are labelled as recommendations and can change without a game fact changing.

How weapon tiers are decided

We judge every weapon on the same four questions: how quickly it handles a mixed room, whether it has a credible isolated-boss plan, how many upgrades are needed before its core loop works, and how much aiming or positioning risk the player must accept. The tier list is a decision aid, not a laboratory damage chart.

What our guides do—and do not—claim

Build pages explain a coherent route: what the setup is trying to do, which choice enables that loop, how solo and co-op positioning differ, and which failure points to avoid. We do not have access to private developer telemetry, and the site does not present its rankings as official balance data. Where we have not run a controlled damage comparison, we avoid publishing invented DPS values or false precision.

Roguelite runs also vary. Available Blessings, Forge mods, teammates, arena geometry, and player accuracy can all make a lower-ranked weapon the correct choice. The recommendations are starting points that should be adapted to the run in front of you.

Update and correction policy

A major update triggers a roster and system review. Hotfixes trigger a targeted review when their notes affect a recommendation. Every substantive guide shows its reviewed patch and date. New systems may carry a “developing” label until the documented mechanics are stable enough for a firmer recommendation.

If a fact is wrong or a source has changed, send the page URL, the disputed text, and a public source through the contact page. Corrections are checked against the hierarchy above; opinion disagreements may be reflected as a clearer trade-off rather than silently presented as fact.

Change log