Genesis support
Recover access, capture evidence, and keep moving.
Start with the path that matches the problem. Never include a password, API key, recovery token, or authenticator code in a report.
Can't sign in
Use Reset password for an email/password account. If two-step verification is enabled, use a current code from the enrolled authenticator. An inactive account remains blocked even when an old browser session still exists.
Editor or gameplay problem
Signed-in creators can open Report a bug from Genesis's global command menu. In Construct, Download debug information captures a sanitized reconstruction bundle and can attach permitted local models. Review the bundle before sending it.
Generation or background job
Keep the request or job identifier shown by Genesis. A refused action should name the missing configuration, review, budget, or durable-worker condition. Retrying a paid action may create cost, so review the latest estimate before approving it again.
Publishing or export
Use Project Delivery for canonical Editor release history, public links, view counts, and revoke controls. Run the available readiness check before export or publish. A green check applies only to the recorded source, schema, assets, and runtime evidence named in that result.
Privacy, export, or account deletion
Settings → Security contains session controls, two-step verification, structured account export, and account deletion. Complete binary assets and game packages are exported from their own workspaces. Read the privacy and data notice before deletion.