Skip to main content
A survey is a standalone form with its own link, its own roster, and its own analytics. Nobody has to play anything. Publish it, share the address, and answers come back.

Playbooks

Run a survey

Create it, publish it, and read the responses.

Write survey questions

Pick block types, order them, and avoid leading the respondent.

Share a survey link

Get the link out, and rotate it if it lands somewhere you did not intend.

Announce a survey in Discord

Post an embed with a Take the survey button to a channel.

When to use one

Surveys suit any structured feedback that is not tied to a gameplay session:
  • Pre-launch interest checks (“Would you play a co-op survival game on Steam Deck?”)
  • Post-playtest follow-ups sent days after the session
  • Community polls shared on Discord or social
  • Player profiling, to sort respondents into groups for future playtests
If you want feedback during or right after a session, use the playtest’s own survey component. If you want to filter people by their answers, use a waitlist.

How it works

1

Create a survey

Open Surveys in the sidebar and click Create survey. Name it, and you land in the editor.
2

Set up onboarding

Choose the identities a respondent must connect, and write the welcome content they land on.
3

Write the questions

Up to 20 blocks, questions and context together.
4

Write the Thanks screen

This is what a respondent sees the moment they submit.
5

Publish and share

Click Publish, then copy the link.
6

Read the results

Responses arrive as people submit them.

What you configure

Publishing adds two more views, the roster of respondents and the analytics behind their answers. Announcement is off until you switch it on in Config, and it needs a connected Discord server. Turning it on adds the Announcement tab, where you write the message that posts with a Take the survey button.

Survey announcements

Writing the message, what publishing costs, and how the button follows a link reset.

Surveys and groups

Every survey keeps its respondents in a player group of its own. The group is owned by the survey: you manage it from the survey, you cannot rename it or add to it by hand, and archiving the survey archives the group too.

Lifecycle

Once published, a survey moves between published and unpublished for the rest of its life. It never returns to draft.

Next steps

Survey onboarding

The identities to require, and the screen respondents land on.

Survey questions

Block types, the 20-block cap, and when the set freezes.

Publishing a survey

Go live, and get the link respondents open.

Survey analytics

Who responded, and what they said.

Survey acknowledgement

What a respondent sees the instant they submit.

Run a survey

Playbook: write the questions, publish the link, read the answers.