# Ultrono Arena map authoring: Quick Start

The add-on supports Blender 4.3 or newer on every operating system supported
by Blender. Import, editing, validation, and export do not require the UA source
repository, Rust, Cargo, or a native game client.

## Install

1. Download `ua-blender-map-addon-latest.zip`. Do not unzip it.
2. In Blender, choose **Edit > Preferences > Add-ons > Install from Disk** and
   select the zip.
3. Enable **Import-Export: Ultrono Arena Map**.
4. Optional: open the add-on preferences and set **Asset Root** to a UA asset
   directory containing `debug.bmp`, `tex`, and `map`. Geometry editing and
   export still work when textures are unavailable. If a `.blend` was opened
   before configuring assets, click **Reload UA Texture Assets**.

## Make a small map

1. Start a blank Blender file.
2. Open **Scene Properties > Ultrono Arena Map Tools** and click **Set Up UA
   Authoring Workspace**.
3. Use **Floor**, **Block**, and the entity buttons to create objects at the 3D
   cursor. Select an object and edit its semantic fields under **Object
   Properties > Ultrono Arena**.
4. Every normal map needs at least one Player Spawn. CTF needs one Cyan and one
   Gold flag base. Sacrifice additionally needs exactly one Soul Spawn.
5. Choose the intended mode in the optional playtest section, then click
   **Validate UA Map**. Validation errors offer **Select** buttons that focus
   the responsible object.
6. Choose **File > Export > Ultrono Arena Map (.map)**. Keep the textual `.map`
   file as the portable source of truth; keep a `.blend` alongside it when
   Blender-specific organization is useful.

## Existing maps and textures

Use **File > Import > Ultrono Arena Map (.map)**. The importer searches the map
directory and its parent for relative texture paths. An explicit **Asset Root**
in the add-on preferences takes priority and avoids depending on where Blender
was launched.

The public beta intentionally rejects unsafe absolute or parent-relative
texture paths. It also does not silently repair historically malformed
non-XML map text; canonicalize such maps with repository tools first.

## Optional native playtest

Native playtest is a developer feature in this beta. Authoring does not depend
on it. Developers may configure either an explicit **Native Playtest Launcher**
or a **Developer Repository** in the add-on preferences. The repository
launcher requires the repository's own Bash, Python, Rust, and Cargo setup and
is not an OS-independent end-user runtime.

See `README.md` and `docs/blender-map-authoring.md` in the UA repository for
the full navigation, geometry, texture, validation, and source-control guide.

## License and included content

The add-on code, package documentation, and metadata are licensed under
`GPL-3.0-or-later`; the archive includes the complete license text and scope
notice. The package intentionally contains no maps, textures, sample `.blend`,
or game runtime. Using the add-on does not apply its license to maps or assets
that you open or create.