Unlock advice must be more precise than a weapon ranking. A player needs the displayed weapon name, the exact requirement or message, the mode and save context, and a way to confirm that the unlock belongs to base-game AppID 2436940. If a community post supplies only a rumor or an old Early Access route, keep it as a lead rather than turning it into a guaranteed instruction.
Separate evidence from inference
“I found a new weapon after playing” is an observation. “You must defeat this boss without taking damage” is a requirement claim. The second needs a visible message, a repeatable experiment, or an official source. Do not infer a hidden gate from timing alone; a reward may have been granted by a different progression event, save state, or update.
Use the Chapters and Updates hubs to identify route and version context. If a test fails, record what the game displayed and what was already completed. A negative result is valuable when it prevents a reader from repeating an unsafe detour.
Verify a new weapon
After the menu shows the weapon, start a small comparison in the Weapons Guide. Test the basic action before judging upgrades. Write whether the weapon is available in solo and co-op as observed; do not assume that a menu presence proves every mode uses the same pool. Preserve the first-use context so a future update can be compared.
If the unlock is tied to an achievement, link to the Achievements hub and keep the achievement description separate from the route suggestion. Steam currently lists the base product’s achievement scope, but a community route still requires a live confirmation.
Product and version boundary
The Steam store lists a separately associated Sephiria demo with AppID 2686970. This guide covers the base game AppID 2436940, so do not merge weapon screenshots or unlock instructions unless the source identifies the product. Early Access posts can show a genuine historical route and still be wrong for the public release.
A complete unlock record
An unlock record should say where the player first saw the weapon, whether the menu marked it permanent, which action preceded the change, and whether a fresh run could select it. Add the exact date and platform. If the player was in co-op, record party size and host context because an observed group condition should not be silently rewritten as a solo requirement.
When comparing two reports, keep both until the difference is explained. One player may have completed a chapter while another completed an achievement; one may be using a launch build while another is reading an Early Access guide. The correct response to conflicting evidence is a narrower test, not a more confident sentence.
What to do after confirmation
Once a weapon is confirmed, pass the result to the Weapons Guide for behavior testing and to Weapon Upgrades for branch notes. Do not publish the unlock page as a complete build guide. The unlock tells a player when the option becomes available; the separate pages explain how to learn it and what evidence supports later recommendations.
If the unlock changes the available reward pool, record that menu state separately from the first combat test. Availability and usefulness are different claims, and each deserves its own versioned observation.
If the menu does not explain the pool change, state that it was observed but leave the cause open for a future retest.
That distinction keeps the unlock page from becoming an unsupported reward guide.
Keep the combat test on its own dated line.