01

Rank the use case

A weapon tier list should separate room clear, boss consistency, learning curve, and co-op value. A single overall tier hides the exact question the player is asking.

The official store page says each of the six weapons has more than fifty upgrades, so the tier can change with the selected branch.

02

Show the evidence

Every row needs a version, difficulty, mode, and test result. Link the detailed weapon page and attach a short run clip when the recommendation depends on timing rather than raw numbers.

03

Avoid false precision

Use labels such as reliable, specialist, learning-friendly, and high ceiling until a repeatable current-version test supports a numerical ranking. That keeps the page useful after balance changes.

04

Tier by scenario, not by hype

Create separate labels for room clear, boss damage, safety, and ease of assembly. A weapon can be excellent in one column and awkward in another without being badly designed.

The page should show the test conditions and date beside every placement. If a branch has not been tested after a patch, keep it provisional.

05

How to read the list

Use the tier list to choose a direction, then open the full weapon page for the actual route and substitutions. The list is a map of questions, not a replacement for the build guide.

When community results disagree, preserve both tests and explain the difference in difficulty, artifact access, or player goal.

06

What would make this a publishable tier list

For every placement, run the same branch through a normal room, a dense room, and a boss opening on the same difficulty. Record the inventory grid, key tablet line, permanent progression state, and whether the test is solo or co-op. Without that context, a ranking is entertainment rather than a decision tool.

Use provisional labels such as learning-friendly, specialist, safe DPS, or high ceiling while the evidence is incomplete. Those labels tell a player how to choose today without pretending that balance has stopped changing.

07

Version stamps prevent stale rankings

A tier can move when a weapon interaction, tablet, or boss telegraph changes. Put the game version and last test date next to every row, then link to the patch note that prompted the retest. Readers should be able to see the difference between a current observation and an older community result.

If a ranking has not been rechecked, preserve it as a historical note rather than silently leaving it in the live table. This protects searchers from treating an old showcase as a recommendation for a different game state.