> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/boxing-creator/configuration/ring-props.md).

# Ring props

The included 3D ring model, how it streams, and how to add your own ring models.

The script ships with its own 3D boxing ring, **`zarazir_boxing_ring`**, with built-in collision. Admins can place it anywhere from the creator. See [Ring creator](/visionstore-docs/scripts/boxing-creator/guides/ring-creator.md).

## How it streams

Every player spawns the model **locally** (frozen, not networked) when they come close, and removes it when they leave. Nothing is synced over the network and nothing can be left behind.

```lua
Config.RingPropStream = {
    Spawn = 220.0,    -- spawn within this many metres
    Despawn = 260.0,  -- remove past this
}
```

## Adding your own ring model

{% stepper %}
{% step %}

### Stream your model

Add your `.ydr` / `.ytd` / `.ytyp` to a streaming resource of your own, and make sure its archetype is registered (the `data_file 'DLC_ITYP_REQUEST'` line in that resource's manifest).
{% endstep %}

{% step %}

### Measure it

Using CodeWalker or in-game, note in the model's own space (origin = centre of the base, +Y = the front):

* the **canvas height** above the origin;
* the **fighting area** half-width (X) and half-length (Y) inside the ropes;
* where the **corners** are;
* where players should stand to open the menu (the **join point**, usually at the foot of the steps).
  {% endstep %}

{% step %}

### Add it to the config

```lua
Config.RingProps = {
    zarazir_boxing_ring = { ... },          -- keep the included one
    my_gym_ring = {
        label = 'My Gym Ring',
        canvas = 1.10,                      -- canvas height
        size = { x = 3.0, y = 3.0 },        -- fighting area half-extents
        corner = { x = 2.3, y = 2.3 },      -- red at (-x,-y), blue at (+x,+y)
        join = { x = 0.0, y = -5.0 },       -- menu point
    },
}
Config.RingPropDefault = 'my_gym_ring'      -- preselected in the creator
```

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The server only accepts models listed in `Config.RingProps`, placed within 10 m of the ring centre. If you remove a model from the list later, rings that used it keep working, just without the prop.
{% endhint %}


---

# 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://visionstore.gitbook.io/visionstore-docs/scripts/boxing-creator/configuration/ring-props.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.