Fast answer

Obsidian tracks an onboarding blocker where Diving the Depths may not update if Eelgrass was scanned before the quest began. No universal workaround is documented, so preserve the save and report that exact state.

Do this first

Save-safe order

  1. Confirm the active objective asks for Eelgrass analysis.
  2. Record whether Eelgrass was scanned before the quest appeared.
  3. Do not delete analyzer, quest, or save data.
  4. Back up the world where available.
  5. Follow official issue P20-43219 and submit evidence if requested.

01

The exact trigger

The issue is specifically about scan order, not every stuck quest. Preserve whether the quest existed before Eelgrass was analyzed and who performed the scan in co-op.

02

Report without inventing a reset

Include build, platform, world type, host/client role, the current objective text, and a screenshot of the analyzer/quest state. Restarting may be harmless, but unrelated file changes are not a confirmed fix.

Evidence ledger

Sources checked

OfficialDiving the Depths P20-43219

Official trigger and issue ID.

OfficialGrounded 2 Issue Tracker

Authoritative issue IDs and current status. Recheck the tracker before acting on a status label.

Official supportHow to Report a Grounded 2 Issue

Official evidence and attachment requirements for useful support reports.

Editorial boundary

Official sources establish shipped features, issue status, and support steps. Cross-check and community sources are labeled and never treated as universal fixes.