Player feedback and community links

Hear from your players

Give feedback appears on the game page and in the player header. Signed-in players can send a suggestion, bug, or other feedback of up to 4,000 characters. Guests are prompted to sign in. Private-game testers can submit when they have access.

Open Manage → Feedback alongside analytics and diagnostics. The private inbox shows the player's public username, message, date, and the build when sent while playing. Keep feedback to revisit it, or discard it. Discarded feedback can be restored.

Use your preferred development tools to act on feedback and publish an update. Feedback does not automatically edit your game, start an AI task, or notify other players.

Optional SDK integration

import { Inkwell } from '@silicon-jungle/inkwell-sdk'

export async function readCommunityLinks() {
  const game = await Inkwell.game.get()
  return { websiteUrl: game.websiteUrl, discordUrl: game.discordUrl }
}
// Connect this to your game's feedback button.
export async function giveFeedback() {
  await Inkwell.feedback.open()
  // The form is open. The player decides whether to submit.
}

Available in SDK 0.0.8 and later. Both methods require the Inkwell player frame. Opening the form resolves with { opened: true }; this does not mean feedback was submitted. The player controls submission. Game code cannot read feedback, access the creator inbox, or submit on a player's behalf.

Website and Discord server

Both fields are optional in Manage and on game creation. Website accepts a full HTTP(S) URL. Discord accepts an HTTPS invitation such as discord.gg/example or discord.com/invite/example. Links appear on the game page and are returned by Inkwell.game.get(), with null for unset values.

inkwell games update --game my-game --website https://example.com --discord https://discord.gg/example
# Omit a flag to keep its current value; pass an empty value to clear it.
inkwell games update --game my-game --website "" --discord ""

CLI 0.0.12 adds these flags to both create and update. The creator API uses optional websiteUrl and discordUrl fields. An omitted field is preserved; null or an empty string clears it.

Creator inbox API

Creator sessions and creator API keys can read and triage their own game's feedback. These endpoints are private and return no account email or internal player ID.

GET /api/v1/games/:slug/feedback?status=inbox&offset=0
# status: inbox | kept | discarded; up to 50 entries and nextOffset
PATCH /api/v1/games/:slug/feedback/:feedbackId
{ "status": "kept" }

Player submission uses POST /api/v1/games/:slug/feedback with a signed-in browser session, same-origin write protection, a UUID requestId, kind, message, and optional accessible buildId. Retrying the same request and content returns its original receipt; changing content with the same request ID returns 409. Creator API keys cannot submit player feedback.