Echo Weaver · Reviewed Nov 4, 2026

Tetsa Courtyard Lead and achievement not counting | Echo Weaver

Quick answer

Hotfix 1.0.0.67 on October 18 fixes two Courtyard triggers: the location not counting toward Tetsa’s achievement and her Lead not logging. The developer moved the check to the start of the long conversation and added a safety check at every loop start. Update first; recovery of every earlier save has not been independently tested by GGClue.

Version and source details

Guide context: Tetsa Courtyard Lead or achievement missing in Echo Weaver? See what the 1.0.0.67 hotfix actually changed, plus what older saves still need to verify.

Game version and evidence scope: PC hotfix 1.0.0.67 October 18, 2026; later 1.0.8 news also reviewed; sourced, not independently played by GGClue.

Last reviewed: Nov 4, 2026

Sources and evidence scope

  • Echo Weaver developer hotfix notesdeveloper or publisher primary evidence · Tier A · checked Nov 4, 2026

    Supports: Version 1.0.0.67 Courtyard and Tetsa trigger changes

  • Steam player discussionsplayer/third-party evidence · Tier D · checked Nov 4, 2026

    Supports: Issue follow-up; not an independently verified universal mechanic

Check your exact symptom and game version

This page covers Tetsa Courtyard Lead and achievement not counting, rather than unrelated walkthrough objectives. The relevant source scope is PC hotfix 1.0.0.67 October 18, 2026; later 1.0.8 news also reviewed. A correct answer depends on the active game version and the precise problem; GGClue does not claim a firsthand playthrough.

Question What the evidence says
Verify the installed build The named Tetsa hotfix is 1.0.0.67; a previous attempt in 1.0.0.66 did not fully solve it.
Separate two symptoms The Courtyard Lead and the achievement are two distinct flags mentioned in the patch.
Compare the new trigger The developer now checks at conversation start and at new loop starts; it did not prescribe deleting saves.
Original GGClue three-step evidence checklist for Tetsa Courtyard Lead and achievement not counting, not gameplay UI
Original GGClue evidence map: Tetsa Courtyard Lead and achievement not counting. Editorial diagram, not an in-game screenshot.

The precise failure

The developer reported that Courtyard failed to count for Tetsa’s achievement and sometimes did not log her corresponding Lead. A missing record is not proof of a separate collectible or another hidden dialogue option. Identify which of the two entries is absent on your save.

What 1.0.0.67 actually changed

The October 18 Tetsa Blip hotfix moved the award point to the beginning of her longer Courtyard conversation, rather than waiting until it finished. It also checks the achievement at the start of every time loop. A prior 1.0.0.66 fix was not sufficient for all players, which is why the later version matters.

Safe checks before replaying anything

Check your installed version. On your existing run, note whether Tetsa’s Lead is listed and whether the achievement registered. Observe the status after a loop restarts, if you naturally reach one. The notes do not confirm a universal reload path or a separate item that must be picked up. Do not delete saved progress to try to force the trigger.

If the record still fails

Provide the current build, platform, missing Lead versus achievement, conversation state and loop history through the official discussion channel. The developer’s code change is strong evidence of an intended fix, but it is not a first-person GGClue verification of every previous save.

Frequently asked questions

Did I need to finish the whole long conversation?

The patched trigger is now at the beginning, not the end; older instructions may no longer apply.

Are the Tetsa Lead and achievement identical?

No, the official patch mentions both records separately.

Does starting a new loop always repair an old save?

The developer added a loop-start check, but GGClue has not reproduced every old save.

Primary sources and what they establish

The sources support the claims above only within their specific date and version. Third-party playthroughs do not become developer statements or first-person GGClue observations.

Limit of this answer: No first-person Tetsa route or retroactive recovery test.

Independent publisher notice: GGClue is an unofficial English-language player-help website, not the developer or an authorized support desk. No copyrighted gameplay screenshot is represented here as an owned capture.