> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/all-competition-types/backyard.md).

# Backyard

A Backyard event, or sometimes called "Last Man Standing", consists of a circuit to be repeated as many times as possible within a set time limit.

At the end of each lap, only competitors who have finished within the time limit are allowed to start the next loop.

## Settings

In Wiclax this type of event is managed like a lap race, which will have the particularity of having a start time for each lap.

If you did not select the Backyard event type when creating the event, the setting can be found here:&#x20;

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FjR775TUnCZZolckLdoqw%2Fimage.png?alt=media&amp;token=1e303515-dac0-41f0-b60d-fdf856f80b5f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The *unlimited number of laps* option is the most suitable in this case.
{% endhint %}

{% hint style="warning" %}
Note the additional option regarding the final time of the competitors, which can be the time of the last lap or the cumulative laps. It is this time which determines the final classification, to decide between competitors who have completed the same number of laps.
{% endhint %}

## Starts management

The event list of starts must contain one line for each round (lap):&#x20;

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FIBpYGxaji2YWsw4bpv3a%2Fimage.png?alt=media&amp;token=6bbfb6ed-c025-47d9-a629-e989ae29f12c" alt="" width="362"><figcaption></figcaption></figure>

The lines are normally pre-positioned, and you just have to fill in the times.

{% hint style="info" %}
If multiple races are managed in the same file and with separate starts, the start lines will need to be duplicated. For example 2 lines for round 1, each with a filter associated with its respective race.
{% endhint %}

## Results management

Wiclax does not automatically eliminate out-of-time competitors. You must therefore manually mark them as DNF, or more simply ensure that their chip is removed to prevent them from accidentally crossing the finish line again.

## Printout

When printing the results, remember to ask for the summary lap columns to be printed, in order to obtain a complete summary of the race.

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FXq3xA0C6dJaDCp2FKTsj%2Fimage.png?alt=media&amp;token=d539d6ff-2d63-40a5-bccd-b77912df5e44" alt=""><figcaption></figcaption></figure>


---

# 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.wiclax.com/en/all-competition-types/backyard.md?ask=<question>&goal=<user_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.
