The store confirms that Sephiria has six distinct weapons, but a player still needs a way to learn them. Start with behavior, not names. For each weapon, ask how it reaches targets, how it handles a missed attack, how much room it needs, and what kind of Artifact or Tablet arrangement makes its good moments repeatable. The answer can change with a patch, so record the version and do not reuse an Early Access ranking as if it were a launch result.
The four-part weapon test
Reach
Measure the distance and angle at which a normal attack can safely connect. A longer reach can reduce contact risk, but it may demand a different movement rhythm.
Timing
Watch recovery after an attack, dash, or special action. A high-damage option is not useful if a missed swing leaves no answer to the next threat.
Room control
Test one crowded room. Note whether the weapon creates space, focuses one target, or needs a teammate to protect its setup.
Follow-up
Write down the first upgrade and the inventory bonus that would make it more reliable. This is the start of a build, not a final ranking.
Record a fair comparison
Use the same chapter or practice context, the same starting assumptions, and a clear success condition. “Kills the target quickly” is incomplete unless the target, distance, upgrade branch, and defense context are named. A better record says that a weapon finished a defined room without taking damage, or that it kept a boss window safe for a measured period. Do not overstate a small sample; three clean rooms show a promising direction, not a universal answer.
For a new player, comfort is evidence too. If a weapon makes the enemy telegraph readable and lets you keep a safe distance, it may be the best learning tool even if an advanced build has a higher ceiling. Once the controls feel natural, you can compare damage and speed without confusing unfamiliar timing with poor balance.
Use inventory support deliberately
An Artifact or Tablet should be listed beside the weapon choice, never in a separate universe. If the weapon rewards staying near enemies, protect the spaces that support survival and movement. If it rewards repeated ranged attacks, preserve the inventory region that amplifies its reliable action. The exact interactions belong to the current game build; the stable method is to place, test, observe, and document.
Co-op introduces another comparison field: who creates the safe window? A weapon that needs setup may become more comfortable when a teammate draws attention, but that does not prove the weapon is stronger in solo play. Publish solo and group observations separately.
Add the same honesty to a successful result: say what the weapon did not test. A clean room does not prove boss safety, and a co-op opening does not prove solo consistency.
A three-run learning protocol
Use the first run to learn reach and recovery, the second to test one upgrade direction, and the third to compare the result against the original checkpoint. Keep the target and route as similar as possible. If a run changes because a reward was unavailable or an enemy behaved differently, mark that difference rather than silently combining the results.
The protocol is intentionally modest. It cannot prove a global ranking, but it can show whether a weapon’s job is comfortable, whether its inventory support is plausible, and which question deserves a deeper test. Add the current version and mode to the note before sharing it with another player.
Before publishing the result, explain the losing condition too. A weapon comparison is more useful when it says whether the test failed because of range, recovery, crowd pressure, inventory space, or an unverified upgrade interaction. That detail gives readers a practical next experiment and prevents a small sample from becoming an exaggerated ranking.