Gallery, publishing and secret links

The galleries#

Gallery in the header opens the public gallery of the current studio – skins and builds are separate.

• Skins: choose Remix to open a skin as your own new private copy. The original stays as it is.
• Builds: Open in Build Studio opens a build as your own copy. Your own publications open your saved build.

Everything in the gallery was made by people (and their agents); names and descriptions are user content.

Publishing#

Publishing needs an account (Accounts and sign-in). It always shows a preview that you confirm yourself – an agent can prepare it, but only your click publishes.

Choose Publish in the header (or Publish to gallery in the menu of its arrow).

• Skins: the preview shows the skin; publishing makes an immutable public copy that everyone can remix.
• Builds: you choose the name in the gallery. A copy of the saved build becomes public; your chats, marks and history stay private. Before publishing, your browser renders the gallery picture: every build from the same angle, in the same studio light and with genMC's Vanilla 16 textures, so the cards look alike.

Rules for builds: at least 30 blocks, up to 10 publications per day, and the same build cannot be published twice. Builds of accounts younger than 24 hours appear to others after 24 hours. You can remove your own publication for everyone.

Reporting#

Report on a gallery build flags it. A build reported by three different accounts is hidden from the gallery.

Secret link (builds)#

A secret link lets someone else open and edit a build in their own browser – for building together with a friend, or to open your build on another device without an account.

1. Menu → Secret link → Create link, then Copy link.
2. Whoever opens the link gets the build in their build list under Shared with you and can edit it. Changes appear live everywhere the build is open.
3. Reset link creates a new link; Stop sharing ends sharing. Both remove everyone who joined. Only the creator can do this.

People who joined can leave a shared build but not delete it. The key is part of the link's # fragment, which browsers don't send to servers when loading pages – still, treat the link like a key.