> ## Documentation Index
> Fetch the complete documentation index at: https://items.lodemc.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Bedrock (Geyser)

> Let Bedrock players joining through Geyser see your items, blocks, props, armour, sounds and glyphs.

Bedrock players who join through [Geyser](https://geysermc.org) can't load a Java resource pack. With Geyser support on, Lode Items also builds a **Bedrock pack** and Geyser's **custom item and block mappings** every time it builds the pack, and writes them into Geyser's folder.

## Turning it on

**1. Enable it in config.yml**

```yaml plugins/LodeItems/config.yml theme={null}
geyser:
  enabled: true
  folder: "Geyser-Spigot"   # Geyser's folder, relative to plugins/
```

**2. Let Geyser show custom items**

In Geyser's `config.yml`, set `add-non-bedrock-items: true`.

**3. Restart the server**

Lode Items writes these files before Geyser starts:

* `packs/lodeitems.mcpack`
* `custom_mappings/lodeitems_items.json`
* `custom_mappings/lodeitems_blocks.json`

> [!WARNING]
>
> Geyser only reads its packs and mappings when it starts. After `/lodeitems reload` changes anything Bedrock players see, the console says so: **restart the server** (or Geyser) for them to see it.

**Geyser on a proxy** (BungeeCord, Velocity): set `folder` to any folder, then copy its `packs/` and `custom_mappings/` to the proxy's Geyser folder.

## What Bedrock players get

The Bedrock pack is made from the finished Java pack, so packs merged with [`pack.merge`](https://items.lodemc.net/resource-pack#merging-other-packs) are included too.

| Content | On Bedrock |
| - | - |
| [Items](https://items.lodemc.net/items.md) | Their own icon and name. Handheld tools are held like tools. |
| [Blocks](https://items.lodemc.net/blocks.md) | All kinds: solid, see-through, walk-through, rotated, per-face textures, `model:` blocks, stairs, slabs, trapdoors and doors. |
| [Props](https://items.lodemc.net/furniture.md) | Their 3D model, including states, open doors and connected shapes. Hitboxes, seats and storage work as for Java players. |
| [Armour](https://items.lodemc.net/armor.md) | Flat sets with their worn texture, 3D sets in 3D. |
| [Sounds](https://items.lodemc.net/sounds.md) | All custom sounds. |
| [Glyphs](https://items.lodemc.net/glyphs.md) | In chat and text. Animated glyphs show their first frame. |
| Elytras, mob armour | The vanilla item (see below). |
| [Fluids](https://items.lodemc.net/fluids.md) | Plain water. |

Behaviour is all server-side, so it's the same for everyone: mining speed, drops, events, mechanics, recipes.

### Elytras and mob armour

On Bedrock, only the real elytra can glide, and only vanilla horse armour, wolf armour, carpets and saddles fit on a mob. That is built into those items and can't be added to a custom one. So custom elytras and mob armour are shown to Bedrock players as **their base item** (`material:`): they still glide and fit their mob, with the vanilla look. The console lists these items when it builds.

### Menus and optional packs

* The [item browser](https://items.lodemc.net/commands.md#item-browser) and other menus show their plain look (vanilla icons) to Bedrock players.
* [Optional packs](https://items.lodemc.net/resource-pack.md) are Java only: `/packs` tells Bedrock players so. Geyser sends the same packs to every Bedrock player.

## How props are shown

Geyser can't draw the display entities props are made of. Instead, each Bedrock player who can see a prop is sent an invisible armour stand (only they see it, and it costs no real entity on the server) wearing the prop's model.

> [!NOTE]
>
> Geyser support hasn't been tested with a Bedrock client yet. If something looks wrong (a block turned the wrong way, a prop floating or facing away), please report it with a screenshot.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.