Context

Target reader: developers attaching game state that helps triage a feedback report.

Context should explain where the player was and what they had just done. The contract supports scene, level, position, quest_id, and an extra object. Breadcrumbs and recent logs are separate arrays with limits from SDK config.

Minimal example

EchoNebulaFeedback.set_player({
  "player_id_hash": "sha256:337180dda29405211bf7a37ea531367110370dc54db2298fcf4450f1749badb3"
})

EchoNebulaFeedback.set_context({
  "scene": "res://scenes/hub.tscn",
  "level": "hub",
  "position": { "x": 12.5, "y": 0.0, "z": -3.0 },
  "quest_id": "tutorial_find_gate"
})

EchoNebulaFeedback.set_context_provider(func() -> Dictionary:
  return { "extra": { "coins": 42, "party_size": 3 } }
)

EchoNebulaFeedback.add_breadcrumb("inventory.opened", { "tab": "weapons" })
EchoNebulaFeedback.log_warning("Network retry started")

Common mistakes

• Do not put raw account IDs into player.id_hash; hash or pseudonymize them first.
• The example hash is a demo SHA-256 digest, not a player identifier to reuse.
• Do not place contact data in game_context.extra.
• Do not exceed max_breadcrumbs or max_recent_logs from SDK config.

Next step

Review Screenshots and privacy.