> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/colibri/building-exercises/branching-and-choices.md). # Branching and Choices In exercises, you can create branching based on player choices. Designing exercises that consider **player agency** ensures they are immersive. Training is much more memorable and effective when players **experience the impact of their choices**.

What is branching?

Branching is when a scenario **splits into different paths** based on a decision point.

## How to Follow these three steps to set up branching in your scenario table: {% stepper %} {% step %} #### Create a new step as a question type To branch, select either `Choice` or `Drop-down list` under *Type of question*. {% hint style="danger" %} You won't be able to branch with either Multiselect or Open text options. This is because there is no clear answer. {% endhint %}

{% endstep %} {% step %} #### Select the persona and channel Fill out the content of the step (which should include a question). {% hint style="success" %} Click the :sparkles: icon to generate content with our AI Assistant. {% endhint %}

{% endstep %} {% step %} #### Go into the `Interactions` tab Click `+ Add new option` to create a response to the persona question. Fill out the button text and decide which step will be activated as a result of the player selecting it. To achieve branching, the **activated steps for each button should be different**.

{% endstep %} {% endstepper %} ### Arrange You can branch with Arrange but it's important to note the answer arranged at the top is the one that activates the next step (the outcome):

## When to use Use branching in your exercise when you want players to experience the impact of their choices. This is most effective when the right answer isn't entirely clear. As a result, different players will have different experiences within the same exercise based on their own perspectives. ### Alternate endings A great way to use branching is to create alternate endings for players based on their actions. It may be that you don't need to use branching throughout your exercise but only at the end for maximum impact. This would work for scenarios where **tension culminates into one dilemma**. By using alternate endings, players can feel and experience the consequences of their actions.

### :zap:Avoid overuse Too much branching can **overcomplicate exercises**. Only use when necessary to immerse players and get the most out of experiential learning. If you're using branching in the middle of an exercise, it's recommended to **eventually bring the scenario back into one pathway again unless you're using alternate endings.**

--- # 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://helpdocs.conducttr.com/colibri/building-exercises/branching-and-choices.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.