01

Six families, different decisions

The official store page confirms six distinct weapons and more than fifty unique upgrades per weapon. That makes the weapon choice a route decision, not a cosmetic loadout choice.

Compare range, recovery, dash behavior, special attack timing, and the kind of artifact effects the weapon can use consistently. Raw damage alone does not explain why a weapon feels safe or awkward.

02

Read the upgrade tree

The Steam Community guide recommends using the in-game Journal to inspect unlocked artifacts, tablets, weapons, and upgrades before committing to a build. Use that journal as the primary reference, then record the exact upgrade name and version on the Wiki.

The old community guide contains useful mechanics notes but is explicitly based on pre-1.0 versions. Treat its numbers as historical until re-tested.

03

Weapon page checklist

Every weapon page should answer four questions: how it attacks, what its safe range is, which upgrades define its route, and which artifacts or tablets are common partners. Add a short demo video only when the version is clearly labeled.

04

Compare weapons by job

Use four questions when testing a weapon: how safely does it start an encounter, how quickly can it recover, how much space does its special attack control, and what happens when enemies surround you? A weapon can be slower and still be the better answer if it creates a reliable punish window.

Capture the normal attack, dash, and special attack separately. Treat the upgrade path as a change in job, not merely a bigger number.

05

A current weapon test

Run the same weapon through one normal room, one dense room, and one boss attempt. Note the first upgrade that changes the route, the artifact that made the largest difference, and the moment the weapon stopped feeling safe.

The Journal is the right place to verify names and branches. Link a screenshot when a page claims an unlock or a specific evolution.