A combo is a claim that two or more choices improve one another in a repeatable context. In Sephiria, that context may connect a weapon action to an Artifact shape, a Tablet placement, an upgrade branch, or a co-op role. The official store confirms the components and the strategic inventory, but it does not publish a complete combo database. Build a combo from an observable question and keep unsupported precision out of the final recommendation.
Write the combo hypothesis
Use a sentence with a condition: “If this Artifact stays in this region, the weapon can repeat its action safely in this checkpoint.” Avoid a vague statement such as “these items are strong together.” The condition tells you what to test and what evidence would disprove it. Include solo or co-op mode, chapter, platform, and version from the beginning.
Test the base action first
Perform the weapon action without the proposed support, then add one component. Use the same target and movement goal. Watch whether the result improves reliability, range, crowd control, recovery, or a visible effect. If the room differs, record it as a separate attempt. A combo that works only because the enemies behaved differently is not yet a stable recommendation.
Do not add every upgrade at once. A weapon branch, Artifact, Tablet, and Talent can all change the result, but a four-way change cannot reveal which part mattered. Test the simplest pair, then add a third component only after the first relationship is clear. This also makes the combo easier for a new player to reproduce.
Record the cost
Every combo spends something: inventory space, action time, proximity, attention, a teammate’s position, or a reward choice. Write the cost beside the benefit. A high-output combo may be appropriate for a boss window and poor for a first clear. A low-risk combo may take longer but complete more chapters. The objective decides the recommendation.
Keep combos current
When a patch changes the weapon, Artifact, Tablet, enemy, or boss used by the test, retest the base action and the combo. Link the result to Updates. Community clips can identify promising interactions, but rewrite the test in original language and omit copied tables, images, and unsupported numbers.
Compare pair, then trio
Run the weapon with one support component first. If the action becomes more reliable, add the next component and repeat the same checkpoint. If the result becomes worse, identify whether the new item consumed space, changed timing, or distracted from the original job. This stepwise route is easier to explain than an end-state build assembled from several simultaneous rewards.
Publish a failure boundary
State where the combo should not be used: crowded rooms, a boss phase, solo mode, a four-player arena, or a route with uncertain rewards. A limitation does not make a combo weak; it makes the recommendation usable. Link the detailed inventory observation to Artifact Synergies and the current balance note to Patch Notes.
Keep the build reproducible
Include weapon, branch, Artifact job, Tablet placement, chapter, mode, platform, version, and success condition. Do not require a reader to recognize a screenshot or copy a community table. The build is ready when another player can repeat the question, understand the fallback, and report a different result without changing the definition of success.
Keep the success condition in the first paragraph of any published combo so readers know what the interaction is trying to improve.
The condition should remain unchanged across the comparison runs, even when the reward choices vary.
Record why a variation was unavoidable and whether it changed the result.
That note keeps the comparison honest for the next player.