> 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/4.-using-experiments-to-try-ideas.md).
# 4. Using Experiments to Try Ideas
**Congratulations on creating your game! If you want to try something bold without applying it to your game first, check out Experiments below.**
{% 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 %}
**Experiments lets you open separate conversations with Cyra on the same game project.** Each experiment appears as a tab with its own sandbox, where you can test changes, try new ideas and push your game in different directions - all without touching your original version!
Keep what you like, ditch what you don't.
***
### How Experiments Work
Each experiment is a separate conversation with Cyra, but they all work on the same game project.
Here's the key difference:
* **"Your game" tab** = your main build. This is the version that gets published and shared.
* **Experiment tabs** = test versions. Changes here don't affect your main game until you decide to apply them.
You can have multiple experiments open at once. One could be testing a new color palette while another is reworking the combat speed. They will not interfere with each other.
***
### What Can I Use Experiements For?
Experiments are great for any change where you're thinking "this might be cool but I'm not sure yet."
* **Visual overhauls**\
Want to completely restyle your game? Test it in an experiment first. If the new look is better, apply it. If not, your original style is untouched.
* **Mechanic changes**\
Thinking about changing how combat works, adding a new movement ability, or overhauling the scoring system? Try it in isolation.
* **Audio direction**\
Testing different music styles or sound effect approaches without committing.
* **Wild ideas.** \
Ever think "what if I made the enemies twice as big?" or "what if gravity was reversed?" Experiments are built for this!
***
### How to Start an Experiment
1. Look at the top of your workspace. You'll see a **+** button next to the tab **"Your Game"**
2. Click **+** to open a new experiment tab.
3. A fresh chat along with a duplicate of your existing game opens with a message: *"Describe what you want to try. Your conversation and changes will appear here."*
4. Name your experiment something descriptive so you can keep track of it (e.g., "Red Color Theme," "Faster Enemies," "More Layered Sound Effects").
5. Type what you want to try and Cyra builds it.
***
### How to Apply an Experiment
**When an experiment produces something you want to keep:**
1. Click on "Experiment" under your chat.
2. Click "Apply to Game" and confirm it by clicking "Apply Changes"
3. Return to your main build. ("Your Game" Tab) You'll see a confirmation in your main chat. The changes from that experiment merge into your main game!
***
### How to Discard an Experiment
If an experiment didn't work out: \
\
**Option 1:** Close the tab to discard it permanently
**Option 2:** Archive it.
Nothing from that experiment carries over to your main game.
***
### How to Retrieve an Archived Experiment
Archived an experiment and want it back?
1. Click **Open experiments** (above the game preview)
2. You'll see all your experiments listed, including ones you've closed
3. Click on any archived experiment to reopen it as a tab
> **Quick-tip:** Built something cool in an experiment weeks ago and forgot about it? Check your archived experiments. The conversation and changes are all preserved exactly as you left them.
***
### Tips from Our Beta Game Creators (Like you!)
1. **Name your experiments clearly.** \
When you have 3 or 4 tabs open, "New experiment" and "New experiment 2" aren't helpful. "Neon Color Test" and "Boss Fight Rework" tell you exactly what each one is doing.
2. **Keep experiments focused.** \
One idea per experiment gives you the clearest results. An experiment that changes the visuals AND the combat AND the audio is harder to evaluate than three separate experiments.
3. **Use experiments before big changes.** \
Any time you're about to make a change that could break things you like about your current game, open an experiment first. It takes two seconds and could save you a full rebuild.
4. **Your main game is always safe.** \
That's the whole point. Experiment freely!
---
# 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/4.-using-experiments-to-try-ideas.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.
