Sephiria Wiki: Your Field Guide to the Tower

Weapon quick reference

Branch names and examples come from TEAM HORAY's launch announcement and 1.0.31 update. This is a recognition table, not a damage ranking. Full unlock costs, complete upgrade paths and measured branch DPS: not available.

The game and its systems

Game identity and supported modes are recorded on the official Steam store page. The launch notes document the Side Bag. “Latest reviewed” describes this site's research cutoff, not a live connection to the game.

Make your first descent easier to understand

• Start with one attack you can explain. Before evaluating a reward, identify what you are doing to deal damage. Is it a normal weapon attack, a special attack, an Artifact activation, or a combination? Write the answer in ordinary language. If a tooltip changes that action, reread the answer. A setup becomes confusing when its equipment rewards actions you stopped using. This small habit makes later choices easier because you can ask whether each new effect helps the action that actually happens during combat.

• Learn the cost of the action as well as its payoff. A dramatic effect can look impressive while leaving you unable to repeat it when you need it. Watch the resource display during practice, then observe what happens when you stop attacking. Avoid making a build decision from the first burst alone. A useful comparison includes the quiet period after the burst, the time spent moving, and any recovery you need before starting again. These are suggested practice questions, not a claim about a universal damage rotation.

• Keep your first experiment narrow. Changing a costume, weapon, several Artifacts and your entire inventory arrangement at once makes it difficult to understand why the next room feels different. Try one meaningful change, inspect the result, and decide whether it addresses your current problem. If you keep getting hit while committing to an attack, simply adding another source of damage may leave that problem intact. Choose an experiment that answers a concrete question instead of trying to reproduce every part of a late-game screenshot.

Read an upgrade as a set of conditions

• Look for replacement language. An upgrade can replace an action rather than merely improve the original one. In the September update, Bloodletting Gearblade changes Reassemble into Bloodletting, while Arges changes the Blade's special attack. The practical consequence is that the old action name may no longer describe your rotation. Check equipment that mentions that action before assuming it still works. A familiar weapon silhouette does not guarantee that the inputs, resource needs or enabling conditions remain familiar.

• Separate a named partnership from a general bonus. Some effects explicitly name another piece of equipment. That is stronger evidence for a connection than similar colors or matching artwork. However, it also means the connection may depend on possessing that exact piece. When a reward mentions an Artifact you have not found, assess what the weapon offers today and what it would offer after the missing part appears. Do not value a complete combination as though the run has already supplied it.

• Treat a patch note as a change record. A note explaining that one behavior changed does not necessarily describe every unchanged property of the item. Use it to correct the affected part of an older guide, then consult the complete in-game tooltip for the rest. This distinction matters for values, duration, rarity and prerequisites. Where the public evidence does not supply a complete record, this wiki shows “not available” instead of filling the gap with a plausible number.

Make inventory space earn its place

• Compare arrangements, not just individual objects. The official description establishes that Tablets empower Artifacts and that inventory arrangement matters. When considering an item, first identify the effect you want to improve, then inspect how the proposed arrangement supports it. A visually tidy grid is not automatically the most useful grid. Conversely, keeping every appealing object can make it harder to support the few effects responsible for most of your actual combat plan. Evaluate the whole arrangement before removing a piece that another effect relies on.

• Distinguish carried spares from active equipment. The Side Bag stores inactive items. That makes it useful to think in two lists: the setup currently fighting and the alternatives you might bring into it. A backup does not solve an immediate damage or resource problem merely because you own it. When checking why an expected effect is missing, verify where the relevant item is stored before assuming the interaction is broken. The launch announcement is the source for this inactive-storage rule.

• Use visible results when rearranging. Record an Artifact's displayed state before moving support away from it and compare afterward. If multiple values change, trace the contributing pieces one at a time. This is more informative than judging a rearrangement solely from how much empty space remains. Keep the useful comparison small enough that you can undo it confidently. The aim is to understand the tradeoff you are making, especially when a replacement supports a different trigger or damage source.

Choose a direction without forcing a shopping list

• Build around an available connection. A good starting question is whether two pieces you already possess explicitly support each other. From there, decide which missing function matters most: keeping the attack available, dealing with a difficult situation, or improving the existing payoff. This site uses “route” for that decision process. It does not imply that a particular drop is guaranteed, that a map node always appears, or that every run can assemble the same final inventory.

• Name a fallback before committing. If a proposed setup depends on an item you have not obtained, decide what you will use while waiting. A fallback should keep the current weapon usable without requiring the missing interaction. It is also reasonable to abandon a plan when another documented connection becomes available. This is an editorial decision method, not a claim that switching is always free or that every offered upgrade can be reversed. Read the actual choice screen before spending resources.

• Give a defensive failure a specific description. “The build is weak” tells you less than “I could not act after the first special attack” or “I lost track of incoming attacks while standing close.” The more specific observation points toward a more useful adjustment. Keep damage comparisons separate from control comfort and survivability. A player learning an input pattern may reasonably prefer a setup that is easier to repeat, even when another setup produces a larger number under ideal conditions.

Characters, costumes and progression are different questions

• Start by identifying which menu you mean. Searching for a character can mean a playable costume, a person encountered during the story, or a combat companion. Those categories answer different questions. A costume effect belongs in your starting setup; an NPC's dialogue does not make that NPC a playable class. Avoid treating every named figure as a selectable hero. Our character page focuses on documented costume information and marks missing unlock requirements rather than inventing a complete roster.

• Distinguish Talents from weapon skills. A search for a skill tree can refer to Destiny Inscription progression, a Talent choice, or an attack named in a weapon tooltip. Start with the system that controls the thing you want to change. If you are trying to make an attack appear, inspect the weapon and input settings. If you want to expand future preparation options, inspect progression. A point-allocation recommendation is only meaningful when it states which system and which available choices it concerns.

• Check the save before following an old unlock guide. Older public guides can be useful historical evidence, but a requirement copied from Early Access is not automatically a current instruction. Match the displayed name, read the current locked-entry text, and note any associated quest. This is especially important when an old guide lists fewer entries than the launch announcement. Missing documentation here is a research gap; it is not proof that the game lacks the content.

Use practice to answer the next question

• Try unlocked equipment in the Comprehensive Training Grounds. The 1.0.31 notes explain that this area is entered from the Training Grounds entrance and lets you take out unlocked items through the inventory. Use that opportunity to isolate an interaction before judging an entire run. Start with the weapon, add the item that is supposed to enable it, and watch for the expected behavior. Record what you actually see rather than assigning the result a rank immediately.

• Keep practice and expedition results separate. A controlled test helps establish whether an effect occurs. A run asks whether you can obtain the setup, operate it under pressure and keep it functioning across encounters. Neither observation replaces the other. When comparing notes with a friend, include the patch, equipment, relevant settings and what was being tested. A short reproducible explanation is more useful than a screenshot labeled “broken” with no account of the conditions behind it.