> For the complete documentation index, see [llms.txt](https://docs.gocipher.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gocipher.gg/cipher-tutorials/5.-publishing-and-sharing-your-game.md). # 5. Publishing and Sharing Your Game **You've built a great game! Now let's put it in front of gamers!** {% hint style="info" %} Not done with your game creation yet? We recommend you to check out: \ \ [**1. Getting Started**](/cipher-tutorials/1.-getting-started.md) to learn more about the tools you'll be mastering;\ [**2. Creating Your First Game**](/cipher-tutorials/2.-creating-your-first-game.md) to get your first game up and running; \ [**3A. Improve Your Game Via Design Studio**](/cipher-tutorials/3a.-improve-your-game-via-design-studio.md) to perfect your game manually; [**3B. Improve Your Game Via Cyra**](/cipher-tutorials/3b.-improve-your-game-via-cyra.md) to perfect your game through chat {% endhint %} This guide covers how to share your game instantly with a link, how to submit it to the [**Cipher Game Lobby**](https://gocipher.gg/games) where everyone can play it, and what happens after publishing your game. *** ### Sharing Your Game (Before Publishing) You don't need to publish on the [**Cipher Game Lobby**](https://gocipher.gg/games) immediately if you're not ready! \ You can still share it. Every project has a **Share** button that generates a link instantly. #### When Do You Use Sharing? 1. **Game creation on Livestream** \ Share the link with your audience so they can play along while you build on stream. You build the game live, they play it in real time.
2. **Getting feedback before you publish** \ Send the link to your friends and family, or on our [**Discord**](https://discord.com/invite/gocipher). Find out what's broken, confusing, or fun before it goes live.
3. **Testing on different devices**\ Open the link on your phone or another computer to see how your game plays outside the workspace.
#### **How to Share Your Game**
1. Open your project in the workspace. 2. Click **Share** in the bottom toolbar. 3. A "Share your game" popup appears with a **Public link**. 4. Click **Copy link**. 5. Send that link to anyone. They can play in their browser or mobile device immediately
> **Quick-tip:** The link stays the same even when you update your game. When you make changes, anyone who opens the link gets the newest version automatically. *** ### Publishing to the Cipher Game Lobby \ Publishing puts your game in the [**Cipher Game Lobby**](https://gocipher.gg/games), which is where gamers go to discover, show their support and play games by independent creators! Your game will show up as a card listed in a grid alongside other creators' games. #### **Before You Publish** Make sure your game is ready for everyone to play:
* **Does the game work from start to finish?**\ The game loads, the player can interact with it, and there's a clear ending (game over screen, win state, score display).
* **Can someone figure it out without you explaining?** \ If the controls aren't obvious, make sure they're shown on a title screen or instructions overlay. After all, you won't be standing next to every player!
* **Have you tested it in Fullscreen?** \ Hit Fullscreen and play through the entire thing at least once.
* **Does the title screen work?** \ If your game has a Play button or Start screen, make sure it actually responds when clicked. #### **How to Submit Your Game For Publishing**
{% hint style="info" %} Publishing goes through a quick review process where the Cipher team will check for major issues and flag up to you if any requires fixing before it goes live. {% endhint %} 1. Open your project in the workspace. 2. Click **Publish** in the bottom toolbar. 3. Fill in the **Game Details** popup: * **Game Name** — The name players see in the lobby (Max. 30 characters) * **Game Description** — What the game is about (Max 250 characters) * **Game Cover Image** — A 16:9 image that represents your game. This is the biggest thing on your card and the first thing players notice. Accepted formats: JPEG, JPG, PNG (Max. 10 MB) 4. Click **+ Submit for Review**. > **Quick-tip:** Not sure how to design a cover image? No problem! Simply generate a cover image unique to your game using the tools provided on the publishing page. #### **What Happens After Submission** Your game enters one of these states:
StatusWhat it means
Under ReviewYour game is tested for any major gameplay issues
PublishedYour game is live in the Cipher Game Lobby
UnpublishedRemoved from the lobby (Can be republished after fixes)
Once published, your game appears in the lobby with your cover image, game name, avatar, and nametag. Players click **Play Now** to launch it. *** ### After You've Published Your Game 1. **Keep improving!** \ Publishing doesn't freeze your project, so you can keep making changes. All updated versions will go live automatically through the same link.
2. **Tell people about it.** \ Share your game with your audience or show people how to locate your game on the Cipher Game Lobby!
3. **Stream the whole process.** \ For creators seeking new, unique and engaging fan-service or stream ideas - why not build a game live, publish it, then having your community play it in real time?
4. **Collect feedback!**\ Use it to make your game better. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gocipher.gg/cipher-tutorials/5.-publishing-and-sharing-your-game.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.