Trigger Points

Target reader: developers deciding where players can open the feedback panel.

Supported trigger sources come from the contracts enum: api, hotkey, button, menu, shake, error_prompt, and qa_menu. P0 should favor deliberate player actions such as a visible button, F8, an in-game menu item, or a QA menu.

Minimal example

func _on_pause_menu_feedback_pressed() -> void:
  EchoNebulaFeedback.open_feedback_panel({
    "trigger_source": "menu",
    "category": "bug"
  })

func report_from_code() -> void:
  EchoNebulaFeedback.open_feedback_panel({
    "trigger_source": "api",
    "category": "suggestion"
  })

The built-in hotkey opens the panel with trigger_source set to hotkey.

Common mistakes

• Do not automatically submit feedback from a crash or exception path. echo-nebula is not crash monitoring.
• Do not invent trigger names outside the contracts enum.
• Do not hide the privacy confirmation when opening from a QA-only entry point.

Next step

Add useful scene and player Context.