> For the complete documentation index, see [llms.txt](https://cardstock-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cardstock-studio.gitbook.io/docs/test/a-b-variations.md).

# A/B Variations

Performing A/B tests is a great way to understand how slight changes to your rules may impact the game. **This is not going to discover "fun" changes — human playtesting is still required.**

This can let you know if rule changes result in a longer or shorter game, or if it changes how often bot players perform specific actions.

Best practice: follow up all playtest learnings with human playtests and your own human mind.

## Create a Variation

Click the "*+ Add Variation*" button to create a new variation. All variables that have been identified will be displayed — with some hidden behind the "*Show internal values*" button.

{% hint style="info" %}
Best practice is to change very little when running variations, ideally just a single impactful value. This way any deltas between the two will likely be a result of your change, which allows you to action upon it.
{% endhint %}

### Name your variation

At the top, double click the variation name to name it something you will recognize later. 

<figure><picture><source srcset="/files/dOWzmQ4iTzwkXwwcOvN7" media="(prefers-color-scheme: dark)"><img src="https://2449056524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK6BdQXak9wiY4BdSf9Rq%2Fuploads%2Fg8LtHbo5BhLYaANGIfBY%2FScreenshot%202026-07-19%20at%208.12.09%E2%80%AFPM.png?alt=media&amp;token=326e7d3e-1f98-4129-b534-764ce8584dd5" alt=""></picture><figcaption></figcaption></figure>

### Set Values

Find the value you'd like to change, and update the field under the Varation you're targetting.

<figure><picture><source srcset="/files/HwLygVZ8TZ6wP340Tenr" media="(prefers-color-scheme: dark)"><img src="https://2449056524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK6BdQXak9wiY4BdSf9Rq%2Fuploads%2FZmRc5WTApxKkFmIIhg1j%2FScreenshot%202026-07-19%20at%208.12.16%E2%80%AFPM.png?alt=media&amp;token=4c37b2d5-5c79-45e7-9bc2-9e594efdb3e4" alt=""></picture><figcaption></figcaption></figure>

Here, we are doubling the starting cards from 4 to 8, giving players more options to choose from.

While this step is optional, when you're ready, you can [Simulate & Analyze](/docs/test/simulate-and-analyze.md) your game!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cardstock-studio.gitbook.io/docs/test/a-b-variations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.