# LockerSpawn

**Description**\
Controls behavior for placing a custom item inside a map locker (e.g., rifle rack). When enabled, the spawn system will target a locker of the configured type/room/zone or offset relative to a locker.

**Parameters**

* `enable` — `bool` — Whether to attempt locker-based spawning.
* `locker_type` — [`LockerType`](/uncomplicatedcustomitems/api/enums/internal/lockertype.md) — Which locker/rack type to use (e.g., `RifleRack`).
* `room` — `string` — Preferred room name where the locker is located. Default: `"HczWarhead"`.
* `zone` — [`FacilityZone`](/uncomplicatedcustomitems/api/enums/external/facilityzone.md) (enum) — Preferred zone where the locker exists. Default: `HeavyContainment`.
* [`chamber`](/uncomplicatedcustomitems/api/enums/internal/lockerchambers.md) — `string` — ChamberName within the locker.
* `offset` — `Vector3` — An extra offset applied to the chosen locker position.

**Example Yaml context**

```yaml
spawn:
  spawn_settings:
  - chance: 20
    locker_settings:
      enable: true
      locker_type: RifleRack
      room: HczWarhead
      zone: HeavyContainment
      chamber: 0
      offset:
        x: 0
        y: 0
        z: 0
```


---

# Agent Instructions: 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:

```
GET https://docs.uci.ucserver.it/uncomplicatedcustomitems/api/spawning/lockerspawn.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
