Known issues · 2 active workarounds
Both entries are single-source reports from the captured launch roadmap. They are not labeled as official acknowledgements.
Symptom and impact
Leaving the area before collecting the Tarstone may close the gates, and the cited report says they do not reset in NG+.
Temporary workaround
Collect the Temple of Vatra Tarstone before leaving the area for the first time.
Symptom and impact
The cited report says the interaction can remain stuck on the parry tutorial after entering NG+.
Temporary workaround
Fully upgrade Genessa's bond during the first playthrough before advancing to NG+.
Begin with the exact symptom, affected target, version label, and source date. A report belongs on this page because it can affect completion and includes a practical avoidance or recovery step; it is not automatically an official acknowledgement or proof that every similar failure shares the same cause. Match the game build and reproduce the described sequence before applying the label to a new run.
Read the workaround as temporary risk control. It can help protect a route while the issue remains unresolved, but it should not be rewritten as normal game design. If the workaround involves collecting an item before leaving, delaying a transition, or keeping a backup, follow only the step relevant to the named symptom. Broad precautionary language must not become an invented requirement for unrelated targets.
Record the build, platform, location, last successful action, expected result, and observed result before restoring a save. Keep screenshots, logs, or support correspondence outside the companion profile. The profile can preserve target states and source links, but it cannot store or verify the platform's gameplay data. Use the platform's own backup and synchronization controls separately.
After recovery, repeat only the smallest sequence needed to verify the workaround. If the target succeeds, close that target for the current run without declaring the underlying issue fixed for everyone. If it fails again, keep the target open and retain both observations. Multiple dated results are stronger evidence than changing the issue status from memory.
When an official patch or current build test resolves the symptom, add that evidence before removing the warning. Confirm the affected target in the new build, note whether the workaround is still required, and preserve the earlier record as history. A listed patch bullet alone is not enough if the wording only resembles the symptom.
An active workaround can coexist with a completed target in one run, and an unresolved target does not prove the issue occurred. The issue page describes risk evidence; the tracker describes the local run. Maintaining those two states separately prevents one player's successful workaround from hiding the warning or one failed attempt from marking every related objective broken.
A useful escalation record is narrower than a general bug report. Give the exact game build, platform, affected target, shortest reproducible sequence, expected result, observed result, and workaround outcome. Remove unrelated theories and never include account credentials or private save data in a public source note. If the report cannot be reproduced, label that uncertainty and keep the original evidence date. A later tester can then repeat the same sequence without mistaking a similar symptom for the same issue or interpreting silence as an official fix.
