The official Steam page describes more than fifty unique upgrades for each of Sephiria’s six distinct weapons. That scale makes a copied “best upgrade” list tempting, but the useful first step is smaller: identify the job of an upgrade, the cost it creates, and the follow-up that makes it reliable. Exact names, branches, and coefficients belong to the current game build and should be recorded with a version.
Read the branch before selecting it
Write the displayed upgrade text and the branch context before choosing. If a choice changes the attack’s reach, timing, area, or follow-up, describe that change in player language. Avoid inventing an exact coefficient when the menu does not show one. A clear functional description remains useful even after a balance patch.
The Weapons Guide provides the comparison fields. Use the same target, range, room, and mode when comparing two branches. If the reward path is random or unavailable, record that limitation instead of merging observations from unrelated runs.
Name the tradeoff
An upgrade can improve damage while demanding a longer action, a closer position, or a tighter inventory. Another can improve control while slowing the clear. Neither result is universally correct without an objective. State whether the test seeks first-clear safety, boss consistency, room speed, achievement progress, or a co-op role. Then judge the branch against that objective.
A tradeoff also has an execution cost. If a player cannot reliably trigger the upgraded action, a theoretical increase will not appear in a normal run. Test the input, recovery, and movement separately. The first successful action is not enough; repeat it after a miss or a crowded room to see whether the upgrade has a practical fallback.
Connect upgrades to inventory
The Artifacts and Tablets pages explain why a weapon branch cannot be evaluated alone. Reserve the space required by the test, then compare what the branch makes possible against what it removes. If a Tablet arrangement supports the action only in a quiet room, label the build as situational or co-op-specific.
Publish a responsible upgrade note
Each entry should include weapon, displayed branch, date, version, mode, target context, observed result, limitation, and confidence. A community guide can reveal a promising branch, but the page should rewrite the idea and omit copied numbers or tables until the current game confirms them. Link to Updates when a patch changes the system.
A branch comparison card
For each branch, record the displayed name, weapon, preceding choice, intended job, target context, and the first failure it prevents. Add one sentence about the cost. “More control” is incomplete if the action consumes the only safe movement window; “more damage” is incomplete if the upgrade requires a range the player cannot maintain. This card keeps the comparison practical without inventing hidden coefficients.
Run the comparison in two passes. First, test the branch in a quiet room where the action is easy to observe. Second, test the same action when a normal threat requires movement or target switching. If the branch improves only the quiet test, label it as setup-dependent. If it remains useful under pressure, state what fallback made the difference.
Update the recommendation
When a balance note arrives, check the branch’s job and cost before changing its label. A numerical change may not alter the route, while a recovery or footprint change may invalidate the whole layout. Link the retest to Patch Notes and preserve the previous observation as historical evidence.
That record also tells readers what to practice next.