Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/BunnyNabbit/voxel-telephone/llms.txt

Use this file to discover all available pages before exploring further.

The point of Voxel Telephone is to watch how a prompt transforms as it passes through many players’ interpretations. That only works when every player builds and describes honestly. These rules keep the game fair and the gallery enjoyable for everyone.

Core rules

Do not intentionally derail games. Build and describe as you genuinely see it.
  1. Build and describe faithfully. When it is your turn to build, build what the prompt describes as you honestly interpret it. When it is your turn to describe, write what you actually see in the build. Deliberate derailing — building or describing something unrelated on purpose — ruins the chain for every player who contributed before you.
  2. No inappropriate content. Builds and prompts must not contain sexual content, graphic violence, hate symbols, or any other content that would be considered inappropriate for a general audience.

Describing accurately

When describing a build, focus on what the build represents — not how well it was made. Avoid commenting on build quality (for example, “a poorly built cat”). Describe what you see as if you were telling someone who cannot see it. Enter your description in chat. When you are satisfied with it, use /finish to submit.

Reporting violations

If you encounter a prompt or build that breaks the rules, use /report followed by an optional reason:
/report inappropriate content
Reporting does the following:
  • Skips the game for you immediately and returns you to the hub.
  • Removes the game from the active queue so other players are not assigned it.
  • Flags the game for moderator review with your reason attached.
Use /report instead of /skip whenever content is genuinely inappropriate rather than just difficult to interpret.
/skip passes on a game without flagging it. Use /report when the content itself is the problem.

Build docs developers (and LLMs) love